Targeted offers such as coupons are a useful marketing tool to enhance brand loyalty and introduce new products. By customizing an offer to a consumer based on purchasing patterns and preferences, the offer provides a targeted incentive for the consumer to purchase a particular product or line of products.
Conventionally, offers have been available in printed form from sources such as newspapers. Increased adoption of electronic sources of information such as the world-wide-web, however, has led to the increase in popularity of electronic offers.
In addition, most consumers now own and operate a cell phone or other portable electronic device. This renders such consumers accessible to the distribution of electronic offers as they do their shopping, or are otherwise mobile. After distribution, the targeted offers may be redeemed. Such systems require knowledge of the nearest store locations where the offer can be redeemed. Moreover, the targeted offers are typically redeemed only at the physical store location. Recent developments in offer redemption permit offers to be redeemed for online purchases. In these systems, consumers are required to wait for delivery of the goods purchased using the offer. There is no way for consumers to redeem offers using their portable electronic device and to collect the goods or services at the physical store location. These and other drawbacks and limitations exist with respect to existing targeted offer distribution systems.
Embodiments of the invention address these and other problems individually and collectively.
Embodiments of the invention are directed to improved consumer notification systems and methods. In particular, a method and system for providing visual representation of purchase offers targeted to a consumer are disclosed.
One embodiment of the invention is directed to a method including monitoring for an event to trigger a targeted offer. Upon detection of the event, the offer is generated. The offer is targeted to a consumer and is generated using payment data generated in response to transactions conducted by the consumer with a plurality of different merchants. A geographic location for redeeming the offer is determined. A notification message is generated about the offer. The notification message includes the offer and the geographic location for redeeming the offer. The notification message is sent to a notification device which is operated by the consumer. A graphical depiction of the offer is displayed on a map on the notification device.
Another embodiment of the invention is directed to a notification device having a processor, an antenna coupled to the processor, and a computer readable medium coupled to the processor, the computer readable medium comprising code executable by the processor, the code comprising code for receiving an offer targeted to a consumer based on payment data generated in response to transactions conducted by the consumer with a plurality of different merchants, the notification device operated by the consumer, and code for generating a map comprising a graphical depiction of the offer and a graphical depiction of a geographic location for redeeming the offer, wherein the offer is received by the notification device upon detection, by a payment processing server, of a triggering event.
Another embodiment of the invention is directed to a system that includes a payment processing network configured to monitor for an event to trigger a targeted offer, generate the offer upon detection of the event, the offer targeted to a consumer, wherein the offer is generated using payment data generated in response to transactions conducted by the consumer with a plurality of different merchants, and determine a geographic location for redeeming the offer. The system also includes a notification module coupled to the payment processing network, the notification module configured to generate a notification message about the offer, the notification message including the offer and the geographic location for redeeming the offer, and send the notification message to a notification device operated by the consumer, wherein a graphical depiction of the notification message is displayed on a map on the notification device.
Accordingly, a method and system allowing for the redemption of electronic targeted offers by mobile electronic devices, such as a notification device, is disclosed.
Yet another embodiment of the invention is directed to a machine-readable storage medium storing a sequence of instructions execution of which causes a processor to provide notifications of targeted purchase offers, the execution of the sequence of instructions causes the processor to perform the actions of: monitoring for an event to trigger a targeted offer; generating the offer upon detection of the event, the offer targeted to a consumer, wherein the offer is generated using payment data generated in response to transactions conducted by the consumer with a plurality of different merchants, determining a geographic location for redeeming the offer, generating a notification message about the offer, the notification message including the offer and the geographic location for redeeming the offer, and sending the notification message to a notification device operated by the consumer, wherein a graphical depiction of the offer is displayed on a map on the notification device based on the notification message.
Other embodiments of the invention are directed to computer readable media comprising code for performing the above-described methods as well as systems, apparatuses and devices that perform the methods and/or that use the computer readable media.
These and other embodiments of the invention are described in further detail below.
Embodiments of the invention are directed to a method of providing, on a consumer's notification device, a visual representation of purchase offers targeted to the consumer. A notification is triggered upon detection of an event. Once triggered, a targeted offer, map, and one or more location icons indicating the geographic locations for redeeming the targeted offer are determined and delivered as a notification to the notification device if the consumer is enrolled to receive the notification. The map and location icons of the notification are displayed on the consumer's notification device. The visual representation of the redemption location on a map enables the consumer to quickly ascertain where the offer can be redeemed.
Certain embodiments of the invention may provide one or more technical advantages to merchants and consumers. One technical advantage is that the consumer is shown the geographic location (geo-location) of a location (i.e., redemption location) where the targeted offer can be redeemed. The consumer need not know or research all of the locations where the targeted offer can be redeemed. As described herein, a consumer is provided with a notification that includes a targeted offer and graphic representations of a geo-location of a redemption location. For example, a map with a carrot or icon relative to the map that points to the exact physical location where the targeted offer can be redeemed may be provided. The visual depiction of the redemption location provides the consumer with meaningful information. There is a better chance of the consumer to make a purchase if the redemption locations are known by the consumer.
Another advantage is the timeliness of the targeted offer. Targeted offers are generated based on the most up-to-date historical purchasing data available for each individual consumer. As such, the targeted offers are directly relevant to consumer's current spending habits and preferences. Various prior art systems require merchants to provide transaction data to the system generating the offers. Typically, the transaction data is sent only on a monthly or quarterly basis. Thus, the offers are generated based on stale data which may be irrelevant to the current preferences of the consumer.
Another advantage is the accuracy of the terms of the targeted offer and locations for redemption of the offer. The offer terms may specify particular goods or services as subjects of the offer provided by a merchant, original price of the goods or services, a discounted price, etc. By interfacing with the merchant systems when generating the targeted offer, the terms and redemption locations are highly likely to be accurate. For example, a targeted offer may identify a particular item that is the subject of the offer. Redemption locations where the targeted offer can be redeemed may be identified. In one embodiment, the redemption locations are identified by using the merchant system which checks current inventories and stock levels. Where the inventories fall below a threshold at a particular location, that location is not identified as a valid redemption location. As such, consumers are only notified about locations that can actually honor the offer.
Furthermore, by interfacing with the merchant systems, there is little overhead for providing accurate targeted offers and redemption locations. The system generating the targeted offers need not bear the cost of keeping track of the inventories and stock of each physical location of multiple merchants.
Yet another advantage is the ability to take immediate action on the targeted offer using a portable electronic device of the consumer. Actions to be performed on a targeted offer may include one or more of the following: reserve with confirmation, purchase, set for will call, and redeem at checkout using mobile device. The actions may then be immediately acted upon by the payment processing network and the merchant systems. A graphical user interface (GUI) may provide these action options to the consumer thus allowing the consumer to act upon the targeted offer quickly and easily. The consumer need only select an action and the payment processing system immediately fulfills the action. In contrast, typical systems permit offers to be redeemed using mobile devices only for online purchases. In these systems, consumers are required to wait for delivery of the goods purchased using the offer. As described herein, consumers can redeem offers using their portable electronic device and can immediately collect the goods or services at the merchant's physical store location.
Certain embodiments of the invention may include none, some, or all of the above technical advantages. One or more other technical advantages may be readily apparent to one skilled in the art from the figures, descriptions, and claims included herein.
The systems and methods as described herein may be used in the context of payment transactions using payment processing systems, which are configured to process credit and debit card transactions. Further, embodiments of the invention are directed to the use of notification devices, and methods and systems that use them. The notification devices can be used in payment processing systems like those shown in
I. Providing Notification Device with Geo-Location of Targeted Offer
The system 20 includes a merchant 22 and an acquirer 24 associated with the merchant 22. In a typical payment transaction, a consumer 30 may purchase goods or services at the merchant 22 using a portable consumer device 32, such as a credit card. The payment transaction may occur at one or more transaction locations involving merchant 22, portable consumer device 32, and consumer 30. The acquirer 24 can communicate with an issuer 28 via a payment processing network 26, which provides the acquirer 24 with a transaction authorization response. The payment processing network 26 can also provide targeted offers to consumer 30.
As used herein, a targeted offer is an offer to purchase goods, services, or other subjects. Targeted offers may be based on, among other things, one or any combination of the following: purchase history of previous purchases made with a portable consumer device, purchase patterns determined from historical purchase records for a consumer, and the like. Targeted offers may include an item description (product name, size, color, model, manufacturer, etc.), an amount of a discount, limited time price, original price, information about the issuing merchant, expiration date, issue date, restrictions, method of valid redemption, and the like.
Additionally, payment processing network 26 communicates with a notification device 36 via notification module 27, which provides notifications of targeted offers and is responsible for notifying consumers of the possibility of fraudulent transactions and other alerts.
The acquirer 24 is typically a bank that has a merchant account. The issuer 28 may also be a bank, but could also be business entity such as a retail store. Some entities are both acquirers and issuers, and embodiments of the invention include such entities. The issuer 28 may operate a server computer 21, which may have a computer readable medium comprising code for performing the functions that the issuer 28 performs. A database 23 comprising account number information and other information may be operatively coupled to the server computer 21.
The consumer 30 may be an individual, or an organization such as a business that is capable of purchasing goods or services. In one embodiment, consumer 30 may be one or more individuals who are authorized to use portable consumer device 32.
The portable consumer device 32 may be in any suitable form. For example, suitable portable consumer devices can be hand-held and compact so that they can fit into a consumer's wallet and/or pocket (e.g., pocket-sized). They may include smart cards, ordinary credit or debit cards (with a magnetic strip and without a microprocessor), keychain devices (such as the Speedpass™ commercially available from Exxon-Mobil Corp.), etc. Other examples of portable consumer devices include cellular or mobile phones, personal digital assistants (PDAs), pagers, payment cards, security cards, access cards, smart media, transponders, and the like. The portable consumer devices can also be debit devices (e.g., a debit card), credit devices (e.g., a credit card), or stored value devices (e.g., a stored value card).
The portable consumer device 32 may comprise a computer readable medium (CRM) 32(a) and a body 32(b). The computer readable medium 32(a) may be on the body 32(b). The body 32(b) may in the form a plastic substrate, housing, or other structure. The computer readable medium 32(a) may be a memory that stores data and may be in any suitable form. Exemplary computer readable media 32(a) may be in any suitable form including a magnetic stripe, a memory chip, etc. If the portable consumer device 32 is in the form of a card, it may have an embossed region 32(a) which is embossed with a PAN (primary account number).
The payment processing network 26 may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception file services, and clearing and settlement services. An exemplary payment processing network may include VisaNet™. Payment processing networks such as VisaNet™ are able to process credit card transactions, debit card transactions, and other types of commercial transactions. VisaNet™, in particular, includes a VIP system (Visa Integrated Payments system) which processes authorization requests and a Base II system which performs clearing and settlement services.
The payment processing network 26 may also include a mobile targeting module that is responsible for generating offers targeted to a user. According to certain embodiments, the offers can be targeted based upon a location based services (LBS) approach, utilizing prior purchasing activity by a consumer as detected over a payment processing network. Analytical analysis may be performed on the prior purchasing activity to determine purchasing preferences and patterns which in turn can be used to generate the targeted offers. The prior purchasing activity may include all purchase transactions made using portable consumer device 32. The prior purchasing activity may encompass transactions across multiple merchants. This provides an enriched dataset upon which analytical analysis is performed producing more accurate forecasts of purchasing preferences and patterns.
The payment processing network 26 may include a server computer. A “server computer” or “server” is typically a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. In one example, the server computer may be a database server coupled to a Web server. The payment processing network 26 may use any suitable wired or wireless network, including the Internet.
Merchant 22 may also have, or may receive communications from, an access device 34 that can interact with the portable consumer device 32. In
The access devices according to embodiments of the invention can be in any suitable form. Examples of access devices include point of sale (POS) devices, cellular or mobile phones, PDAs, personal computers (PCs), tablet PCs, handheld specialized readers, set-top boxes, electronic cash registers (ECRs), automated teller machines (ATMs), virtual cash registers (VCRs), kiosks, security systems, access systems, and the like.
If the access device 34 is a point of sale terminal, any suitable point of sale terminal may include a reader 34(a), a processor 34(b) and a computer readable medium 34(c). The reader 34(a) may include any suitable contact or contactless mode of operation. For example, exemplary card readers can include RF (radio frequency) antennas, magnetic stripe readers, etc. to interact with the portable consumer device 32.
System 20 also includes notification module 27 for processing notifications. Notification module 27 may include various subsystems which enroll one or more consumers, such as consumer 30, into a program for receiving targeted offers. Notification module 27 may also generate notifications, for example, notifications of targeted offers. These notifications may be generated to include the targeted offer, location icons identifying the locations where the offer can be redeemed, and/or a map upon which the location icons may be displayed. As such, the notifications provide the geo-locations of redemption locations where the offer can be redeemed. Notification module 27 is communicatively coupled to payment processing network 26 and an aggregator 37.
Aggregator 37 collects and forwards notifications from notification module 27 to notification device 36. Aggregator 37 may be an entity or organization that receives and transmits messages to a phone, email account, etc. In some cases, wireless telephone companies may be considered aggregators.
Notification device 36 refers to any suitable device for receiving notifications and for providing the notifications to consumer 30. Notifications refer to communications of information relating to a purchase offer targeted to consumer 30 which is presented on a display of notification device 36. As used herein, a notification includes a targeted offer, a map or other graphic representation of a geographic area, and/or a location icon (i.e., a carrot, marker, etc.) which is a graphical indication of the location where the offer can be redeemed. A targeted offer is in the form of textual information about the terms of the offer.
Notifications may be in any suitable form and may be delivered by any suitable method. Some examples of notifications include a phone call, a voice message, a voicemail message, a short message service (SMS) message, e.g., a text message, an instant messaging (IM) message, an email message, or a periodically updated display on a device. An exemplary embodiment of a notification is a purchase offer targeted to a consumer. The targeted offer is a communication to notify consumer 30 of the terms of the offer.
Notification device 36 may be in any suitable form. For example, suitable notification devices 36 can be hand-held and compact so that they can fit into a consumer's wallet and/or pocket (e.g., pocket-sized). Some examples of notification device 36 include mobile phones (e.g., as shown in
In a typical purchase transaction, the consumer 30 purchases a good or service at the merchant 22 using a portable consumer device 32 such as a credit card. The consumer's portable consumer device 32 can interact with an access device 34 such as a POS (point of sale) terminal at the merchant 22. For example, the consumer 30 may swipe a credit card through an appropriate slot in the POS terminal.
Alternatively, the POS terminal may be a contactless reader, and the portable consumer device 32 may be a contactless device such as a contactless card. In certain embodiments, the portable consumer device may be a mobile device such as shown in
An authorization request message is then forwarded to the acquirer 24. After receiving the authorization request message, the authorization request message is then sent to the payment processing network 26. The payment processing network 26 then forwards the authorization request message to the issuer 28 of the portable consumer device 32.
After the issuer 28 receives the authorization request message, the issuer 28 sends an authorization response message back to the payment processing network 26 to indicate whether or not the current transaction is authorized. The payment processing network 26 then forwards the authorization response message back to the acquirer 24. The acquirer 24 then sends the response message back to the merchant 22.
After the merchant 22 receives the authorization response message, the access device 34 at the merchant 22 may then provide the authorization response message for the consumer 30. The response message may be displayed by the access device 34 or the portable consumer device 32, or may be printed out on a receipt.
At the end of the day, a normal clearing and settlement process can be conducted by the payment processing network 26. A clearing process is a process of exchanging financial details between and acquirer and an issuer to facilitate posting to a consumer's account and reconciliation of the consumer's settlement position.
In one embodiment, payment processing network 26 may monitor and detect an offer event. As used herein, an offer event is an event which triggers the generation of targeted offers. Upon the detection of the offer event, payment processing network 26 may be triggered to generate targeted offers.
Offer events may have any suitable characteristics. In some cases, a targeted offer may be triggered by the initiation or completion of a transaction on an account associated with portable consumer device 32. In another example, targeted offers are generated on a periodic basis and/or on-going basis. Other examples of offer events include the following: a request for a targeted offer initiated by consumer 30 or other suitable entity, and a geographic location of consumer 30, as determined by the geo-location of notification device 36, being within proximity to a target location. In one embodiment, a geo-location of the notification device is compared with a geo-location of a target location, and it may be determined that consumer 30 has traveled in a proximity to the target location based on the comparison. For example, consumer 30 may be physically near a retail shop or location. Payment processing network 26 may be triggered to generate a targeted offer upon detection of consumer's 30 proximity to the retail shop. Offer events may be specified by merchant 22, consumer 30, by default, or other suitable entity. Thus, embodiments of the invention are flexible enough to allow for many types of offer events.
In one embodiment, notification module 27 may be triggered by payment processing network 26 to send a notification of the targeted offer. Notification module 27 receives the targeted offer generated by payment processing network 26. Notification module 27 determines whether consumer 30 should be notified about the targeted offer, and generates and sends a notification to consumer 30 via aggregator 37 and notification device 36.
Some of the embodiments described below may use a payment processing system like the one described above, or any suitable combination of components in the payment processing system.
Device 12 further includes a contactless element 13, typically implemented in the form of a semiconductor chip 13(a) (or other data storage element) with an associated wireless data transfer (e.g., data transmission) element 13(b), such as an antenna. Contactless element 13 is associated with (e.g., embedded within) mobile device 12 and data such as a targeted offer or control instructions transmitted via cellular network may be applied to contactless element 13 by means of contactless element interface 18. Contactless element interface 18 functions to permit the exchange of data and/or control instructions between the mobile device circuitry 19 (and hence the cellular network) and contactless element 13.
Mobile device 12 may also include a secure data space 11, which may be used by the device to store operating parameters and/or other data utilized in operation of the device. The secure data space 11 may be in the form of a chip that is separate and apart from the chip in the contactless element 13, or alternatively, could be a section of memory in the chip that forms part of the contactless element 13. Note that the chip in the contactless element 13 may include data storage capability in the form of a memory that may be accessed via interface 18 to permit the implementation of read, write, and erase functions, for example.
In accordance with still other embodiments, the mobile device may further include a processor 15 and computer readable storage medium 16 for storing code and configured to direct the processor to perform various tasks. For example, the computer readable storage medium may comprise a magnetic disk drive or a flash memory chip.
As discussed below, the computer readable storage medium may contain code that is configured to cause a processor of the portable consumer device to receive and recognize a message including a notification and code that is delivered to the mobile device. The computer readable storage medium may also include code that is configured to decrypt an encrypted message including the code that is received by the mobile device.
Contactless element 13 is capable of transferring and receiving data using a near field communications capability (or near field communications medium) typically in accordance with a standardized protocol or data transfer mechanism (identified as ISO 14443/NFC in the figure). Near field communications capability is a short-range communications capability, such as RFID, Bluetooth™, infra-red, or other data transfer capability that can be used to exchange data between the mobile device 12 and a local apparatus, for example located a point-of-sale of a merchant or another location at which targeted offers are expected to be redeemed. Thus, mobile device 12 is capable of communicating and transferring data and/or control instructions via both cellular network and near field communications capability.
In accordance with certain embodiments, the mobile device further includes a Global Positioning System (GPS) element 17. GPS element 17 is configured to allow determination of the location of the user at any time. In particular, GPS element 17 relies upon signals from a plurality of orbiting satellites in order to allow the user's location to be determined. Location information obtained from the GPS element 17 may in turn be communicated through the antenna to allow monitoring of the user's position.
II. Infrastructure for Providing Geo-Location Notifications for Targeted Offers
Embodiments of the invention are directed to geo-location notifications for targeted offers. In these embodiments of the invention, the system may provide a consumer with a notification about a targeted offer upon occurrence of an offer event. When the notification is viewed, a notification device of the consumer displays a graphical representation of the notification on a map. For example, upon occurrence of an offer event, the system may provide to a phone or other notification device of the consumer, a notification including an offer, a map and/or an icon indicating the location of where the offer can be redeemed. The visual representation of the redemption location on the map enables the consumer to quickly ascertain where the offer can be redeemed. For example, the representation of the geo-location of the notification may indicate to the consumer one or more redemption locations within a five mile proximity to the consumer.
Payment processing network 26 is configured to generate offer information and is communicatively coupled with merchant 22 through acquirer 24. Offer information includes one or more targeted offers and/or geo-locations of locations where the offer(s) can be redeemed. For example, during or after generation of an offer, payment processing network 26 may determine locations where the offer can be redeemed. These redemption locations may be affiliated with merchant 22. For example, the redemption locations may be retail locations of the merchant 22.
In one embodiment, payment processing network 26 sends a request to merchant 22 via acquirer for one or more redemption locations affiliated with merchant 22. Merchant 22 may provide to payment processing network 26 identification (ID) of the one or more redemption locations via acquirer 24. The IDs of the one or more redemption locations may be in the form of a geo-locations of the redemption location or another form of identification. Payment processing network 26 determines the geo-location of the redemption locations using the received IDs. For example, a store ID is received. The store ID may be a number or other unique identifier assigned to a store that is associated with merchant 22. Payment processing network 26 may perform a look-up on a table using the store number as a search key into the table. The table may associate the store number with the geo-location of the redemption location.
In one embodiment, merchant 22 identifies each of its locations where the offer can be redeemed. For example, if a targeted offer presents a red coat for a sale price, merchant 22 may check stock for the red coat at various locations, and identify only those locations that have a minimum stock of the red coat. Since merchant 22 has the most updated information about the inventories and stock of each of its store locations, consumer 30 can trust that the stores identified by merchant 22 will actually honor the targeted offer.
In another embodiment, payment processing network 26 may store the geographic locations of a plurality of merchants. Payment processing network 26 may determine which of the stored redemption locations can redeem the targeted offer. Rules may also be applied to narrow the redemption locations to those which are within a threshold distance from a target location, such as the geo-location or position of consumer 30, a city center, etc. Rules may indicate the threshold distance and may also indicate how the threshold distance is to be further expanded, for example if there are no redemption locations within a default radius from the position of the consumer, the threshold distance may be expanded. The threshold distance may be narrowed, for example if there are too many redemption locations within a default radius. In one embodiment, one or more retail establishments are identified as locations where the offer can be redeemed. Rules may be applied to include only those retail establishments that are within a predetermined proximity to consumer 30. The geographic locations of the narrowed set of retails establishments are determined. Other methods of determining a geo-location of the redemption locations may be used. The offer information is provided by payment processing network 26 to notification module 27.
In one embodiment, notification module 27 may be triggered by payment processing network 26 to send a notification of the targeted offer. Notification module 27 receives the targeted offer generated by payment processing network 26. Notification module 27 determines whether consumer 30 should be notified about the targeted offer.
Notification module 27 includes an enrollment system 210, a notification server 220, a mapping server 230, and a gateway 240. Enrollment system 210 is in communication with consumer 30, payment processing network 26, and notification server 220. Notification server 220 is in communication with gateway 240, mapping server 230, and payment processing network 26. Although enrollment system 210 is shown as being separate from issuer 28, enrollment system 210 can be at issuer 28 in some embodiments.
Before a consumer receives notifications, the consumer can register with enrollment system 210 for enrolling in a targeted offer distribution program. Consumer 30 may register for notifications of targeted offers or update existing notifications in any number of ways. For example, consumer 30 can register via a separate website designed for this purpose, or manually though a paper form (which may be considered a registration interface). Issuer 28 or payment processing network 26 may also enroll consumer 30 automatically for notifications of targeted offers.
Enrollment system 210 receives enrollment information from consumer 30, for example, via a web interface using a computer, or from issuer 28 and may store the enrollment information in a database. Enrollment system 210 may provide the enrollment information to a system which will be detecting the offer event so that the system knows what events to monitor before a targeted offer is generated for consumer 30. The enrollment information may be provided on demand (e.g., when consumer 30 makes a change), periodically (e.g., hourly, daily, etc.), or on an individual request basis, and using a push or pull scheme. In one embodiment, the system detecting the offer event is payment processing network 26. In another embodiment, the system detecting the offer event may be issuer 28.
Enrollment information includes details of offer events that describe the conditions that must take place to trigger the generation of targeted offers, updated enrollment information, and other account information. Consumer 30 may define the offer events when enrolling in a program to receive notifications. In alternative embodiments, the offer events are predetermined by the system, for example, such that consumer 30 can enroll by opting into the notification program with minimal input.
The enrollment information may also specify the types of offers that consumer 30 is interested in receiving. For example, consumer 30 may indicate an interest in receiving offers from particular merchants, such as Starbucks®. Consumer 30 may indicate preferences in receiving offers for certain products, such as coffee. Types of offers may be specified in various other ways.
Notification server 220 generates and processes notifications with graphic representations of a geo-location of a targeted offer and is in communication with payment processing network 26, enrollment server 210, mapping server 230, and gateway 240. Notification server 220 may receive offer information from payment processing network 26. As previously described, offer information includes one or more targeted offers and/or geo-locations of redemption locations.
In embodiments of the invention, notification server 220 and/or a server in the payment processing network 26 may comprise a processor, and a computer readable medium. The computer readable medium may comprise code executable by the processor. The code may comprise (i) code for monitoring for an event to trigger a targeted offer, (ii) code for generating the offer upon detection of the event, the offer targeted to a consumer, wherein the offer is generated using payment data generated in response to transactions conducted by the consumer with a plurality of different merchants, (iii) determining a geographic location for redeeming the offer, (iv) generating a notification message about the offer, the notification message including the offer and the geographic location for redeeming the offer, and (iv) code for sending the notification message to a notification device operated by the consumer, wherein a graphical depiction of the offer is displayed on a map on the notification device based on the notification message.
Notification server 220 may determine whether consumer 30 would like to be notified about the targeted offer by communicating with enrollment system 210, generate the notification messages, and send the notification messages through gateway 240 to aggregator 37. In other words, notification module 27 determines whether a notification message about the targeted offer is required. For example, it is determined whether consumer 30 has enrolled in the notification program and whether the offer is a type of offer that consumer 30 would like to be notified about. Notification messages may then be sent to consumer 30 upon determining that the notification message is required. A geo-location of the redemption location is extracted from the offer information and is provided to mapping server 230. Mapping information is received from mapping server 230. As used herein, mapping information includes a map or other graphic representation of a geographic area and/or a location icon (i.e., a carrot, marker, etc.) which is a graphical indication of the location where the offer can be redeemed. The notification message (notification) may be generated including the offer and/or mapping information. For example, a notification may be generated using only the offer and another notification may be generated with the mapping information.
Mapping server 230 provides mapping information and is in communication with notification server 220. The communication may occur through an appropriately configured network, such as the internet, and one or more private networks, such as a cellular data network. Mapping server 230 may receive a message including geo-locations, interpret the message to extract geo-locations, convert the geo-locations into a common format, and provide mapping information to notification server 220. Mapping information may include a map with a graphic representation of a geo-location of a redemption location, such as a map and/or a location icon.
Mapping server 230 includes a map generator 235 which selects map tiles which encompass the geo-locations and generates a location icon to be overlaid on a map in the correct location. In one embodiment, maps are broken-down into smaller components, i.e., map tiles. The location icon is an object on the map that is tied to latitude/longitude coordinates of the map. The location icon may be used to indicate the point in the map representing the geo-locations. For example, if the geo-location of a merchant's retail store is provided, map generator may select one or more map tiles and may generate a graphical location icon (i.e., a carrot, marker, etc.) to point to the exact location of the merchant's retail store on the map. In one embodiment, the received (or extracted or otherwise determined) geo-location may not only represent the location of the transaction, but may also represent the location of notification device 36 in the form of a consumer icon. A consumer icon, which is a type of location icon, may be generated such that, for example, consumer 30 may visually compare on the map the location of the targeted offer relative to the current geographic location of consumer 30. The geographic location of the consumer may be determined by a geographic location of notification device 36, for example using a global positioning system (GPS) element in the notification device. The map may include multiple location icons which identify multiple retail stores that can redeem the targeted offer. Consumer 30 can use the map to quickly and easily ascertain which retail store is closest to his current position or otherwise most convenient by visually comparing the distance between the location icons and the consumer icon.
Notification server 220 may send the notifications through gateway 240 to aggregator 37. Gateway 140 is any suitable device that converts information from the protocol or format used in notification module 27 to those used in aggregator 37. Gateway 260 may be embodied by a computer or a network that allows or controls access to another computer or network. Gateway 260 may also be a software interface between the computer or network and another computer or network. As previously mentioned, aggregator 37 refers to any suitable entity or device that receives notifications, and collects and transmits the notifications to notification device 36 for consumer 30.
As previously mentioned, notification device 36 refers to any suitable device for receiving notifications and for providing the notifications to consumer 30. Notification device 36 may be in communication with payment processing network 26. In one embodiment, where the notification includes the targeted offer but does not include the mapping information, notification device 36 may include an interface to enable consumer 30 to select a notification and to send a request for mapping information for the selected notification to notification server 220 via payment processing network 26. Notification device 36 may then receive the requested mapping information from notification server 220 via gateway 240 and aggregator 37.
At step S2, it is determined whether an offer event has been detected, for example after monitoring for the offer event(s). As previously discussed, the detection of an offer event triggers the generation of a targeted offer. For example, payment processing network 26 may detect the offer event and may generate the targeted offer. At step S3, if offer events are not detected, processing ends.
If the offer event has been detected, the targeted offer is determined and one or more locations for redeeming the targeted offer are also determined at step S4. Typically, payment processing network 26 generates targeted offers based on consumer 30 payment data (i.e., purchasing history) as determined by past purchases made by consumer 30 or made using a portable consumer device 32 associated with consumer 30. In order to provide offers which are truly relevant to consumer 30, the payment data is generated in response to transactions conducted by consumer 30 with a plurality of different merchants. The targeted offers also may be generated using any combination of the following: consumer ID, consumer name/address, consumer demographics, date/time, consumer proximity to the merchant's location, and consumer preferences, such as those identified via enrollment. In one embodiment, the payment data is collected by a payment processing network.
The one or more redemption locations can be determined in various ways. Merchant 22 (who is associated with the offer) may identify the redemption locations. Alternatively, payment processing network 26 may identify the locations where the offer can be redeemed.
In one embodiment, the geo-location of the one or more redemption locations is determined. This information may be provided by merchant 22, determined by retrieving the geo-location from a data store, or any other similar method. In yet another embodiment, the geo-location of consumer 30 or portable consumer device 32 which was used in a transaction which triggered the generation of the targeted offer may be used for the geo-location of the redemption location. Offer information can be generated to include the targeted offer and/or the geo-locations of redemption locations.
A map with a graphic representation of a geo-location of the targeted offer is determined at step S5. Using the offer information, a map may be generated with a location icon, such as a carrot or marker, which points to or otherwise identifies the geo-location(s) of the one or more redemption locations. For example, the location icon may graphically indicate the particular store where the targeted offer may be redeemed. In one embodiment, the location icon is embedded within the map. In another embodiment, the location icon is a separate object which is intended to overlay the map and is tied to latitude/longitude coordinates on the map. The metes and bounds of the map may be limited to representation of a relative vicinity of a present geo-location or position of consumer 30 and the location icon(s) fitting within these metes and bounds may be included.
At step S6, a notification including the map is sent to a consumer notification device. For example, the notification may be sent to notification device 36 belonging to consumer 30. The notification message (notification) may be generated including the offer and/or map and location icons. For example, a first notification may be generated including only the offer and a second notification may be generated including the map and location icons. The consumer may select the offer in the first notification, and the selection may trigger the generation of the second notification with the map and location icons, which may then be displayed on the notification device of the consumer. A graphical depiction of the notification or offer is displayed on a map on the notification device based on the notification message.
Maps may include multiple location icons indicating a plurality of the most current locations where the selected notification can be redeemed. Location icons may also indicate the consumer's present location such that, for example, consumer 30 may visually compare on the map the redemption location relative to the current position of the consumer 30 (for example as determined by a geographic location of notification device 36). For example, location icon 445 may be a consumer icon or carrot showing the consumer's present location, as determined for example by a GPS location of the notification device 440.
III. Notification Infrastructure Supporting Actions to be Performed on a Notification
In addition to providing near-real time notifications for targeted offers, methods and systems as described herein enable consumers to act on those notifications quickly and easily. For example, consumers may select actions to be performed on a notification (and/or associated offer) after receiving the notification on a PDA. In one embodiment, the actions provide options to the consumer for various ways to redeem the targeted offer. A GUI may be provided to the consumer including a list of selectable actions. Actions to be performed on a targeted offer may include one or more of the following: reserve with confirmation, purchase, set for will call, and redeem at checkout using mobile device. The consumer need only select an action and the payment processing system immediately fulfills the action. Consumers can redeem offers using their portable electronic device and can immediately collect the goods or services at a physical store location.
In one embodiment, the actions may be customized. For example, actions may be context-specific and/or consumer-specific. Consumer 30 enrolls in the program to receive notifications on notification device 36. Consumer 30 may send enrollment information to enrollment system 210. The enrollment information may specify the types of actions that consumer 30 would like to enable. Actions may be specified in various ways. Actions may be specified based on any attribute/characteristic of an offer. For example, consumer 30 may set actions to be performed for all offer types. In another embodiment, one set of actions may be set out for offers for goods and another set of actions may be set out for offers for services. In an alternative embodiment, a default set of actions may be provided.
Customized actions may be determined by notification module 27 and communicated to notification device 36. For example, when notification module 27 is triggered to generate a notification, notification server 220 may determine from enrollment system 210 one or more customized actions associated with a targeted offer and may embed a list of the customized actions within the notification itself.
It may be desirable to allow a consumer to reserve the subject of the targeted offer (i.e., goods or services) and to receive a confirmation that the reservation has been accepted. For example, consumer 30 may receive a notification of an offer for a dozen red roses from 1-800-Flowers®. Consumer 30 may select the “Reserve with Confirmation” action to be applied to a selected location for redeeming the 1-800-Flowers® offer. Payment processing network 240 may distribute the action, selected notification, and/or the selected location to merchant reservation system 520 for fulfillment. A message may be provided to a system of merchant 22 for reserving the subject of the targeted offer.
Upon receipt of a “Purchase” action to be applied to one or more selected notifications, payment processing network 240 may distribute the action, selected notifications, and/or selected redemption locations to transaction processing system 510 for fulfillment, which may activate channels to engage in a purchase transaction. In one embodiment, the consumer's notification device is used to purchase the goods or services that are the subjects of the targeted offer. Transaction processing system 510 may send a message to a system of merchant 22 for purchasing the subject of the offer.
For example, the consumer's notification device can engage in a purchase transaction with the selected redemption location of merchant 22. The consumer may then go to the physical location to take possession of the subject of the offer. In one embodiment, the purchase transaction is completed, and as such, the consumer does not need to engage in any further purchase transactions at the redemption location. Other known methods of purchasing a selected good or service may also be implemented without departing from the scope of the invention.
Upon receipt of a “Will Call” action to be applied to one or more selected notifications, payment processing network 240 may distribute the action, selected notifications, and/or selected redemption locations to merchant reservation system 520 for fulfillment, which may activate channels to place the subject of the offer at Will Call in a redemption location.
Upon receipt of a “Redeem at Checkout using Mobile Device” action to be applied to one or more selected notifications, payment processing network 240 may distribute the action, selected notifications, and/or selected redemption locations to merchant reservation system 520 for fulfillment.
Through the GUI of the notification device, the consumer may select one or more of the received notifications and/or locations where the targeted offer can be redeemed. An action to be applied to the selected notifications and/or redemption locations is received. Notification device 36 may receive these selections in steps 620 and 630.
At step 640, a system or module to fulfill the selected action is determined. The determination may be made based on an association among actions and fulfillment systems or modules. In one embodiment, payment processing network 26 distributes the selected notification(s) to a system or module based on the action selected. Other methods of distribution are also contemplated. At step 650, the selected notification(s), selected action, and/or redemption location(s) are provided to the system or module for fulfillment. In one embodiment, fulfillment of the action may be achieved by communication with the merchant.
The redemption of offers can be time consuming, and often requires skill on the part of the cashier to actually redeem the offer, for example, by entering offer codes, providing redemption codes, etc. If the cashier of merchant 22 does not have the requisite skill, the time required to redeem the offer becomes obtrusive for the consumer. It may be desirable to expedite or otherwise streamline the checkout process by which consumers can redeem their targeted offers and make purchases of goods and services. Moreover, an untrained cashier may enter an incorrect code causing disruption to the merchant's records.
In one embodiment, the consumer can select the “Redeem at Checkout using Mobile Device” action causing, for example, merchant reservation system 520 to interface with merchant 22 and to provide a reconciliation process that does not involve the store clerk or cashier. Merchant 22 is made aware that the consumer has accepted the targeted offer. For example, a message is sent to merchant 22 to associate the consumer with the terms of the offer. When consumer 30 approaches the cashier to redeem the offer, the cashier does not need to perform any functions beyond that of a typical purchase transaction. For example, the cashier may scan a barcode for an item that is the subject of the targeted offer. The backend system of the merchant automatically adjusts the price based on the acceptance of the offer. In one embodiment, the access device (such as a point of sale device) of merchant 22 automatically present to the associated consumer 30, a purchase price according to the terms of the offer. The cashier need not take other actions to redeem the offer for consumer 30. In one embodiment, the backend system of the merchant authorizes the redeemer as consumer 30 who accepted the targeted offer.
Any of the server computers, client computers, and even some portable consumer devices described above may utilize any suitable number of subsystems. Examples of such subsystems or components are shown in
Any of the software components or functions described in this application, may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions, or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM. Any such computer readable medium may reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network.
The above description is illustrative and is not restrictive. Many variations of the invention will become apparent to those skilled in the art upon review of the disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents.
One or more features from any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the invention.
A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary.
It should be understood that the present invention as described above can be implemented in the form of control logic using computer software in a modular or integrated manner. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know and appreciate other ways and/or methods to implement the present invention using hardware and a combination of hardware and software.
The present application is a continuation of U.S. application Ser. No. 15/363,311, filed Nov. 29, 2016, which is a continuation of Ser. No. 12/491,139, filed on Jun. 24, 2009, now U.S. Pat. No. 9,542,687, issued Jan. 10, 2017 which claims priority to U.S. Provisional Application No. 61/076,099, filed on Jun. 26, 2008, the entire contents of which are herein incorporated by reference for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
3356021 | May et al. | Dec 1967 | A |
4044231 | Beck et al. | Aug 1977 | A |
4461861 | Loffelman et al. | Jul 1984 | A |
4528442 | Endo | Jul 1985 | A |
4613904 | Lurie | Sep 1986 | A |
4674041 | Lemon et al. | Jun 1987 | A |
4701601 | Francini et al. | Oct 1987 | A |
4868376 | Lessin et al. | Sep 1989 | A |
5034597 | Atsumi et al. | Jul 1991 | A |
5305196 | Deaton et al. | Apr 1994 | A |
5311594 | Penzias | May 1994 | A |
5327508 | Deaton et al. | Jul 1994 | A |
5353218 | Delapa et al. | Oct 1994 | A |
5359183 | Skodlar | Oct 1994 | A |
5388165 | Deaton et al. | Feb 1995 | A |
RE34915 | Nichtberger et al. | Apr 1995 | E |
5420606 | Begum et al. | May 1995 | A |
5420926 | Low et al. | May 1995 | A |
5430644 | Deaton et al. | Jul 1995 | A |
5448471 | Deaton et al. | Sep 1995 | A |
5465206 | Hilt et al. | Nov 1995 | A |
5477038 | Levine et al. | Dec 1995 | A |
5483444 | Heintzeman et al. | Jan 1996 | A |
5500513 | Langhans et al. | Mar 1996 | A |
5502636 | Clarke | Mar 1996 | A |
5513250 | McAllister | Apr 1996 | A |
5530438 | Bickham et al. | Jun 1996 | A |
5564073 | Takahisa | Oct 1996 | A |
5577266 | Takahisa et al. | Nov 1996 | A |
5579537 | Takahisa | Nov 1996 | A |
5592560 | Deaton et al. | Jan 1997 | A |
5604921 | Alanara | Feb 1997 | A |
5615110 | Wong | Mar 1997 | A |
5621201 | Langhans et al. | Apr 1997 | A |
5621812 | Deaton et al. | Apr 1997 | A |
5627549 | Park | May 1997 | A |
5638457 | Deaton et al. | Jun 1997 | A |
5642485 | Deaton et al. | Jun 1997 | A |
5644723 | Deaton et al. | Jul 1997 | A |
5649114 | Deaton et al. | Jul 1997 | A |
5659165 | Jennings et al. | Aug 1997 | A |
5659469 | Deaton et al. | Aug 1997 | A |
5675662 | Deaton et al. | Oct 1997 | A |
5678939 | Ross | Oct 1997 | A |
5679938 | Templeton et al. | Oct 1997 | A |
5679940 | Templeton et al. | Oct 1997 | A |
5687322 | Deaton et al. | Nov 1997 | A |
5708422 | Blonder et al. | Jan 1998 | A |
5710886 | Christensen et al. | Jan 1998 | A |
5717866 | Naftzger | Feb 1998 | A |
5761648 | Golden et al. | Jun 1998 | A |
5774525 | Kanevsky et al. | Jun 1998 | A |
5777903 | Piosenka et al. | Jul 1998 | A |
5791991 | Small | Aug 1998 | A |
5793972 | Shane | Aug 1998 | A |
5806044 | Powell | Sep 1998 | A |
5822735 | De Lapa et al. | Oct 1998 | A |
5852775 | Hidary | Dec 1998 | A |
5855007 | Jovicic et al. | Dec 1998 | A |
5870030 | Deluca et al. | Feb 1999 | A |
5872834 | Teitelbaum | Feb 1999 | A |
5878337 | Joao et al. | Mar 1999 | A |
5884277 | Khosla | Mar 1999 | A |
5903830 | Joao et al. | May 1999 | A |
5903878 | Talati et al. | May 1999 | A |
5905246 | Fajkowski | May 1999 | A |
5907830 | Engel et al. | May 1999 | A |
5914472 | Foladare et al. | Jun 1999 | A |
5924080 | Johnson | Jul 1999 | A |
5959577 | Fan et al. | Sep 1999 | A |
5974399 | Giuliani et al. | Oct 1999 | A |
5988497 | Wallace | Nov 1999 | A |
5991749 | Morrill, Jr. | Nov 1999 | A |
5991750 | Watson | Nov 1999 | A |
5995823 | Stephens | Nov 1999 | A |
6002771 | Nielsen | Dec 1999 | A |
6003326 | Hensley | Dec 1999 | A |
6009411 | Kepecs | Dec 1999 | A |
6009415 | Shurling et al. | Dec 1999 | A |
6012038 | Powell | Jan 2000 | A |
6012144 | Pickett | Jan 2000 | A |
6014634 | Scroggie et al. | Jan 2000 | A |
6018718 | Walker et al. | Jan 2000 | A |
6029151 | Nikander | Feb 2000 | A |
6035280 | Christensen | Mar 2000 | A |
6041309 | Laor | Mar 2000 | A |
6049778 | Walker et al. | Apr 2000 | A |
6052675 | Checchio | Apr 2000 | A |
6055505 | Elston | Apr 2000 | A |
6055570 | Nielsen | Apr 2000 | A |
6062991 | Moriarty et al. | May 2000 | A |
6064990 | Goldsmith | May 2000 | A |
6067526 | Powell | May 2000 | A |
6067529 | Ray et al. | May 2000 | A |
6076068 | DeLapa et al. | Jun 2000 | A |
6076069 | Laor | Jun 2000 | A |
6076101 | Kamakura et al. | Jun 2000 | A |
6081792 | Cucinotta et al. | Jun 2000 | A |
6095413 | Tetro et al. | Aug 2000 | A |
6122624 | Tetro et al. | Sep 2000 | A |
6128599 | Walker et al. | Oct 2000 | A |
6185290 | Shaffer et al. | Feb 2001 | B1 |
6185541 | Scroggie et al. | Feb 2001 | B1 |
6195542 | Griffith | Feb 2001 | B1 |
6219793 | Li et al. | Apr 2001 | B1 |
6227447 | Campisano | May 2001 | B1 |
6237145 | Narasimhan et al. | May 2001 | B1 |
6247129 | Keathley et al. | Jun 2001 | B1 |
6263447 | French et al. | Jul 2001 | B1 |
6267292 | Walker et al. | Jul 2001 | B1 |
6279112 | O'Toole, Jr. et al. | Aug 2001 | B1 |
6292786 | Deaton et al. | Sep 2001 | B1 |
6307958 | Deaton et al. | Oct 2001 | B1 |
6311169 | Duhon | Oct 2001 | B2 |
6317718 | Fano | Nov 2001 | B1 |
6318631 | Halperin | Nov 2001 | B1 |
6321208 | Barnett et al. | Nov 2001 | B1 |
6330543 | Kepecs | Dec 2001 | B1 |
6330550 | Brisebois et al. | Dec 2001 | B1 |
6334108 | Deaton et al. | Dec 2001 | B1 |
6336098 | Fortenberry et al. | Jan 2002 | B1 |
6336099 | Barnett et al. | Jan 2002 | B1 |
6341724 | Campisano | Jan 2002 | B2 |
6351735 | Deaton et al. | Feb 2002 | B1 |
6353398 | Amin et al. | Mar 2002 | B1 |
6377935 | Deaton et al. | Apr 2002 | B1 |
6378775 | Hayashida | Apr 2002 | B2 |
6381324 | Shaffer et al. | Apr 2002 | B1 |
6424949 | Deaton et al. | Jul 2002 | B1 |
6424951 | Shurling et al. | Jul 2002 | B1 |
6434534 | Walker et al. | Aug 2002 | B1 |
6470181 | Maxwell | Oct 2002 | B1 |
6484146 | Day et al. | Nov 2002 | B2 |
6484148 | Boyd | Nov 2002 | B1 |
6488203 | Stoutenburg et al. | Dec 2002 | B1 |
6488206 | Flaig et al. | Dec 2002 | B1 |
6496936 | French et al. | Dec 2002 | B1 |
6505046 | Baker | Jan 2003 | B1 |
6516302 | Deaton et al. | Feb 2003 | B1 |
6529725 | Joao et al. | Mar 2003 | B1 |
6535855 | Cahill et al. | Mar 2003 | B1 |
6553100 | Chen et al. | Apr 2003 | B1 |
6560581 | Fox et al. | May 2003 | B1 |
6571279 | Herz et al. | May 2003 | B1 |
6584309 | Whigham | Jun 2003 | B1 |
6587835 | Treyz et al. | Jul 2003 | B1 |
6594376 | Hoffman et al. | Jul 2003 | B2 |
6601759 | Fife et al. | Aug 2003 | B2 |
6608556 | De Moerloose et al. | Aug 2003 | B2 |
6609104 | Deaton et al. | Aug 2003 | B1 |
6611811 | Deaton et al. | Aug 2003 | B1 |
6612488 | Suzuki | Sep 2003 | B2 |
6631849 | Blossom | Oct 2003 | B2 |
6647257 | Owensby | Nov 2003 | B2 |
6647269 | Hendrey et al. | Nov 2003 | B2 |
6664948 | Crane et al. | Dec 2003 | B2 |
6684195 | Deaton et al. | Jan 2004 | B1 |
6685093 | Challa et al. | Feb 2004 | B2 |
6715672 | Tetro et al. | Apr 2004 | B1 |
6736322 | Gobburu et al. | May 2004 | B2 |
6741188 | Miller et al. | May 2004 | B1 |
6747547 | Benson | Jun 2004 | B2 |
6749118 | Kobayashi et al. | Jun 2004 | B2 |
RE38572 | Tetro et al. | Aug 2004 | E |
6775539 | Deshpande | Aug 2004 | B2 |
6813606 | Veyama et al. | Nov 2004 | B2 |
6823318 | Creswell et al. | Nov 2004 | B1 |
6832721 | Fujii | Dec 2004 | B2 |
6837425 | Gauthier et al. | Jan 2005 | B2 |
6857073 | French et al. | Feb 2005 | B2 |
6862575 | Anttila et al. | Mar 2005 | B1 |
6868391 | Hultgren | Mar 2005 | B1 |
6877661 | Webb et al. | Apr 2005 | B2 |
6877665 | Challa et al. | Apr 2005 | B2 |
6879838 | Rankin et al. | Apr 2005 | B2 |
6883708 | Fiedler et al. | Apr 2005 | B1 |
6912398 | Domnitz | Jun 2005 | B1 |
6913194 | Suzuki | Jul 2005 | B2 |
6920611 | Spaeth et al. | Jul 2005 | B1 |
6948656 | Williams | Sep 2005 | B2 |
6842774 | Piccioni | Nov 2005 | B1 |
6968180 | Kirby et al. | Nov 2005 | B2 |
6970850 | Freeny, Jr. | Nov 2005 | B1 |
6975852 | Sofer et al. | Dec 2005 | B1 |
6982941 | Yamanoi et al. | Jan 2006 | B2 |
6988657 | Singer et al. | Jan 2006 | B1 |
6990330 | Voerepalli et al. | Jan 2006 | B2 |
6993326 | Link, II et al. | Jan 2006 | B2 |
7003497 | Maes | Jan 2006 | B2 |
7007840 | Davis | Mar 2006 | B2 |
7013286 | Aggarwal et al. | Mar 2006 | B1 |
7014107 | Singer et al. | Mar 2006 | B2 |
7024211 | Martin | Apr 2006 | B1 |
7024374 | Day et al. | Apr 2006 | B1 |
7025256 | Drummond et al. | Apr 2006 | B1 |
7027801 | Hall et al. | Apr 2006 | B1 |
7028052 | Chapman et al. | Apr 2006 | B2 |
7028906 | Challa et al. | Apr 2006 | B2 |
7039423 | Daniel et al. | May 2006 | B2 |
7039611 | Devine | May 2006 | B2 |
7040533 | Ramachandran | May 2006 | B1 |
7051923 | Nguyen et al. | May 2006 | B2 |
7055031 | Platt | May 2006 | B2 |
7058611 | Kranzley et al. | Jun 2006 | B2 |
7069001 | Rupp et al. | Jun 2006 | B2 |
7076329 | Kolls | Jul 2006 | B1 |
7089208 | Levchin et al. | Aug 2006 | B1 |
7092724 | Fellenstein et al. | Aug 2006 | B2 |
7096003 | Joao et al. | Aug 2006 | B2 |
7099850 | Mann et al. | Aug 2006 | B1 |
7100821 | Rasti | Sep 2006 | B2 |
7104446 | Bortolin et al. | Sep 2006 | B2 |
7107250 | Harrison | Sep 2006 | B2 |
7110954 | Yung et al. | Sep 2006 | B2 |
7121456 | Spaeth et al. | Oct 2006 | B2 |
7124937 | Myers et al. | Oct 2006 | B2 |
7136841 | Cook | Nov 2006 | B2 |
7150393 | Drummond et al. | Dec 2006 | B1 |
7152780 | Gauthier et al. | Dec 2006 | B2 |
7152788 | Williams | Dec 2006 | B2 |
7159770 | Onozu et al. | Jan 2007 | B2 |
7167711 | Dennis | Jan 2007 | B1 |
7194437 | Britto et al. | Mar 2007 | B1 |
7201313 | Ramachandran | Apr 2007 | B1 |
7203300 | Shaffer et al. | Apr 2007 | B2 |
7207477 | Ramachandran | Apr 2007 | B1 |
7213755 | Newsome et al. | May 2007 | B2 |
7225156 | Fisher et al. | May 2007 | B2 |
7231357 | Shanman | Jun 2007 | B1 |
7231372 | Prange et al. | Jun 2007 | B1 |
7231657 | Honarvar et al. | Jun 2007 | B2 |
7236799 | Wilson et al. | Jun 2007 | B2 |
RE39736 | Morrill, Jr. | Jul 2007 | E |
7243853 | Levy et al. | Jul 2007 | B1 |
7251624 | Lee et al. | Jul 2007 | B1 |
7257545 | Hung | Aug 2007 | B1 |
7264154 | Harris | Sep 2007 | B2 |
7280981 | Huang et al. | Oct 2007 | B2 |
7290704 | Ball et al. | Nov 2007 | B1 |
7292996 | Nobrega et al. | Nov 2007 | B2 |
7308254 | Rissanen | Dec 2007 | B1 |
7310534 | Northcutt | Dec 2007 | B2 |
7343149 | Benco et al. | Mar 2008 | B2 |
7343317 | Jokinen et al. | Mar 2008 | B2 |
7349668 | Ilan et al. | Mar 2008 | B2 |
7350702 | Bortolin et al. | Apr 2008 | B2 |
7353187 | Emodi et al. | Apr 2008 | B1 |
7356516 | Richey et al. | Apr 2008 | B2 |
7357310 | Calabrese et al. | Apr 2008 | B2 |
7376431 | Niedermeyer | May 2008 | B2 |
7407094 | Myers et al. | Aug 2008 | B2 |
7440771 | Purk | Oct 2008 | B2 |
7447662 | Gibson | Nov 2008 | B2 |
7464867 | Kolls | Dec 2008 | B1 |
7653599 | Doran et al. | Jan 2010 | B2 |
7857212 | Matthews | Dec 2010 | B1 |
7912193 | Chingon et al. | Mar 2011 | B2 |
8000726 | Altman et al. | Aug 2011 | B2 |
8073461 | Altman et al. | Dec 2011 | B2 |
8489452 | Warner et al. | Jul 2013 | B1 |
8682793 | Carlson | Mar 2014 | B2 |
9105032 | Altberg | Aug 2015 | B2 |
20010013542 | Horowitz et al. | Aug 2001 | A1 |
20010029485 | Brody et al. | Oct 2001 | A1 |
20010049636 | Hudda et al. | Dec 2001 | A1 |
20020013711 | Ahuja et al. | Jan 2002 | A1 |
20020062249 | Iannacci et al. | May 2002 | A1 |
20020065713 | Awada et al. | May 2002 | A1 |
20020077964 | Brody et al. | Jun 2002 | A1 |
20020087460 | Hornung | Jul 2002 | A1 |
20020091569 | Kitaura et al. | Jul 2002 | A1 |
20020091945 | Ross | Jul 2002 | A1 |
20020102993 | Hendrey et al. | Aug 2002 | A1 |
20020107027 | O'Neil | Aug 2002 | A1 |
20020108062 | Nakajima et al. | Aug 2002 | A1 |
20020111852 | Levine | Aug 2002 | A1 |
20020128903 | Kernahan | Sep 2002 | A1 |
20020133462 | Shteyn | Sep 2002 | A1 |
20020140542 | Prokoski et al. | Oct 2002 | A1 |
20020156677 | Peters et al. | Oct 2002 | A1 |
20020160761 | Wolfe | Oct 2002 | A1 |
20020161647 | Gailey et al. | Oct 2002 | A1 |
20020161701 | Warmack | Oct 2002 | A1 |
20020165775 | Tagseth et al. | Nov 2002 | A1 |
20020169713 | Chang et al. | Nov 2002 | A1 |
20020169719 | Dively et al. | Nov 2002 | A1 |
20020190118 | Davenport et al. | Dec 2002 | A1 |
20020198777 | Yuasa | Dec 2002 | A1 |
20030004802 | Callegari | Jan 2003 | A1 |
20030004808 | Elhaoussine et al. | Jan 2003 | A1 |
20030006911 | Smith et al. | Jan 2003 | A1 |
20030058261 | Challa et al. | Mar 2003 | A1 |
20030061163 | Durfield | Mar 2003 | A1 |
20030061211 | Shultz et al. | Mar 2003 | A1 |
20030062214 | Smith et al. | Apr 2003 | A1 |
20030105707 | Audebert et al. | Jun 2003 | A1 |
20030120502 | Robb | Jun 2003 | A1 |
20030120593 | Bansal et al. | Jun 2003 | A1 |
20030126078 | Vihinen | Jul 2003 | A1 |
20030126095 | Allen | Jul 2003 | A1 |
20030135463 | Brown et al. | Jul 2003 | A1 |
20030144907 | Cohen et al. | Jul 2003 | A1 |
20030154126 | Gehlot et al. | Aug 2003 | A1 |
20030163359 | Kanesaka | Aug 2003 | A1 |
20030172040 | Kemper et al. | Sep 2003 | A1 |
20030182191 | Oliver et al. | Sep 2003 | A1 |
20030201500 | Furukawa et al. | Oct 2003 | A1 |
20030208406 | Okamoto et al. | Nov 2003 | A1 |
20030208684 | Camacho et al. | Nov 2003 | A1 |
20030212595 | Antonucci | Nov 2003 | A1 |
20030212642 | Weller et al. | Nov 2003 | A1 |
20030220835 | Barnes, Jr. | Nov 2003 | A1 |
20030220843 | Lam | Nov 2003 | A1 |
20030222134 | Boyd | Dec 2003 | A1 |
20030225618 | Hessburg et al. | Dec 2003 | A1 |
20030230630 | Whipple et al. | Dec 2003 | A1 |
20030233292 | Richey et al. | Dec 2003 | A1 |
20040004117 | Suzuki | Jan 2004 | A1 |
20040019522 | Bortolin et al. | Jan 2004 | A1 |
20040024638 | Restis | Feb 2004 | A1 |
20040030607 | Gibson | Feb 2004 | A1 |
20040039691 | Barratt et al. | Feb 2004 | A1 |
20040044621 | Huang et al. | Mar 2004 | A1 |
20040049455 | Mohsenzadeh | Mar 2004 | A1 |
20040050922 | Gauthier et al. | Mar 2004 | A1 |
20040054575 | Marshall | Mar 2004 | A1 |
20040054581 | Redford et al. | Mar 2004 | A1 |
20040054590 | Redford et al. | Mar 2004 | A1 |
20040054591 | Spaeth et al. | Mar 2004 | A1 |
20040064403 | Hasumi et al. | Apr 2004 | A1 |
20040064406 | Yates et al. | Apr 2004 | A1 |
20040078340 | Evans | Apr 2004 | A1 |
20040093274 | Vanska et al. | May 2004 | A1 |
20040103049 | Kerr | May 2004 | A1 |
20040117254 | Nemirofsky et al. | Jun 2004 | A1 |
20040133653 | Defosse et al. | Jul 2004 | A1 |
20040137886 | Ross et al. | Jul 2004 | A1 |
20040139021 | Reed et al. | Jul 2004 | A1 |
20040148224 | Gauthier et al. | Jul 2004 | A1 |
20040148253 | Shin et al. | Jul 2004 | A1 |
20040153715 | Spaeth et al. | Aug 2004 | A1 |
20040158534 | Zahir Azami et al. | Aug 2004 | A1 |
20040199470 | Ferry et al. | Oct 2004 | A1 |
20040201500 | Miller et al. | Oct 2004 | A1 |
20040220964 | Shiftan et al. | Nov 2004 | A1 |
20040243519 | Perttila et al. | Dec 2004 | A1 |
20040254848 | Golan et al. | Dec 2004 | A1 |
20040254868 | Kirkland | Dec 2004 | A1 |
20040260653 | Tsuei et al. | Dec 2004 | A1 |
20050015300 | Smith et al. | Jan 2005 | A1 |
20050021400 | Postrel | Jan 2005 | A1 |
20050021456 | Steele et al. | Jan 2005 | A1 |
20050027543 | Labrou | Feb 2005 | A1 |
20050029344 | Davis | Feb 2005 | A1 |
20050035847 | Bonalle et al. | Feb 2005 | A1 |
20050036611 | Seaton et al. | Feb 2005 | A1 |
20050045718 | Bortolin et al. | Mar 2005 | A1 |
20050055270 | Broe | Mar 2005 | A1 |
20050058427 | Nguyen et al. | Mar 2005 | A1 |
20050071225 | Bortolin et al. | Mar 2005 | A1 |
20050071226 | Nguyen et al. | Mar 2005 | A1 |
20050071227 | Hammad et al. | Mar 2005 | A1 |
20050071228 | Bortolin et al. | Mar 2005 | A1 |
20050075958 | Gonzalez | Apr 2005 | A1 |
20050080716 | Belyi et al. | Apr 2005 | A1 |
20050091118 | Fano | Apr 2005 | A1 |
20050097473 | Malik et al. | May 2005 | A1 |
20050102233 | Park et al. | May 2005 | A1 |
20050102234 | Devine | May 2005 | A1 |
20050121506 | Gauthier et al. | Jun 2005 | A1 |
20050149455 | Bruesewitz et al. | Jul 2005 | A1 |
20050165684 | Jenson et al. | Jul 2005 | A1 |
20050177510 | Hilt et al. | Aug 2005 | A1 |
20050199714 | Brandt et al. | Sep 2005 | A1 |
20050210387 | Alagappan et al. | Sep 2005 | A1 |
20050216337 | Roberts et al. | Sep 2005 | A1 |
20050219061 | Lai et al. | Oct 2005 | A1 |
20050222933 | Wesby | Oct 2005 | A1 |
20050228719 | Roberts et al. | Oct 2005 | A1 |
20050283416 | Reid et al. | Dec 2005 | A1 |
20050283430 | Reid et al. | Dec 2005 | A1 |
20050283431 | Reid et al. | Dec 2005 | A1 |
20050283432 | Reid et al. | Dec 2005 | A1 |
20050283433 | Reid et al. | Dec 2005 | A1 |
20060004631 | Roberts et al. | Jan 2006 | A1 |
20060010231 | Spector | Jan 2006 | A1 |
20060043473 | Eppich | Mar 2006 | A1 |
20060043474 | Kenzer et al. | Mar 2006 | A1 |
20060053056 | Alspach-Goss et al. | Mar 2006 | A1 |
20060059110 | Madhok et al. | Mar 2006 | A1 |
20060074769 | Looney et al. | Apr 2006 | A1 |
20060080243 | Kemper et al. | Apr 2006 | A1 |
20060085260 | Yamagishi | Apr 2006 | A1 |
20060089905 | Song et al. | Apr 2006 | A1 |
20060099936 | Link et al. | May 2006 | A1 |
20060111967 | Firbes | May 2006 | A1 |
20060122881 | Walker et al. | Jun 2006 | A1 |
20060122921 | Comerford et al. | Jun 2006 | A1 |
20060131385 | Kim | Jun 2006 | A1 |
20060136546 | Trioano et al. | Jun 2006 | A1 |
20060149529 | Nguyen et al. | Jul 2006 | A1 |
20060155644 | Reid et al. | Jul 2006 | A1 |
20060161435 | Atef et al. | Jul 2006 | A1 |
20060161599 | Rosen | Jul 2006 | A1 |
20060163345 | Myers et al. | Jul 2006 | A1 |
20060165060 | Dua | Jul 2006 | A1 |
20060175403 | Fossen Mcconnell et al. | Aug 2006 | A1 |
20060178957 | LeClaire | Aug 2006 | A1 |
20060179007 | Davis | Aug 2006 | A1 |
20060200396 | Satterfield et al. | Sep 2006 | A1 |
20060202025 | Calabrese et al. | Sep 2006 | A1 |
20060206376 | Gibbs et al. | Sep 2006 | A1 |
20060218086 | Campbell et al. | Sep 2006 | A1 |
20060219780 | Swartz | Oct 2006 | A1 |
20060224449 | Byerley et al. | Oct 2006 | A1 |
20060229945 | Walker et al. | Oct 2006 | A1 |
20060237531 | Heffez | Oct 2006 | A1 |
20060248007 | Hofer et al. | Nov 2006 | A1 |
20060253389 | Hagale et al. | Nov 2006 | A1 |
20060253390 | McCarthy et al. | Nov 2006 | A1 |
20060270421 | Phillips et al. | Nov 2006 | A1 |
20060281439 | Benco et al. | Dec 2006 | A1 |
20060282382 | Balasubramanian et al. | Dec 2006 | A1 |
20060287902 | Helsper et al. | Dec 2006 | A1 |
20060290501 | Hammad et al. | Dec 2006 | A1 |
20060293027 | Hammad et al. | Dec 2006 | A1 |
20070001000 | Nguyen et al. | Jan 2007 | A1 |
20070001001 | Myers et al. | Jan 2007 | A1 |
20070005613 | Singh et al. | Jan 2007 | A1 |
20070005774 | Singh et al. | Jan 2007 | A1 |
20070011099 | Sheehan | Jan 2007 | A1 |
20070012764 | Bortolin et al. | Jan 2007 | A1 |
20070017970 | Gauthier et al. | Jan 2007 | A1 |
20070027803 | Brandes et al. | Feb 2007 | A1 |
20070034682 | Williams | Feb 2007 | A1 |
20070050259 | Wesley | Mar 2007 | A1 |
20070055597 | Patel et al. | Mar 2007 | A1 |
20070055630 | Gauthier et al. | Mar 2007 | A1 |
20070057034 | Gauthier et al. | Mar 2007 | A1 |
20070057051 | Bortolin et al. | Mar 2007 | A1 |
20070083465 | Ciurea et al. | Apr 2007 | A1 |
20070084913 | Weston | Apr 2007 | A1 |
20070094150 | Yven et al. | Apr 2007 | A1 |
20070100691 | Patterson | May 2007 | A1 |
20070107044 | Yven et al. | May 2007 | A1 |
20070125842 | Antoo et al. | Jun 2007 | A1 |
20070136131 | Mankoff | Jun 2007 | A1 |
20070155402 | Van Erlach | Jul 2007 | A1 |
20070162328 | Reich | Jul 2007 | A1 |
20070174082 | Singh | Jul 2007 | A1 |
20070174259 | Amjadi | Jul 2007 | A1 |
20070178912 | Baranowski | Aug 2007 | A1 |
20070179819 | Bradley et al. | Aug 2007 | A1 |
20070185776 | Nguyen et al. | Aug 2007 | A1 |
20070194104 | Fukuda | Aug 2007 | A1 |
20070199049 | Ziebell | Aug 2007 | A1 |
20070203836 | Dodin | Aug 2007 | A1 |
20070205270 | Kemper et al. | Sep 2007 | A1 |
20070226051 | Addepalli et al. | Sep 2007 | A1 |
20070241189 | Slavin et al. | Oct 2007 | A1 |
20070244811 | Tumminaro | Oct 2007 | A1 |
20070250380 | Mankoff | Oct 2007 | A1 |
20070262136 | Ou | Nov 2007 | A1 |
20070276764 | Mann et al. | Nov 2007 | A1 |
20070278291 | Rans | Dec 2007 | A1 |
20070281689 | Altman et al. | Dec 2007 | A1 |
20070281690 | Altman et al. | Dec 2007 | A1 |
20070281716 | Altman et al. | Dec 2007 | A1 |
20070282621 | Altman et al. | Dec 2007 | A1 |
20070288373 | Wilkes | Dec 2007 | A1 |
20070288641 | Lee et al. | Dec 2007 | A1 |
20080000964 | Flake et al. | Jan 2008 | A1 |
20080003987 | Mechaley | Jan 2008 | A1 |
20080004950 | Huang et al. | Jan 2008 | A1 |
20080006685 | Rackley, III et al. | Jan 2008 | A1 |
20080017708 | Singer-Harter | Jan 2008 | A1 |
20080021784 | Hessburg et al. | Jan 2008 | A1 |
20080040265 | Rackley, III et al. | Feb 2008 | A1 |
20080052168 | Peters et al. | Feb 2008 | A1 |
20080059297 | Vallier et al. | Mar 2008 | A1 |
20080070593 | Altman et al. | Mar 2008 | A1 |
20080071614 | Mebruer et al. | Mar 2008 | A1 |
20080082424 | Walton | Apr 2008 | A1 |
20080103959 | Carroll | May 2008 | A1 |
20080114657 | Forzley | May 2008 | A1 |
20080120182 | Arnold et al. | May 2008 | A1 |
20080126145 | Rackley | May 2008 | A1 |
20080132251 | Altman et al. | Jun 2008 | A1 |
20080132252 | Altman et al. | Jun 2008 | A1 |
20080133336 | Altman et al. | Jun 2008 | A1 |
20080133366 | Evans et al. | Jun 2008 | A1 |
20080139112 | Sampath et al. | Jun 2008 | A1 |
20080139181 | Lokshin | Jun 2008 | A1 |
20080147484 | Davis | Jun 2008 | A1 |
20080147495 | Bal et al. | Jun 2008 | A1 |
20080154727 | Carlson et al. | Jun 2008 | A1 |
20080154735 | Carlson | Jun 2008 | A1 |
20080154772 | Carlson | Jun 2008 | A1 |
20080156870 | Niedermeyer et al. | Jul 2008 | A1 |
20080161018 | Miller et al. | Jul 2008 | A1 |
20080163257 | Carlson et al. | Jul 2008 | A1 |
20080167991 | Carlson et al. | Jul 2008 | A1 |
20080177603 | Muthugopalakrishnan | Jul 2008 | A1 |
20080182590 | Ruckart et al. | Jul 2008 | A1 |
20080183480 | Carlson et al. | Jul 2008 | A1 |
20080201226 | Carlson et al. | Aug 2008 | A1 |
20080201310 | Fitzpatrick et al. | Aug 2008 | A1 |
20080201321 | Fitzpatrick et al. | Aug 2008 | A1 |
20080207124 | Raisanen | Aug 2008 | A1 |
20080208762 | Arthur et al. | Aug 2008 | A1 |
20080300973 | DeWitt et al. | Dec 2008 | A1 |
20080319843 | Moser et al. | Dec 2008 | A1 |
20090076896 | DeWitt et al. | Mar 2009 | A1 |
20090076925 | Dewitt | Mar 2009 | A1 |
20090078777 | Granucci et al. | Mar 2009 | A1 |
20090081990 | Granucci et al. | Mar 2009 | A1 |
20090112721 | Hammad et al. | Apr 2009 | A1 |
20090119170 | Hammad et al. | May 2009 | A1 |
20090134840 | Yamamoto et al. | May 2009 | A1 |
20090150272 | Blythe | Jun 2009 | A1 |
20090182634 | Park et al. | Jul 2009 | A1 |
20090327134 | Carlson et al. | Dec 2009 | A1 |
20090327151 | Carlson et al. | Dec 2009 | A1 |
20100017275 | Park et al. | Jan 2010 | A1 |
20100082454 | Narayanaswami | Apr 2010 | A1 |
20110035284 | Moshfeghi | Feb 2011 | A1 |
20110093326 | Bous | Apr 2011 | A1 |
20110313874 | Hardie | Dec 2011 | A1 |
Number | Date | Country |
---|---|---|
1 096 439 | May 2001 | EP |
1 136 961 | Sep 2001 | EP |
1 178 421 | Feb 2002 | EP |
2 348 781 | Nov 2003 | GB |
396CHENP2011 | Nov 2011 | IN |
2001-76058 | Mar 2001 | JP |
2001-222767 | Aug 2001 | JP |
2002-117313 | Apr 2002 | JP |
2002-318960 | Oct 2002 | JP |
2005-215849 | Aug 2005 | JP |
2006-268376 | Oct 2006 | JP |
10-2004-0094249 | Nov 2004 | KR |
10-2006-0025495 | Mar 2006 | KR |
2006 0117091 | Nov 2006 | KR |
9613814 | May 1996 | WO |
9745814 | Apr 1997 | WO |
9745814 | Dec 1997 | WO |
9951038 | Oct 1999 | WO |
0003328 | Jan 2000 | WO |
0077697 | Dec 2000 | WO |
2004077369 | Sep 2004 | WO |
2005052869 | Jun 2005 | WO |
2006024080 | Mar 2006 | WO |
07056449 | May 2007 | WO |
07056450 | May 2007 | WO |
Entry |
---|
U.S. Appl. No. 12/491,125, Office Action dated Feb. 6, 2012, 19 pages. |
U.S. Appl. No. 12/491,139 , Advisory Action, dated Feb. 1, 2016, 5 pages. |
U.S. Appl. No. 12/491,139 , Final Office Action, dated Sep. 3, 2015, 30 pages. |
U.S. Appl. No. 12/491,139 , Final Office Action, dated Apr. 9, 2014, 44 pages. |
U.S. Appl. No. 12/491,139 , Non-Final Office Action, dated Mar. 2, 2016, 30 pages. |
U.S. Appl. No. 12/491,139 , Non-Final Office Action, dated Jul. 24, 2013, 31 Pages. |
U.S. Appl. No. 12/491,139 , Notice of Allowance, dated Aug. 31, 2016, 20 pages. |
U.S. Appl. No. 12/491,139 , Office Action, dated May 15, 2012, 23 pages. |
U.S. Appl. No. 12/491,139 , Office Action, dated Jan. 14, 2013, 25 pages. |
U.S. Appl. No. 15/363,311 , Final Office Action, dated Mar. 7, 2019, 6 pages. |
U.S. Appl. No. 15/363,311 , Non-Final Office Action, dated Nov. 2, 2018, 18 pages. |
U.S. Appl. No. 15/363,311 , Notice of Allowance, dated May 21, 2019, 12 pages. |
AU2009262087 , “First Examination Report”, dated Jan. 15, 2014, 3 pages. |
AU2009262087 , “Fourth Examination Report”, dated Mar. 25, 2015, 4 pages. |
AU2009262087 , “Notice of Acceptance”, dated Aug. 20, 2015, 2 pages. |
AU2009262087 , “Second Examination Report”, dated Jul. 1, 2014, 3 pages. |
AU2009262087 , “Third examination Report”, dated Oct. 28, 2014, 5 pages. |
AU2015264821, “First Examination Report”, dated Nov. 22, 2016, 4 pages. |
AU2015264821, “Notice of Acceptance”, dated May 15, 2017, 3 pages. |
Application No. EP09771101.4 , Extended European Search Report, dated Apr. 12, 2012, 11 pages. |
Application No. EP09771101.4 , Office Action, dated Aug. 20, 2013, 13 pages. |
Application No. EP09771121.2, Office Action, dated Aug. 6, 2013, 12 pages. |
PCT/US2007/088289, “International Search Report and Written Opinion”, dated May 15, 2008, 10 pages. |
PCT/US2007/088313, “International Preliminary Report on Patentability”, dated Jul. 9, 2009, 6 pages. |
PCT/US2007/088563, “International Preliminary Report on Patentability”, dated Jul. 9, 2009, 8 pages. |
PCT/US2007/088659. “International Preliminary Report on Patentability”, dated Jul. 9, 2009, 7 pages. |
PCT/US2009/048780, “International Preliminary Report on Patentability”, dated Jan. 13, 2011, 6 pages. |
PCT/US2009/048780. “International Search Report and Written Opinion”, dated Feb. 24, 2010, 7 pages. |
PCT/US2009/048813, “International Preliminary Report on Patentability”, dated Jan. 13, 2011, 7 pages. |
U.S. Appl. No. 60/335,667, filed Feb. 5, 2002. |
U.S. Appl. No. 60/356,861, filed Feb. 12, 2002. |
U.S. Appl. No. 60/361,646, filed Mar. 4, 2002. |
Search/Examination Report dated Feb. 5, 2010 from International Application No. PCT/US2009/048813, 11 pages. |
Schreiner, Keri; “Where We At? Mobile Phones Bring GPS to the Mases”; 2007, IEEE Computer Graphics and Applications, pp. 6-11. |
The Supplementary European Search Report for Application No. EP09771121.2, dated Apr. 16, 2012, 10 pages. |
About Us, 1 page downloaded from http://www.cellfire.com/about-us/ on 5/10107, 1 page. |
U.S. Appl. No. 11/960,162, filed Dec. 19, 2007. |
U.S. Appl. No. 11/960,173, filed Dec. 19, 2007. |
Japanese Office Action dated Aug. 10, 2012 for JP Patent Application No. 2009-544232, with English Translation, 9 pages. |
Australian Office Action dated Sep. 5, 2011 for AU Patent Application No. 2007339916, 3 pages. |
Australian Notice of Acceptance dated Mar. 28, 2012 for AU Patent Application No. 2007339916, 3 pages. |
Chinese Office Action dated Dec. 3, 2010 for CN Patent Application No. 200780050840.7, with English Translation, 2 pages. |
Chinese Office Action dated Nov. 22, 2011 for CN Patent Application No. 200780050840.7, with English Translation, 15 pages. |
Chinese Office Action dated Jun. 4, 2012 for Cn Patent Application No. 200780050840.7, with English Translation, 15 pages. |
European Search Report dated Dec. 15, 2011 for EP Patent Application No. 07869801.6, 7 pages. |
“SmarTrip More Than a Smart Card. It's Pure Genius”, 1998-2004, WMATA, http://www.wmata.com/riding/smartrip.cfm (2 pages). |
“Adding value to SmarTrip is as easy as using it”, 1998-2004, WMATA, http://www.wmata.com/riding/smartrip_adding_value.cfm (1 page). |
“Virtual Shopping: Straight Goods on Cyber-stores and Security.” Chatelaine; vol. 70, p. 24 (Feb. 1997). |
Emmerson, Kassidy; “The History of PayPal: One of the Most Successful Online Money Transmitters Today”; 2009, http://www.associatedcontent.com/pop_print.shtml?content_type=arti . . . , 1 page. |
International Preliminary Report on Patentability and Written Opinion from International Application No. PCT/US2007/088615, dated Jul. 9, 2009. |
International Preliminary Report on Patentability from International Application No. PCT/US2007/088289 dated Jul. 9, 2009. |
International Preliminary Report on Patentability from International Application No. PCT/US2007/088313 dated Jun. 30, 2008. |
International Preliminary Report on Patentability from International Application No. PCT/US2007/088687 dated Jul. 9, 2009. |
bCode™ is the future of Mobile Coupon, Ticketing, Loyalty and Payments, 2 page product brochure downloaded from http://www.bcode.com on May 11, 2007, 2 pages. |
bCode™ MediaHub 200 Mobile Coupon, Ticketing Loyalty and Payments, 2 page product brochure, from http://www.bcode.com/news_media.htm on May 11, 2007, 2 pages. |
Cellfire—Mobile coupons for your cell phone, 1 page product brochure downloaded from http://www.cellfire.com on May 11, 2007, 1 page. |
Cellfire, Coupons on Cellfire, 2 pages downloaded from http://www.cellfire.com/coupons on May 10, 2007, 2 pages. |
Press Release, “Three months after California release, Cellfire™ reports redemption rates n times greater than paper coupons,” issued by Cellfire, Inc. Mar. 22, 2006; pp. 1-2 downloaded from http://www.cellfire.com/about-us/articles/2006-03-22_redemption-rate, 2 pages. |
Purdy et al., “When Mobile Coupons Replace Paper Coupons, Everyone Wins,” pp. 1-17 published by Frost & Sullivan.[online]. info.cellfire.com, May 11, 2007, [Retrieved from the Internet: URL: http://info.cellfire.com/cellfire/themes/cellfire/downloads/When_Mobile_Coupons_Replace_Paper_Coupons.pdf], 17 pages. |
Kageyama, Yuri; “Japanese carrier unveils mobile-phone wallet,” [online], [retrieved from the on Feb. 5, 2007]. Retrieved from the internet <URL: http://usatoday.printthis.clickability.com/pt/cpt?action=cpt&title=USATODAY.com+-+Jap . . . >, 3 pages. |
Korousic, Bojan et al.; “3rd Year Project Report EZ-Ca$h: Feasibility Project,” 2003, Electronics Engineering Technology-Telecommunications Systems, Conestoga College, 33 pages. |
Subramanian, Hemang C.; “SIM Access Profile: Electronic currency using SIM Access Profile,” [online] 2003. [Retrieved on Jul. 1, 2007]. Retrieved from the internet <URL: http:/www-128.ibm.com/developerworks/wireless/library/wi-simacc/>, 6 pages. |
“Ubiquitous Commerce”; [online]. [Retrieved on 07-01-24] Retrieved from the internet <URL: http://www.accenture.com/Global/Services/Accenture_Technology_Labs/R_and_l/Mobile . . . > 2 pages. |
“M Pay: Frequently Asked Questions, ”[online]. [Retrieved on 07-01-24]. Retrieved from the internet <URL: http://www.m-pay.com/index.php?id=18> , 5 pages. |
“GSMVend Technical Manual”; [online]. [Retrieved on Jul. 3, 2016]. Retrieved from the internet <URL: http://www.bonusdata.net/IntusJunior/GSMVend/gsmvend.htm>, 14 pages. |
U.S. Appl. No. 11/749,366, filed May 16, 2007(Copy not attached). |
U.S. Appl. No. 11/767,033, filed Jun. 22, 2007 (Copy not attached). |
U.S. Appl. No. 11/963,736 filed Dec. 21, 2007 (Copy not attached). |
U.S. Appl. No. 11/963,095, filed Dec. 21, 2007 (Copy not attached). |
U.S. Appl. No. 11/962,836, filed Dec. 21, 2007 (Copy not attached). |
U.S. Appl. No. 12/491,125, filed Jun. 24, 2009 (Copy not attached). |
U.S. Appl. No. 12/491,139, filed Jun. 24, 2009 (Copy not attached). |
International Search Report from International Application No. PCT/US2008/077688 dated Dec. 2, 2008. |
International Preliminary Report on Patentability from International Application No. PCT/US2007/088653 dated Jun. 30, 2009. |
U.S. Appl. No. 12/491,143, filed Jun. 24, 2009 (Copy not attached). |
International Search Report and Written Opinion of the International Searching Authority from International Application No. PCT/US2007/088687 dated May 12, 2008, 10 pages. |
Number | Date | Country | |
---|---|---|---|
20190378156 A1 | Dec 2019 | US |
Number | Date | Country | |
---|---|---|---|
61076099 | Jun 2008 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15363311 | Nov 2016 | US |
Child | 16550133 | US | |
Parent | 12491139 | Jun 2009 | US |
Child | 15363311 | US |