Patent Grant
10339549
The widespread use of mobile phones and the increasing sophistication of smart phones have created societies in which personal, mobile computing power has become nearly ubiquitous. Content for mobile computing devices has typically flowed from technology initially used with desktop computers. Some aspects of mobile computing devices, such as a small form factor with limited display capabilities and a lack of full-size keyboards, hinder adoption of content originally designed for desktop computers. Other aspects, such as the mobility itself, provide unique opportunities to use mobile computing devices in ways very different than the ways people use desktop computers. Development of content that recognizes the limitations while taking full advantage of the unique aspects of mobile computing devices is still an active and maturing field.
Consumers are also becoming increasingly comfortable with virtual interactions, such as online shopping. However, in spite of the relative convenience of the virtual world, as opposed to the brick-and-mortar world, friction and security concerns still limit adoption of virtual interactions. For example, remembering passwords and maintaining multiple accounts create friction in virtual-world interactions. Additionally, the anonymity and lack of direct interaction between the consumer and the merchant create potential security problems. Accordingly, content designed specifically for mobile computing devices that eliminates the friction of transactions and addresses securities concerns will have great value for consumers.
The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items.
Many activities are defined in whole or part by the location at which those activities occur. In some instances, the activity can be inferred with a high likelihood of accuracy based on the location alone. For example, a car at a tollbooth is likely there to pay the toll and pass through, a person waiting by a boarding gate for an airplane is likely a ticket holder for the flight, a person with a reservation at a hotel is likely going to check in to the hotel when he or she arrives in the lobby. At some locations many types of activities may be probable, but there are certain activities that will only happen at those locations. For example, many things may happen at the entry to a house, but arming or disarming a home security system will only be done at that location. A mobile computing device that is location-aware and can predict or infer what a user may be doing at that location will be able to automate some activities and provide a high level of user convenience.
This disclosure is directed to, in part, facilitating transactions based on geolocation and unique user identification. For instance, these transactions may include electronic commerce transactions or any other type of transaction. Innovations in electronic commerce, such as a one-click shopping cart, have made the “Internet shopping” experience smoother and have reduced friction perceived by the user. For instance, clicking a single button to complete a purchase requires fewer steps than entering a password, address, credit card number, and such. The reduction of steps, clicks, and the like reduces the friction in a transaction. Commerce in the brick-and-mortar world causes the consumer even more friction than transactions in the electronic commerce world in some instances. For example, describing the item one wishes to purchase, presenting payment to a cashier, waiting for the cashier to process the payment, and eventually receiving the desired item is an example of a typical, and relatively high-friction, brick-and-mortar transaction.
Access to the World Wide Web from mobile devices provides a platform for electronic commerce similar to Internet shopping from a desktop computer. Mobile computing devices, such as mobile phones, are often carried with users throughout their daily interactions in the brick-and-mortar world. Many of these mobile computing devices are equipped with Global Positioning System (GPS) functionality to determine a location of the device, and thus, a location of the corresponding user. This disclosure combines the location awareness of mobile devices with the relatively lower friction transactions of electronic commerce to create a friction-free or, in some instances, a “zero-click” solution for interactions between consumers and merchants in the brick-and-mortar world. Unique user identification provides a thread that ties together information about a particular user (e.g., credit card data), a link between that user and a given mobile computing device, and the relationship that user wishes to have with a given merchant (e.g., opt in to zero-click purchasing).
A merchant may include any human or legal person such as, but not limited to, sellers of goods or services that engages in transactions with customers. For example, a government may be a merchant in the context of providing government services, privileges, and/or rights.
The described techniques for low-friction or friction-free transactions may be implemented in a number of ways and in a number of contexts. Example implementations and context are provided with reference to the following figures, as described below in more detail. It is to be appreciated, however, that the following implementations and contexts illustrative of many possible implementations and contexts
Illustrative Environment and System Architecture
The mobile device 104 may be implemented as any number of mobile devices, including but not limited to a mobile phone, a personal digital assistant (PDA), a laptop computer, a net book, an eBook reader, a personal media player (PMP), a portable gaming system, an automobile navigation system, and so forth. The device 104 is location aware, or is able to provide information to another entity (e.g., a server) to allow the other entity to determine a location of the device 104. A location on the surface of the earth, or a “geolocation,” may be provided to the device by a satellite 112 such as a GPS satellite. Alternatively, wireless signals such as from a radio antenna 114 may be used to determine a geolocation of the device 104 relative to a known position of the radio antenna 114. Other technologies and methods for determining geolocation are also envisioned within the scope of this disclosure such as, for example, calculating geolocation based on a network access point (e.g., WiFi hotspot) or from a locator signal broadcast from a known location, such as at the merchant 106.
The device 104 and the merchant 106 may connect to a network 116. The network 116 may include any one or combination of multiple different types of networks, such as cable networks, local area networks, personal area networks, wide area networks, the Internet, wireless networks, ad hoc networks, mesh networks, and/or the like. In some implementations the satellite 112 and/or the radio antenna 114 may provide network connectivity to the mobile device 104 as well as provide geolocation. For example, the radio antenna 114 may provide network access to the mobile device 104 according to the International Mobile Telecommunications-2000 standards (“3G network”) or the International Mobile Telecommunications Advanced standards (“4G network”). Other implementations may include one source of geolocation data such as the satellite 112 and a separate source of network connectivity such as a WiFi hotspot. The merchant 106 may connect to the network 116 through the merchant server 108 using any suitable mechanism such as a wired or wireless connection.
A one or more servers 118 may also be connected to the network 116 and configured to manage interaction between the mobile device 104 and the merchant 106. In some implementations, all or part of the interaction between the mobile device 104 and the merchant 106 may be through a direct communications link 120 without passing through the server 118 or the network 116. The direct communication link 120 may be implemented by radio transmissions (e.g., IEEE 802.11, Bluetooth), infrared signals, radio frequency identification (RFID), magnetism (e.g., magnetic strips such as used on credit cards), display of a code on the device 104 to a human operator or to a scanning device at the merchant 106, and/or any other method of directly passing information between the mobile device 104 and the merchant 106.
The server(s) 118 may house or otherwise have a connection to multiple data stores including user information 122, merchant profiles 124, an advertisement (“ad”) database 126, and/or other data stores. Generally, the user information 122 contains information about the user 102 associated with the mobile device 104. The user information 122 enables efficient and personalized interaction between the user 102 and the merchant 106. The merchant profiles 124 generally contain information about one or more merchants including the merchant 106 with which the user 102 is interacting. One type of interaction between the merchant 106 and the user 102 is advertising provided from the merchant 106 to the device 104. Information for generating relevant advertisements may be contained in the advertisement database 126. Each of the data stores will be discussed in greater detail below.
The server(s) 118 may also comprise an authentication module 128 that compares login information from the mobile device 104 and/or the merchant 106 to confirm that the correct user information 122, merchant profiles 124, advertisement database 126, and other information is correctly correlated with the right entity (e.g., user 102 and/or point-of-sale device 110). The authentication module 128 will be discussed in greater detail below.
Illustrative Mobile Device
The device 104 may also contain user information 210 stored locally in the memory 204. This information may be configurable by the user 102 and can include payment information, a home location, and/or map of the device's 104 past movements, past transaction histories, and/or any other information related to the user 102.
The transaction module 212 may recognize when the mobile device 104 is located at a merchant location and, in response, may facilitate a transaction with the merchant 106. The transaction may be based in part on the user information 210. The transaction module 212 may be configured with appropriate application programming interfaces (APIs) to establish a standard communication protocol for receiving information from the merchant 106 (e.g., merchant name and requested payment) and providing corresponding information about the user 102 (e.g., payment information and user identification 208). In some implementations, the transaction module 212 is a software application that a user 102 may install on his or her device 104 such as by downloading from a website. In other implementations, the transaction module 212 may be preinstalled by a manufacturer or retailer of the mobile device 104 and/or built into the mobile device 104 as a type of firmware or hardware. The transaction module 212 coordinates the user identification 208, user information 210, geolocation, and the like to facilitate transactions between the user 102 and the merchant 106.
Given the ability of the mobile device 104 to serve as a platform for zero-click purchases, there is a need to provide security in order to prevent unauthorized charges. The security module 214 addresses this need by limiting functionality of the mobile device 104 and initiating security events in appropriate circumstances. The security module 214 may process login information, such as passwords and/or biometric information to authenticate the user 102 and prevent other people from using the mobile device 104. The security module 214 may also analyze behavior such as purchasing patterns and/or movement patterns and infer that irregular behavior may indicate fraudulent or unauthorized activity and limit device functionality accordingly, as described below in greater detail.
Mobile device 104 also includes one or more input and output devices 216. The output devices may comprise one or more display devices 218 including touch-screen displays that also function as an input device. An accelerometer 220 detects rotation or vibration of the mobile device 104. The accelerometer 220 may be a convenient mechanism for the user 102 to communicate an input to the mobile device 104 by slapping, shaking, twisting, and/or by making a motion that can be detected by the accelerometer 220. The mobile device 104 may also include a camera 222 capable of taking still or video pictures. An antenna 224 in the mobile device 104 may send and receive wireless signals from sources such as the radio antenna 114 and satellite 112. The device 104 may further comprise other input/output devices 226, such as a microphone and a speaker used, for example, in an implementation in which the mobile device 104 functions as a telephone.
In some implementations, the mobile device 104 may also include a calendar/clock 228, a location sensor 230, and a network interface 232. The calendar/clock 228 may calculate time, date, and other data that can be derived from time data and date data. In some implementations, the calendar/clock 228 may communicate with the location sensor 230 to determine, for example, day length at the current location of the device 104 based on the date. This could enable the device 104 to determine whether it is daytime or nighttime based on the time, date, and geolocation.
The calendar/clock 228 and the location sensor 230 may also communicate to create a log of where the device 104 is located at numerous time points. The log of time-place data may be compiled into a map that shows movements of the device overtime and throughout different dates. This map may be stored in the memory 204, for example as a part of the user information 210. The location sensor 230 includes any sort of system that informs the mobile device 104 of its geolocation including, but not limited to, the Global Positioning System of satellites circling the Earth. Alternatively, the location sensor may determine geolocation by radio signal triangulation (e.g., triangulation based on radio antenna signal strength).
The network interface 232 may be configured for wirelessly communicating with the network 116. The network interface 232 may use any standard protocols for network communication. The network interface 232 may be capable of high speed, wireless network communication. In some implementations, the network interface 232 may use the antenna 224 to send and receive data from the network 116. In further implementations, a network interface 232 may provide information to the location sensor 230 (e.g., a closest network access point) from which the location sensor 230 can infer or calculate a location of the mobile device 104.
Illustrative Server
The user identifier 208 represents a user 104 that is interacting with the server(s) 118 via a mobile device 104. The authentication module 128 determines if communications coming from the mobile device 104 should be associated with the user identifier 208. In some implementations, authorization may involve handshaking or other verification between, for example, the authentication module 128 of the server(s) 118 and the security module 214 of the mobile device 104. The authentication module 128 may similarly authenticate the identity of merchants 106. Providing robust data security may avoid fraudulent transactions from both mobile devices 104 and merchants 106.
The server(s) 118 may also include a transaction module 308. In some implementations, the transaction module 308 on the server(s) 118 is similar to the transaction module 212 on the mobile device 104. Transactions between the user 102 and the merchant 106 may be facilitated by either or both of the transaction modules 212 and 308 when a geolocation of the device matches or is within a threshold distance of a geolocation of the merchant. The transaction module 308 may be configured with APIs for exchanging information with both the merchant 106 and the mobile device 104. In some implementations, the APIs exposed to the merchant 106 may be regulated to prevent unauthorized merchants from access in the system and to improve data security. The APIs exposed to the mobile device 104 may be generic or customized to specific device hardware and operating systems. Providing multiple sets of APIs may allow the server(s) 118 to translate communications between mobile devices 104 and merchants 106 that would otherwise not be able to exchange information.
A map 310 stored on the server(s) 118 may contain geolocations of merchants 106. Correlation between a particular merchant 106 and a particular geolocation may be used to infer that a mobile device 104 is located at or near a merchant 106 because the mobile device is located at or near a geolocation associated with that merchant 106 in the map 310. The map 310 may also contain real-time information about the geolocations of each of the mobile devices 104 associated with the respective user identifiers 208-306. From this information it may be possible to determine how many mobile devices 104 that belong to the system are present at a given merchant location. It may also be possible to identify other mobile devices 104 in proximity to a given mobile device 104. For example, the map 310 may show that a user's friend (or at least the friend's mobile device) is at the merchant next door.
The server(s) 118 may also facilitate advertising via advertisements sent from or on behalf of the merchant 106 to the mobile device 104. In some instances, the bidding module 312 may receive and process bids for the privilege to place advertisements on mobile devices 104. Users 102 may opt in to receive advertising and be presented with relevant advertisements based on a geolocation of the mobile device 104 and user information 122. The bidding may be structured according to any known bidding system or otherwise. The operator of the server 118 may structure the bidding so as to maximize advertising revenue paid by the merchants 106.
Out of all the merchants participating in the system the user 102 may select some subset of those merchants as trusted merchants 408. In some implementations, whenever a user conducts a transaction with a merchant the user may be asked if he or she wishes to add that merchant to the list of trusted merchants. This status as a trusted merchant may be part of the user information 122. The status as a trusted merchant may enable the merchant 106 to engage in transactions with the user 102 via the user's mobile device 104. The status as a trusted merchant may also decrease the amount of interaction required from the user 102 to complete electronic transaction using the mobile device 104 as compared with other merchants that are not included on the trusted merchant list. Within the list of trusted merchants 408 different merchants may be given different trust levels by the user 102. For example, transactions with the most trusted merchants may be completed automatically merely by the user 102 (and the mobile device 104) entering a location of the merchant 106. For other merchants 106 with whom the user 102 does not desire such use of “zero-click” transactions, the user 102 may indicate a lower level of trust that requires some minimal interaction between the user 102 and the mobile device 104 in order to complete a transaction. This may be thought of as a “one-click” interaction, although the specific interaction may be something other than a “click.” For other merchants that the user 102 associates with an even lower level of trust, the user 102 may require more than one click such as entry of a password and login before the mobile device 104 is enabled to complete a transaction with the merchant 106.
The merchant profiles 124 contain information about the merchants such as geolocations 410 of the merchants' brick-and-mortar locations, promotions 412 offered by the merchant, and other data 414 about the merchant which may be used to facilitate transactions with mobile devices 104 (e.g., types of credit cards are accepted). The geolocations 410 may be one source of data used to create the map 310 stored on the server(s) 118. The promotions 412 may include things such as coupons or discounts for goods or services offered by the merchant. The promotions 412 may, for example, give a discount to a user 102 who has designated the merchant as a trusted merchant. As a further example, a merchant may provide a coupon to a user 102 of a mobile device 104 when the user enters a competitor's store.
Communication between merchants and mobile devices 104 may also include advertising. The mobile device 104 may have a user interface with a designated window or advertisement box for displaying advertisements sent from merchants 106. The advertisement database 126 stores advertisement content 416 in association with geolocations 418 and merchant information 420. Because the advertisements are targeted for mobile devices 104 which may include a location sensor 230, the advertisement content 416 is associated with one or more geolocations 418 in order to provide location-relevant advertisements. For example, advertisements for a merchant may appear when the user 102 carrying the mobile device 104 approaches the geolocations of one of the merchant's retail stores. For instance, when a user approaches a coffee shop, that coffee shop may serve an advertisement or a promotion for a discounted cup of coffee when the user is near to or is within the coffee shop.
The advertisement content 416 may appear when the mobile device 104 is a predetermined distance from the merchant. In some implementations, the predetermined distance may depend upon a speed at which the mobile device 104 is traveling so that someone traveling in a moving car may receive the advertisement content 416 at a greater distance from the merchant then someone walking. In some implementations, the display of advertisements may be deactivated based on the speed at which the mobile device 104 is moving. This feature could prevent distractions to drivers by blocking advertisements, or at least placing the mobile device into a silent mode, when the speed of the mobile device 104 exceeds a speed threshold. The merchant information 420 may designate the merchant supplying the advertisement content 416. This may be used in conjunction with the user profile 404 of a user 102 to provide advertisements from merchants from which that user 102 has expressed an interest (explicitly or implicitly), while refraining from providing advertisements from other merchants. The merchant information 420 may also contain a bid amount indicating a maximum amount that the merchant is willing to bid in order to “win” and display their advertisement on the user's mobile device. This bid amount may be used by the bidding module 312 to determine which advertisement content 416 is displayed on a given mobile device 104.
Illustrative Transactions Between a Merchant and a Mobile Device
Operation 506 then correlates the location with a merchant. The merchant may, for example, provide a wireless network connection inside or proximate to its premises and the connection may identity the merchant. By doing so, each device using that network connection may recognize its current location as being at the merchant. In some implementations, the device may additionally or alternatively be aware of an abstract location such as a latitude and longitude provided by GPS. A map of merchant locations 508 may be used to match the latitude and longitude of the device with a merchant location. There may be locations at which the geolocation of the device can be identified; however, that geolocation might not correlate with any merchant location. For example, the device may be on a street near to several merchants but not located at any of those merchants.
At decision point 510 it is determined if the device is located at the merchant. In some instances, this determination may include determining if the device is within the merchant, while in other instances this may include determining if the device is within a predetermined distance of the merchant. If not, process 500 follows the “no” path and returns to operation 504. This loop may repeat continually until the device is located at a merchant. When the device is located at a merchant, process 500 follows the “yes” path to decision point 512.
At decision point 512, it is determined if transactions with this merchant are automated. For example, the user may decide that he or she wants to complete certain types of transactions with certain types of merchants in an automated manner. In such situations, the user may activate an automatic transaction functionality of his or her mobile device. However, for other merchants, or for other types of transactions, the user may desire more interaction such as specifying the details of the transaction or affirmatively agreeing to the transaction. If this transaction with this merchant is not automated, process 500 follows the “no” path and returns to operation 504. If the transaction is automated then process 500 follows the “yes” path to operation 514.
At operation 514 a transaction between the user of the device and the merchant is completed automatically in some instances. This automatic completion of the transaction when the user is located at the merchant creates a friction-free experience for the user. The coupling of location awareness with a mobile computing device allows for zero-click transactions.
As one illustrative example, a user could associate her prepaid card (or other payment instrument) for the local coffee shop with a mobile device. The user could additionally set her favorite drink at this coffee shop as a tall latte. This information may be stored on the mobile device, such as user information 210, or somewhere on a network, such as user information 122. The local coffee shop may have many stores and each store location may be associated with unique latitude and longitude coordinates. When the user carrying her mobile device arrives at any of the store locations the device recognizes those coordinates as corresponding with the local coffee shop and implements a transaction specified by the user. In this example, the user can specify that the mobile device uses her prepaid card to purchase a tall latte whenever she enters one of the local coffee shop locations. The user can walk directly to the counter and pick up her tall latte without opening her wallet or even verbally placing an order. This is a friction-free transaction. This example may take several variations. For instance, the merchant may ask the user to show an identification of the user (e.g., a driver's license), to orally state a password associated with the user, or the like. Or, the user may receive a phone call or a text message and may confirm completion of the transaction via one of these communication channels.
As another illustrative example, the merchant may be an ambulance that is itself mobile with location awareness and ability to communicate with mobile devices. A portion of the user information 122 and/or 210 may contain medical information about the user. This information may be encoded, available only through predetermined APIs, or otherwise limited so that is only released to “merchants” that provide medical services such as the ambulance. When the geolocation of the ambulance and the geolocation of a mobile device are the same, the medical information from that mobile device may be automatically provided to medical service providers in the ambulance. That medical information could potentially contain a photo of the user so that the paramedics can confirm that the person actually in the ambulance is the correct user to associate with the medical information. This medical information may include, for instance, a medical history of the user, medications that the user is allergic to, and the like, thus allowing the paramedics to properly treat the user in the event of an emergency.
The mobile device 104 may also facilitate transactions with merchants even when the user 102 is not at or near the geolocation of the merchant 106. For example, some merchants such as an online dating/matchmaking service may not have a physical location of relevance to users. For this type of merchant, the point-of-sale device 110 may be a server itself or a component of the merchant server 108. In such cases, the user 102 may be at a geolocation associated with another merchant such as a restaurant, but interact with the online merchant.
In an online dating implementation, transactions may be dependent upon the geolocation of one user relative to another user rather than the geolocation of the user 102 with respect to the merchant 106. For example, members of the online dating service may choose to make the geolocations of their respective mobile devices available to a merchant server of the online dating service. The merchant server may determine if two mobile devices are within a threshold distance of each other and if the two users are determined to be a match by the dating service (e.g., a match may be defined at least in part upon user information 122 such as the user profile 404), a transaction may be initiated between one or both of the mobile devices and the online dating service. The transaction may comprise a notification of a “member match” to which one of the users may respond by requesting to contact the other user who is the “member match.” The other user receiving the contact request may accept the contact request, decline the contact request, or ignore the contact request. If the contact request is accepted, the online dating service may allow mediated contact between the two users. In some implementations, direct contact information may be kept private so that communication between the two users must go through the online dating service (e.g., the merchant server of the online dating service).
At decision point 604, it is determined if the merchant is a trusted merchant for the user. The determination may be based in part on the list of trusted merchants 408 illustrated in
At operation 608, information about the device user is shared with the merchant. The information may include payment information 610, preference information 612, and a user identifier 614. In some implementations the user identifier 614 provided to the merchant in this operation may be the same user identifier 208 discussed above. In other implementations, the user identifier 614 in operation 608 may be different such as a unique user identifier 614 for this particular merchant, a “nickname” that is a proxy for the user identifier 614, or other identifier. Information may be shared with a point-of-sale device 110 of the merchant such as illustrated in
Next, at operation 616 the purchase between the user and the merchant is completed. The purchase may be completed using the payment information 606. It may also be completed using preference information 612, which in some implementations, may be used to automate the purchase so that the good or service indicated by the user preference information 612 is automatically purchased when the mobile device is detected at a merchant. In other implementations, completing the purchase at operation 616 may involve only a single interaction between the user and the mobile device. For example, the user may need to press a particular number on a numeric key pad or a soft key on a touch screen display of the mobile device. Additionally, the single interaction may comprise speaking into a microphone on the mobile device or shaking the mobile device to activate an accelerometer inside the mobile device. Some transactions, meanwhile, may involve multiple interactions.
If however, at decision point 604 the merchant is not recognized as a trusted merchant, process 600 proceeds along the “no” path to operation 618. At operation 618 the user is queried regarding if and how to proceed with a purchase at this merchant. For example, the user may decline to interact with this non-trusted merchant. Alternatively, the user may elect to login to the merchant even though it is not a trusted merchant and proceed to complete a purchase.
At operation 706, user information to share with a merchant is selected. The user information may include any or all of the user information 122 shown in
Next, at operation 708 a transaction is initiated between the merchant and the mobile device when the mobile device is at the merchant. The transaction may be verified according to the level of transaction verification indicated at operation 704. As discussed above, in some implementations, this may comprise zero interaction 710 and in other implementations this may comprise a single interaction 712 (or more) between the user and the mobile device. Setting up the mobile device in advance can establish default behavior when the mobile device is present at a merchant location. In some implementations, this setup information may expire after some length of time such as 24 hours. Upon expiration, the level of transaction verification may be reset to require a complete login for every merchant or in some implementations the number of interactions required may be raised incrementally (e.g., zero interaction merchants now require a single interaction, single interaction merchants now require at least two interactions with the mobile device, etc.). In other implementations, the setup information may not expire but rather persists until the user makes a change.
The user may initiate a transaction 804 through interaction with device 802. Device 802 may be the mobile device 104 or it may be a different computing or communication device such as a telephone, a desktop computer, laptop computer, thin client, set top box, game console, or the like. Device 802 may be connected directly or indirectly to a network 806. The network 806 may be the same network as network 116 illustrated in
The user 102 later arrives at the merchant 106 with his or her mobile device 104. Recall that the mobile device 104 may also be associated with the user identifier 208 as illustrated in
For example, a user may make a hotel reservation from his home computer. The reservation along with his user identifier is transmitted across a communication network to the computer systems of the hotel. Some time (e.g., days) later when the user arrives at the hotel and his mobile device is detect at the geolocation of the hotel, the user identifier contained in his mobile device is used to retrieve the reservation. After confirming payment, such as by a credit card also linked to his user identifier, the hotel sends a text message or other communication to his mobile device that contains his room number. This may happen while he is walking through the lobby to the elevators without ever stopping at the front desk. Once at his room, the presence of his mobile device outside the door may be detected by a wireless communication network in the hotel and the door may be automatically unlocked. Room keys may be provided inside the hotel room. In implementations in which the user identifier is also linked to a user profile (and the user has elected to share his user profile with the hotel), the user profile may be used to customize his guest experience at the hotel by, for example, instructing the hotel staff to place his favor type chocolate on the pillow. Similar to the purchase of goods, the system can provide a friction-free experience for the purchase of services.
As a further example, the architecture and systems described herein can be applied to immigration and border security. In this context, the transaction 804 may be the granting of entry to a country. Initially, the person wishing to travel to a different country may enter user information about the potential trip into a computing device 802 and associate that information with the transaction 804 as well as a user identifier 208 for the potential traveler. In some implementations, a passport number could be used as the user identifier 208. Upon arrival at immigration in the destination country, mobile device 104 carried by the traveler may signal to the immigration authority that this person has arrived and is requesting entry. In some implementations, the user identifier 208 may be associated with a mobile device 104, such as a mobile phone, that the user 102 is instructed to bring when they travel to the other country. In other implementations, the mobile device 104 may be a miniaturized electronic device that is attached to the user's passport as an entry visa. In yet other implementations, the passport itself may comprise the mobile device 104 and an RFID in the passport may be the user identifier 208. This system may reduce the friction associated with processing people entering a country by allowing the immigration transaction to be partially completed in advance and by automatically identifying the people and the corresponding information when they are located at an entry point.
Upon arrival at the merchant's geolocation, the mobile device is detected at the merchant in operation 904. The detection may be direct such as implementations in which a signal broadcast by the mobile device is picked up by a receiver at the merchant. Alternatively, the detection by be indirect or inferred by correlating a current geolocation of the mobile device with a geolocation of the merchant. At operation 906, the presence of the user is communicated to the merchant. The communication may trigger the merchant to access the transaction.
User information may be provided to the merchant at operation 908. The user information may be provided directly from the memory of the mobile device or a user identifier associated with the mobile device may be used to retrieve user information from a network or other remote data source. As discussed earlier, the user information may include payment information, a user profile, and the like. The user profile may include user preferences that the merchant uses to modify the transaction. User preferences may include such things as window or aisle seat on an airplane, smoking or non-smoking rooms in a hotel, and the like. Next, at operation 910, the transaction between the user and the merchant is completed. Completion may include collecting a payment, confirming a reservation, making a purchase, etc.
Following completion of the transaction, at operation 912, the merchant may send a message to the mobile device confirming completion of the transaction. The message may be a receipt for the transaction, or in some implementations, it may be a code or other information that is necessary to access a secure location such as a hotel room or an airplane. For example, the message may comprise a boarding pass barcode that can be displayed on a screen of the mobile device and scanned by conventional equipment when the user boards an airplane. In other implementations, the message may be an electronic token that provides additional functionality to the mobile device. For example, the electronic token may allow the mobile device to broadcast a signal (e.g., analogous to a garage-door opener) that may be used to open a door and gain access to the secure location.
Illustrative Parent and Child Devices
The satellite 112 and the radio antenna 114 are the same as shown in
The merchant 106 may also have a connection to the network 1010 over which information may be shared with either the child device 1004 or the parent device 1008. The child device 1004 may communicate with the merchant 106 across the network 1010 and/or communicate directly with the merchant 106 over a direct communication link 1012. The direct communication link 1012 may be similar to the direct communications link 120 illustrated in
An indication of the transaction is transmitted to a parent device at operation 1108. The indication may inform the user of the parent device about the details of the transaction between the child device and the merchant. In some implementations, the indication may be provided in real-time to the parent device. A record or log of transactions of the child device may be maintained for access by the user of the parent device. The log may store any combination of transactions initiated, completed, and/or denied. In some implementations the log may be similar to the transaction record 406 illustrated in
At decision point 1110, is determined whether or not parental authorization is required. When parental authorization is not required, process 1100 proceeds along the “no” path to operation 1112. At operation 1112, the transaction between the child device and the merchant is completed. In some implementations, the transaction may be completed based in part upon a user profile associated with the child. Furthermore, in the same or different implementations, a user profile associated with the parent may also affect how the transaction is completed. For example, if the child has indicated that he or she wishes to automatically a purchase particular candy upon entering a candy store, that portion of the child's user profile may be used to complete a purchase of that type of candy. The user profile associated with the parent may be used for, among other things, a source of payment information to complete the candy purchase.
When parental authorization is required, the process 1100 proceeds from decision point 1110 along the “yes” path to decision point 1114. At decision point 1114, it is determined whether or not the parental authorization has been granted. When parental authorization is granted, for example by the parent interacting with the parent device, process 1100 proceeds along the “yes” path to operation 1112 and the transaction is completed. However, when authorization is denied the process 1100 proceeds along the “no” path to operation 1116 and the transaction is terminated. Termination of the transaction may result in a message being sent to the child device and/or the merchant.
Security for Mobile Devices
The user may begin his workday at his home which has a fixed geolocation. Typically he—specifically his mobile device—may be at home from approximately 6:00 PM until approximately 7:00 AM and this comprises a first temporal-geo-location 1202 for his workday. Commuting from home to work may involve driving along the road to work between approximately 7:00 AM to approximately 7:30 AM. His automobile may include an additional device, such as an on-board navigation system, that is also associated with his user identifier 208, and thus, also contributes to building a map of temporal-geo-locations for the user. He may use the same route every day in commuting to work so the systems of the user device may recognize this temporal-geo-location 1204 even though it is not a single fixed position but rather a series of geolocations and a series of time points. After arriving downtown, the user's day may include another temporal-geo-location 1208 that comprises his walk from a parking area to his office between approximately 7:30 AM and approximately 7:45 AM. While at the office the user and the user device may move around within the office but remain at the geolocation of the office from about 7:45 AM to about 12:00 PM. This is another temporal-geo-location 1210.
Up until lunchtime this user's typical weekday schedule may be fairly consistent. However, during lunch he may move to a variety of geolocations associated with various restaurants shown here as Restaurant A, Restaurant B, and Restaurant C. The user may generally be inside one of the restaurants from approximately 12:10 PM to approximately 12:50 PM. This temporal-geo-location 1212 may have a well-defined time but a loosely defined location. For example, any geolocation within a 10 minute walk of the office may be deemed part of this user's typical weekday movements during the lunch hour. After lunch the user may return to the office. The office is at the same geolocation it was during the morning, but the time period is different so being in the office from about 1:00 PM until about 5:00 PM creates yet another temporal-geo-location 1214 in the map of this user's workday.
The user may have more than one route he takes home from work. During the winter, for example, the user may take a more direct road home leaving office at about 5:10 PM and arriving home at about 6:00 PM. This creates a temporal-geo-location 1214 across a range of space and time similar to the temporal-geo-location 1204 representing the road to work. In the summer, this user may take the scenic route home. The road home in summer may have a different geolocation in all or in part from the road home in winter. The road home in summer may also take longer so that while the user leaves the office at 5:10 PM he does not arrive home until 6:10 PM. This creates an alternate temporal-geo-location 1216 to the temporal-geo-location 1214 representing the road home in winter. Depending on the security settings of the mobile device, the mobile device may not trigger a security event no matter which route the user takes home even if he uses the winter road during the middle of summer. Alternatively, if stricter security settings are applied then taking the summer road during midwinter may trigger security event, but during mid-March the mobile device may tolerate the user taking either road without triggering a security event.
By recording times, dates, and geolocations as the mobile device is used and moved it is possible for a security system, for example security module 214, to learn what are typical movements through space and time. This “geolocation signature” of the user can be stored in a data file as a series of time-location data points. Some or all of these data points may be layered together to create a multidimensional map containing past geolocation and time information for the mobile device.
A map is created from movements of the mobile device over time based on a plurality of the temporal-geo-locations at operation 1308. As indicated above, this may be a multidimensional map comprising a latitude dimension, a longitude dimension, a time dimension, and a date dimension. Including additional and/or alternate dimensions in the map is also possible. This map may become more detailed, and potentially more useful, as a greater amount of data is accumulated. For example, when a user initially purchases a mobile device it may not be possible for the mobile device to detect whether or not it has moved away from the user's “regular” temporal-geo map. If the user knows that he or she will be moving in ways that are atypical (i.e., “going off the map”), the user may manually turn off the recording of temporal-geo-location data points. This may prevent inclusion of data into the map that would degrade rather than improve the accuracy of the map.
In order to detect whether or not the mobile device has been stolen, misplaced, or is otherwise in the wrong place at the wrong time, decision point 1310 may compare the current temporal-geo-location of the mobile device with the map and determine whether or not the current temporal-geo-location varies more than a threshold amount from the map. In some implementations, this comparison may be achieved at least in part through the use of artificial intelligence, heuristics, or fuzzy logic. In some implementations, the threshold may be configurable by the user of the mobile device. The analysis may also draw upon calendar or scheduling information of the user to see if the user has a scheduled trip that varies from his regular map. The calendar information may be included in the user information 210 and provided to the security module 214.
When an amount of variance is less than the threshold amount, process 1300 proceeds along the “no” path and returns to decision point 1310 to once again query whether or not the mobile device has varied too far from the map. This loop may be repeated continuously, periodically, or randomly. The frequency of repeating this loop may be based in part upon processor power of the mobile device 104, a velocity at which the mobile device 104 is moving, and/or other factors. For example, the frequency of performing the analysis at decision point 1310 may be lower when the mobile device 104 is moving at a walking pace and the frequency may be higher when the mobile device 104 is moving at a highway speed (e.g., while in a car).
The threshold amount may also be based at least in part on the presence of other mobile devices in the same geolocation or near to the mobile device. For example, a user may vary from his or her established map during a vacation. However, during the vacation the user may travel with his or her family members who may have their own mobile devices. In one implementation, the mobile devices of the family members (or, as a further example, coworkers) may be associated with each other. One type of association is the parent-child relationship illustrated in
Returning to process 1300, when the current temporal-geo-location varies more than a threshold amount, process 1300 proceeds along the “yes” path to decision point 1312. At decision point 1312 the threshold may be adjusted based on the presence of other mobile devices in the same geolocation as the mobile device. When the threshold is adjusted, process 1300 proceeds along the “yes” path and returns to decision point 1310 to reevaluate based on the adjusted threshold. When the threshold amount of variance is not adjusted, process 1300 proceeds along the “no” path to operation 1314 and initiates a security event. The security event may comprise shutting down the mobile device, initiating an automatic phone call or text message to another device that includes the current location of the mobile device, requiring input of a password before the mobile device can be used, and the like. The user 104 may manually turn off the security events if, for example, the user 104 is travelling to a new place (or travelling at a new time) and wishes to avoid “false positive” security events.
At operation 1402, biometric data is received from a sensor of the mobile device. Many mobile devices, such as the mobile device 104 illustrated in
Next at operation 1408, the biometric data is analyzed. In some implementations, the biometric data may be analyzed by a processor and software present on the mobile device itself. This implementation may allow the mobile device to offer stand-alone confirmation of a user's identity without a need to access a network or other computing device. In other implementations, the biometric data may be sent from the mobile device to another computing device for analysis. This implementation may allow more sophisticated and computationally intensive techniques for analyzing biometric data than could be readily implemented on a mobile and potentially low-power device. Analysis of the biometric data may convert analog input into digital data or convert a complex set of data such as a fingerprint into a relatively simple string of data like a hash code. The analysis of the biometric data may be matched to the type of data received. For example, if the camera 222 is used to collect biometric data by taking a picture of a person's face, that picture may be analyzed using facial recognition techniques. Alternatively, if the microphone 1404 is used to record a sample of a voice, then that data may be analyzed by using voice recognition techniques. For added levels of security, multiple types of biometric data may be used together such as, for example, taking a picture of a person's face and recording that person's voice then analyzing both sets of biometric data.
At decision point 1410, a determination is made as to whether the analysis of the input of biometric data matches stored biometric data associated with the mobile device. For example, the hash code generated from a fingerprint scan could be compared to a stored hash code that the user entered while she was setting up the mobile device. In some implementations, the stored biometric data which is used for comparison is stored locally on the mobile device. The biometric data may be stored, for example, as part of the user information 210 shown in
When the analysis of the biometric data matches the stored biometric data, process 1400 proceeds along the “yes” path and grants access to a functionality of the mobile device at operation 1412. The functionality may comprise any type of operation feature, data, and the like available on or implemented by the mobile device. For example, the ability to initiate and complete a transaction with a merchant is one type of functionality. The ability to make phone calls is a type of functionality on mobile telephone devices. Associating a particular mobile device with an individual user's identity is another type of functionality. For example, a network server such as the server(s) 118 illustrated in
If, at decision point 1410 it is determined that the analyzed biometric data does not match the stored biometric data, process 1400 may proceed along the “no” path and initiate a security event at operation 1414. The security event may be anything from shutdown and complete deletion of all stored data on the mobile device to a warning message displayed on the mobile device. In some implementations, the security event may limit functionalities of the mobile device, such as to those functionality that do not incur additional charges. Other types of security events may include sending an e-mail or making a phone call that communicates the current location of the mobile device. The security event at operation 1414 may be the same or different than the security event triggered at operation 1314 illustrated in
Security events may be triggered by other mechanisms besides variance from a temporal-geo-location map or failure of a biometric login. In some implementations, the user may be able to manually initiate a security event remotely from the mobile device. Some mechanisms of achieving this include calling a phone number, sending an e-mail, entering a command from a webpage, or the like. The web page may be a security web page for that mobile device that shows a current geolocation of the mobile devices as well as past transaction data and the like. For example, if the user suspects that his or her mobile device was lost or stolen that user could call a certain phone number, enter a code, and then a signal would be sent over a network and broadcast to the mobile device causing the mobile device to temporarily shut down. In other implementation, different triggers may be used to initiate a security event. Some of those triggers include financial transactions, for example, sending out an alert message when a large purchase is initiated using the mobile device.
Advertising and Promotions
One user 102 and one mobile device 104 receiving the advertisements 1510 may be the same as illustrated in
Each of the mobile devices 104 and 1514 may receive geolocation information from a satellite 112 or other source. The respective mobile devices 104 and 1514 may receive geolocation information from different sources (e.g., a radio antenna for one mobile device and a WiFi hotspot for the other mobile device). The geolocation of the mobile devices 104 and 1514 may be matched with geolocation(s) 418 associated with advertisement content 416 as illustrated in
Next, at operation 1606, merchants are identified based on the geolocation of the mobile device and on the advertisement preference of the user. The identified merchants may include only merchants within a specified distance from the mobile device. This can limit the possible source of advertisements to only those merchants that are located proximate to the geolocation of the mobile device. For example, if the user is walking down a street lined with restaurants, restaurants along that street may be eligible to advertise on the mobile device but restaurants located across town would not. A threshold or radius within which merchants are identified as being proximate to the mobile device may vary based on the type of advertisement. For example, restaurant advertisements may only be sent to mobile devices that are within a quarter mile of the restaurant geolocation. However, hotel advertisements may be sent to users with mobile devices within five miles of the hotel geolocation. Additionally, the advertisements may be sorted by time such that restaurant advertisements may be more common or cover a larger geographic area in the hours before dinner time and hotel advertisements may cover a larger geographic area earlier in the day but progressively narrow the geographic focus as it becomes night.
Once a pool of merchants has been identified based on at least geolocation and advertisement preference, bids are received from those merchants at operation 1608. The bids may be received and processed by the bidding module 312 illustrated in
At operation 1610, an advertisement is selected. The selected advertisement may be determined based on the bid price, the user preferences, and other factors such as, for example, whether the merchant has enough money in an advertising account to pay the bid price. In some implementations, a winning bid that determines the selected advertisement may be the bid associated with a largest amount of money. Other bidding or auction arrangements are also possible such as, for example, the highest bidder paying an amount bid by the second highest bidder.
Next, at operation 1612, the selected advertisement is presented on the mobile device. The advertisement may be supplied from the advertisement database 126 illustrated in
At operation 1702, a number of mobile devices at a merchant is determined based on geolocation information provided by each of the mobile devices. For example, each mobile device could detect its own geolocation based on a satellite or other system, and expose that information to a server(s) 118 for inclusion in a map 310 in which the geolocations of multiple mobile devices are correlated with the geolocation of a merchant. The number of mobile devices may represent a number of unique users present at that geolocation.
Next, at decision point 1704, the number of mobile devices at the merchant is compared to a threshold number. The threshold number may be set by the merchant as, for example, a number of people the merchant would like to have on its premises. In this implementation, the threshold may be an integer number. The threshold number may be based at least in part on a number of mobile devices at the merchant for which the merchant is designated as a trusted merchant. For example, if the merchant wishes to bring in new users with the hopes that they will designate this merchant as a trusted merchant, the threshold may be set as a ratio such the threshold is exceeded when, for example, more than a third of all mobile devices present do not designate this merchant as a trusted merchant. When the number of mobile devices at the merchant exceeds the threshold number, process 1700 proceeds from decision point 1704 along the “yes” path to operation 1706 and provides a promotion to the users. The promotion may be a discount for a good or service available at the merchant. The promotion may be provided to all the users present at the merchant or to only a subset. For example, to reward loyal customers, a coupon may be sent to the mobile devices of users who have transacted with this merchant in the past.
The promotion may be personalized for each of the users of the mobile devices based on user information associated with the mobile device. This using information may be the same as the user information 210 illustrated in
If however, the number of mobile devices at the merchant does not exceed the threshold, process 1700 may proceed along the “no” path to operation 1708 and send a message to the mobile devices. The message may be a notification of how many more devices must be present at the merchant in order to cross the threshold. This could be a source of viral marketing by encouraging users to call or text their friends to come to this merchant location—with their mobile devices—so that the threshold is crossed and everybody receives the promotion. In implementations, in which mobile devices are counted as being at the geolocation of the merchant only when the user of that mobile device opts to expose his or her geolocation to the merchant this may encourage reticent users to share this information in order to receive the promotion. Many other implementations that take advantage of the “peer pressure” effect by providing a promotion for aggregate behavior are also possible.
There may also be instances in which a large number of customers, as indicated by a number of mobile devices, may be undesirable to the merchant and or the users. Thus in one implementation, the “advertisement” may comprise a notification about how many mobile devices are present at a merchant and to what extent this number exceeds a maximum or threshold number. For example, a restaurant may report that more mobile devices are present at its geolocation than the restaurant has seats. With this information a user could be forewarned that he or she may have to wait for a table at that restaurant. As another example, an airline may identify mobile devices of users scheduled to be on a flight that are not yet at the airport (or not within a threshold distance of the boarding gate) to inform these users that the fight is overbooked. This implementation may use geolocation in conjunction with user information 122 (e.g., the flight reservation) to provide an offer to take a later flight (perhaps in exchange for an upgrade or such) to those customers most likely to avail themselves of that offer. In these instances the process flow from decision point 1704 may be switched in that the message is sent out if the number of user devices exceeds the threshold number.
After sending the message at operation 1708, process 1700 may return to operation 1702 and again determine a number of devices at the merchant. This may repeat until the threshold is crossed or until a period during which the promotion periods ends. The process illustrated in
Bootstrapping from a Transaction
The zero-click or other low-friction transactions are possible when the user 102 and the merchant 106 are aware that they can interact with each other in these ways. Users may be unaware that the merchant they are patronizing is potentially able to complete transactions via the users' mobile devices 104. Therefore, it may be advantageous if inferences about mobile device 104 locations and user purchases are “bootstrapped” in order to introduce users 102 to merchants 106. Even absent knowledge of the user 102, the mobile device 104, the merchant 106, and/or the server(s) 118 may determine that the mobile device 104 is located at a merchant 106 capable of interaction with mobile devices 104. This provides an opportunity for a message, sent to the mobile device 104 or otherwise, to invite the user 102 to configure his or her mobile device 104 for interaction with that merchant 106. However, these invitations could potentially be an annoyance to the user 102 particularly if he or she is visiting a merchant 106 (with his or her mobile device 104) at which the user 102 does not intend to make a purchase. For example, the vegetarian picking up his friend at a steakhouse probably does not wish to add that steakhouse to a list of favorite or trusted merchants. The user 102 may also be in a hurry and simply want to complete a purchase quickly (e.g., buying a cup of coffee on the way to work) without having to read a message on his or her mobile device 104.
If, however, the user 102 has already completed a transaction with the merchant 106, it may be much more likely that the user 102 will want to use his or her mobile device 104 for completing a future transaction with that merchant 106. Once a transaction is complete, it is also more likely that the user 102 will be able to leisurely configure his or her mobile device 104. The techniques discussed above for matching the user 102 with a transaction (e.g., user identifier 208, device identifier, etc.) are not available because the initial transaction is completed without the mobile device 104. Thus, another technique may be used to match a “regular” transaction (i.e., one not tied to the mobile device 104) with the user 102 and the user's mobile device 104.
In some implementations, the payment information may be stored in a memory of the mobile device 104. However, the payment information may also be stored on a network server such as the server(s) 118 shown in
The merchant 106 may store, either temporarily or permanently, payment information and transaction details for recent transactions 1802 completed at the merchant 106. The recent transactions 1802 may be stored on the point-of-sale device 110 at the merchant 106, on the merchant server 108, or elsewhere. In this example, the recent transactions 1802 were funded with four credit cards. Of course, in some implementations the number of recent transactions 1802 may number in the hundreds or thousands and many different payment types (e.g., credit cards, debit cards, electronic checks, gift cards, cash, etc.) may be included. The payment information stored in the recent transactions 1802 may be partial payment information. For example, the merchant 106 may store only the last four digits of a credit card number. Other information may also be included such as the type of credit card, the expiration date, the cardholder's name, and such. For other forms of payment, analogous information may be stored (i.e., a bank routing number for a check payment). Storing only partial payment information protects privacy and reduces opportunities for fraudulent use, yet also supplies enough information to match the user's credit card 1804 with the partial payment information 1806 stored in the recent transactions 1802.
At operation 1904, it is determined that the user's mobile device is located at a merchant capable of conducting transactions facilitated by the mobile device. The determination may be performed by the mobile device, the merchant, or a network server using any of the techniques discussed in earlier sections. Either the mobile device or the merchant may generate an indication that the mobile device is at the merchant. Additionally or alternatively, it may be determined that the mobile device of the user is at the merchant by comparing a detected location of the mobile device (e.g. latitude and longitude determined by GPS) with a stored location of the merchant (e.g. a map or database of merchant locations).
At operation 1906, the merchant is notified that a mobile device capable of facilitating transactions is present at the merchant. If the mobile device has an established relationship with the merchant (e.g., if the merchant is designated as a trusted merchant), the merchant and the mobile device may proceed to conduct a transaction or purchase along the lines discussed in the preceding sections. If, however, the merchant does not have a previous relationship with the user or with the mobile device, the merchant may not yet know which transaction, if any, should be associated with the mobile device.
At operation 1908, at least partly in response to the notifying at 1906, customer identification information for users who recently completed transactions made at the merchant is received. The customer identification information may be sent out by the merchant after the merchant receives notification that the mobile device is located at the merchant. The customer identification information may be received by a network server such as server(s) 118. In other implementations, the customer identification information may be received by a merchant computer such as the merchant server 108 or alternatively by the mobile device itself.
The customer identification information may include information derived from recent transactions made during a previous period of time (e.g., 30 seconds, one minute, 10 minutes, etc.). The length of the previous period of time may be context dependent. For example, a merchant with a higher frequency of transactions (e.g., a coffee shop) may provide customer identification information for a shorter period of time than a merchant with a lower frequency of transactions (e.g., a formal restaurant). In one implementation, the previous period of time may be scaled to include customer identification information on a fixed number of users. For example, the period of time may be lengthened or shortened so that the number of users is approximately 100. In other contexts, the period of time may be based upon behavior of the mobile device. For example, if the mobile device is present at the merchant for eight minutes, then the previous period of time may be that eight minute time period. Additionally, the previous period of time may be forward-looking in that the time period may be based on when the mobile device is initially present at the merchant. For example, the merchant may provide customer identification information for a five minute period that begins when the mobile device first enters the merchant.
In some implementations, the customer identification information may be filtered before it is provided by the merchant. For example, the server(s) 118 may provide information about the user such as information from the user profile 404. This information about the user, although not necessarily sufficient to identify the user uniquely, may allow the merchant to make a best guess as to which customer identification information is likely to match. For example, the user has a preference setting for decaffeinated coffee, all recent transactions to purchased regular, caffeinated coffee may be filtered out of the recent transactions.
At decision point 1910, the customer identification information is compared with identifying information of the user to determine if there is a match. The determination may be based in part on partial payment information that is sufficient to identify the users. When there is no match, the process 1900 proceeds along the “no” path and returns to operation 1908. In some implementations, this may repeat (e.g., every 60 seconds) until the mobile device leaves the merchant or a match is found. When there is an identification information match, for example a partial credit card number match as shown in
At operation 1912, transaction information for the transaction paid for by using the payment information of the user is received. The transaction information may include a price, a description of the item(s) purchased, a timestamp, and the like.
Next, at operation 1914, a message is sent to the mobile device. The message may be sent from the merchant or from a server. The message may ask if the user wishes to designate the merchant as a trusted merchant. Athought the user has already completed a transaction with the merchant at this point, receiving numerous such notification messages throughout the day may be burdensome or unpleasant for the user. Therefore, the user may be able to deactivate the messaging functionality and/or request that numerous messages be aggregated and presented with a lower frequency (e.g., once a week). Additionally or alternatively, the notifications may be provided to the user on a web page or other format that is accessible from more than just the mobile device. For example, the user may access one web site to add new merchants to his or her list of trusted merchants and view merchants at which he or she completed “regular” transactions but has not yet designated a trusted merchants.
At decision point 1916, the user indicates if he or she wishes to add the merchant to a list of trusted merchant(s) 408 as discussed above. If so, process 1900 proceeds along the “yes” path to operation 1918 and the merchant is added to the list of trusted merchant(s) 408. However, if the user does not want to include this merchant in the list of trusted merchant(s) 408, process 1900 proceeds along the “no” path to operation 1920.
The message may also ask if the user wishes to store the transaction information. The transaction information may be stored as part of a transaction record 406, see
At decision point 1922, the user indicates a desire to store or not store the transaction information. If the user wishes to store the transaction information, the process 1900 proceeds along the “yes” path to operation 1924 and stores the transaction information in the transaction record 406. The transaction information, like the transaction record 406, may be stored on the mobile device, a server, or elsewhere. If the user does not wish to store this transaction information (e.g., perhaps the user knows that he or she will not patronize this merchant again) then the process 1900 proceeds along the “no” path to operation 1926 and does not store the transaction information.
If the transaction information is stored, the process 1900 may proceed to operation 1928 and if, at a later time, it is determined that the user is again at the merchant, a message may be sent to the mobile device asking if the user wishes to conduct another transaction with the merchant based at least in part on the transaction information stored in the transaction record 406. For example, the next time that the user returns to the merchant he or she may be able to repeat easily the earlier transactions with a single touch of the mobile device.
Independent of determining whether or not the user wishes to add the merchant as a trusted merchant, the message may also ask the user if he or she wishes to store the transaction information 2010 in a transaction record. Again, the user may reply to the message either by selecting “yes” 2012 or “no” 2014. The user interface 2000 may provide an additional soft button 2016 through which the user may indicate that he or she wishes to store this transaction information as a default transaction. The default transaction may be later implemented along the lines discussed above with respect to operation 708 of
A map 310 or another data file stored on the server(s) 118 may contain geolocations of merchants 106. Correlation between a particular merchant 106 and a geolocation of a mobile device 104 may be performed by a mapping module 2102. The mapping module 2102 may compare measured coordinates of the mobile device 104 (e.g., GPS coordinates) with stored coordinates of the merchant 106 (e.g., a latitude and longitude stored in the map 310). Based on that comparison, the mapping module 2102 may determine that the measured coordinates of the mobile device 104 are within a predetermined proximity of the stored coordinates of the merchant 106, and thus, determine that the location of the mobile device 104 correlates with the location of the merchant 106.
The server(s) 118 may also include a transaction module 308 configured to receive purchase information about the purchase made using the user's payment information 402. For example, if the user 102 purchased a tall latte for $3.75, as shown in
The server(s) 118 may also include an identification information analysis module 2104 to determine if there is a match between the user's identification information 402 and the customer identification information for the recent purchases from the merchant 106. Once the server(s) 118 receives the customer identification information from the recent purchases that were made at the merchant, the server(s) 118 can compare that information with the payment information 402, user profile 404, or other identification information associated with the user identifier 208 to determine if a match exists.
In other implementations, the analysis of identifying information 2100 may be performed by the merchant 106 at, for example, the point-of-sale device 110 or the merchant server 108. In this implementation, the identification information analysis module 2104 may provide the identifying information 2100 of the user associated with the mobile device 104 to the merchant 106. The identification information analysis module 2104 may need to receive authorization from the user 102 before providing the identifying information 2100 of the user to the merchant 106. After the merchant 106 compares the user's identifying information 2100 to recent customer identification information, the identification information analysis module 2104 may receive a response from the merchant 106 indicating whether or not the identifying information 2100 of the user matches any of the customer information associated with recent purchases at the merchant 106.
Messages to the mobile device 104 may be generated by a messaging module 2106 in the server(s) 118. The messaging module 2106 may be configured to send messages to the mobile device 104 in response to input from the payment information analysis module 2104 indicating that a match exists. The messaging module 2106 may generate messages such as those shown in
A trusted merchant management module 2108 may also be present on the server(s) 118 and add merchants to the list of trusted merchants 408 when the identification information analysis module 2104 determines that a match exists between the payment information of recent purchases from the merchant and the identifying information 2100 associated with the user identifier 208.
Illustrative Loyalty Points
The techniques described above include ways for a user of a mobile device to complete transactions with merchants with lower friction than conventional customer-merchant transactions. Other techniques also described above include tools for a merchant to send advertising or promotions to the mobile device. Coupling the ease of transactions using the mobile device and the ability to send targeted advertisements based on device location (as well as other factors) creates a compelling business model.
However, merchants are continually striving to gain new customers and repeat business from previous customers. One way of doing so is to provide coupons or discounts for new customers and/or for repeat customers. Following the steps to receive a discount can increase friction in a transaction because the purchaser must provide a paper coupon, a membership card, or the like in addition to placing an order and providing a payment. Similar to the techniques described above for using a mobile device to reduce friction associated with a transaction, mobile devices can also reduce the friction associated with receiving the benefit of a coupon or a discount.
Multiple users 102 and 2202 may complete transactions with a merchant 2206 and accumulate punches on their respective punch cards 2208 and 2210. The user 102 may provide a payment 2212 from his or her mobile device 104. The merchant 2206 may in turn provide the user 102 with a good or service 2214. For example, the user 102 may receive a cup of coffee from the merchant 2206. This stage of the transaction is similar to the transactions discussed above in the preceding sections.
The mobile device 104 of the user 102 may also store or otherwise have access to a file representing a punch card 2208. In some implementations, the punch card 2208 may be stored on the server(s) 118 or elsewhere in the network 2216 and associated with the mobile device 104 by a user identifier 208 or other unique identifier stored on the mobile device 104. After completing the transaction, the punch card 2208 may receive “a punch” from the merchant 2206 commemorating that the transaction did indeed occur. By providing the punch card 2208 and the punches electronically to the mobile device 104, the user 102 does not have to remember to bring a paper punch card with him or her to the merchant 2206. Also, in configurations in which the punches are provided automatically, the user 102 will not miss out on receiving a punch because the act of “punching” can be completed without user interaction. The merchant 2206 may also benefit from this use of punch cards 2208 and 2210 because encryption or other techniques can make forging an electronic punch much more difficult than forging or fraudulently adding punches to a paper card. Also, communication between the mobile device 104 and the merchant 2206 provides opportunities for the merchant 2206 to track user behavior in ways that are not possible with paper punch cards.
Another user 2202 may interact with the merchant 2206 via a mobile device 2204 that stores a punch card 2210 that contain sufficient punches to be redeemed for a good or service 2218. The merchant 2206 may set a predetermined number of punches that are required in order to receive a free or discounted good or service 2218. The predetermined number of punches may be any number such as, for example, ten or any other suitable number. When the user 2202 has accumulated the predetermined number of punches on the punch card 2210, he or she may provide the punch card 2210 as payment 2216 for a good or service 2218 from the merchant 2206. For example, the mobile device 2204 or the merchant 2206 may recognize the presence of the completed punch card 2210 and may suggest that this punch card 2210 be redeemed to consumate the transaction.
Each of the mobile devices 104 and 2204 may communicate with each other through the network 2216. The network 2216 may be the same as the network 116 shown in
Alternatively or additionally, punches may also be traded or bartered as well as bought and sold. For example, the user 102 who received one punch for buying a cup of coffee from the merchant 2206 may wish to trade that “coffee” punch for a punch that can be redeemed at a merchant which sells tacos. The punch card marketplace 2218 may create a forum for users to list the punches they have to offer and the punches they desire to receive. Hybrid transactions combining trade and payment are also possible (e.g., trade one “coffee” punch plus $0.50 for one “taco” punch). The punch card marketplace 2218 may, in some implementations, be a component of the server(s) 118. The ability of punches to be traded or sold may be limited by the merchants that issue the punches. For example, the merchant 2206 may restrict selling and/or trading of punches. The merchant 2206 may also allow limited trading and selling of punches, but may, for example, require that any punch card 2210 used as payment 2216 for a good or service 2218 have at least half the punches received directly from the merchant 2206 (i.e., punches provided after the user 2202 made a purchase himself or herself).
The merchant 2206 may initiate use of a punch card 2208 by sending the punch card 2208 to a mobile device 104. When the merchant 2206 processes a payment 2212 from the mobile device 104 for a purchase of a good or service 2214 that may trigger the merchant 2206 to send a punch to the punch card 2208 to the mobile device 104 that was used to make the purchase. In this illustrative example, the user 102 buys a cup of coffee from the merchant 2206 and receives a punch card 2208 with one punch. In some implementations, the good or service 2214 that is the subject of the purchase (e.g., a cup of coffee) may be associated with the punch and a predetermined number of punches will be accepted by the merchant 2206 as payment for a future purchase of the same good or service 2214. For example, 10 drip coffee punches can be redeemed for a free drip coffee but not for a mocha (i.e., the punches may be used to receive the same or similar type of good or service).
Another user 2202 (or the same user 102 at a later time) may go to the merchant 2206 and provide the punch card 2210 as payment 2216 for a good or service 2218. In that case, the merchant 2206 receives a predetermined number of punches from the mobile device 2204 and authorizes a good or service (e.g. a cup of coffee) 2218 to be provided to the user 2202 of the mobile device 2204. A point-of-sale device 110 such as shown in
At operation 2306, a loyalty point account is established for the mobile device. In other implementations, the loyalty points may be provided the the mobile device as a reward to the user for completing various actions other than making a purchase from the merchants. A punch card may be sent to the mobile device as a type of advertising without immediately providing loyalty points (e.g., here is a punch card to our coffee shop, please make a purchase to receive your first punch). At operation 2308, the loyalty point account is established on the mobile device in response to completing the transaction at operation 2304. For example, after completing a first transaction with a merchant, the merchant may create a loyalty point account for the mobile device. Alternatively, at operation 2310, the loyalty point account may be established for the mobile device in response to the user of the mobile device performing an action designated by the merchant. The designated act may include listing the merchant as a trusted merchant, referring another user to the merchants, signing up for promotional emails, and the like. For example, in process 700 of
At operation 2312, without regard to how the mobile device received the loyalty points, a number of punches are added to the punch card stored on the mobile device. The points may be added only after the transaction is complete and the merchant has received payment. Adding the points after the transaction is complete may prevent fraudulent accumulation of points or gaining points without actually paying for a good or service or performing a designated act. The number of points or punches added for a given transaction may be based on a number of items purchased (e.g., three punches for a purchase of three coffees), an amount of money spent (e.g., ten points for each five dollars spent), or any other metric associated with the transaction. The number of loyalty points provided to the user may also be based in part on a period of time since the user last completed a transaction with the merchant. For example, the user that has not bought a cup of coffee for a over one week may be incentivized to return to the merchant if offered double points on his or her next coffee purchase. Similarly, the merchant may encourage frequent purchases by offering double points if the user makes another purchase the following day. Many other permutations are possible in which the merchant selects a period of time and a modification to the number of points or punches provided per transaction.
The merchant may be aware of user behavior because the loyalty points are electronic and the merchant may also be aware of user location because the mobile device is location aware. If the merchant has received user consent, this allows the merchant to communicate with the user via the mobile device by sending messages the mobile device. For example, at decision point 2314 the merchant may determine if the mobile device is within a threshold distance. This threshold distance at decision point 2314 may be different than the threshold distance at operation 2302. For example, the threshold distance at decision point 2314 may be sufficiently broad to detect when the mobile device is near but not at the merchant. When the mobile device is within this threshold distance, the process 2300 follows the “yes” path from the decision point 2314 to decision point 2316.
At decision point 2316, it is determined if a number of loyalty points equals the predetermined number. For example, if the merchant sets the predetermined number at ten, then ten loyalty points may be redeemed for a good or service.
At operation 2318, a message is sent to the mobile device. The content of the message may depend on whether the user has accumulated the predetermined number of loyalty points. For example, the message may remind the user that he or she has a punch card or is accumulating loyalty points for a nearby merchant. The message may also indicate a number of points remaining until the user has accumulated the predetermined number of points necessary to receive a good or service (e.g. only one more punch and you can get a free taco) or indicate that the user has enough points to redeem for a good or service.
If the mobile device has less than the threshold number of points, then the process 2300 proceeds along the “no” path from decision point 2316 through operation 2318 optionally sending a message and on to operation 2320 where the loyalty points are saved for possible redemption at a later time.
If the number of loyalty points equals or exceeds the predetermined number, then the user of the mobile device has the option of redeming the loyalty points and the process 2300 proceeds along the “yes” path to through operation 2318 to decision point 2322. At decision point 2322, the user may authorize redemption of the loyalty points. In some circumstances, the user may wish to save loyalty points for use at a later time even though he or she could presently redeem the loyalty points. If the user does not authorize redemption of the loyalty points, the process 2300 proceeds along the “no” path to operation 2320.
However, if the user authorizes redemption of the loyalty points then the process 2300 proceeds along the “yes” path to operation 2324 at which the loyalty points are accepted as payment in exchange for a good or service from the merchant. At operation 2324 the number of loyalty points available to the mobile device is reduced according to the good or service that the user receives in exchange for the punches. Although merchant may frequently provide a free good or service in exchange for loyalty points, it is also possible for merchants to provide a reduced price in exchange for the punches (e.g. collect ten punches and get 50% off your next purchase).
As discussed above, the transaction module 212 is configured to facilitate a transaction with the merchant by providing a payment to the merchant. In some implementations related to electronic currency, punch cards or loyalty points may be the payment. The transaction module 212 may receive location information from the location sensor 230 in order to base the transaction at least in part on a location of the mobile device 104. The transaction module 212 may also be configured to conduct transactions with the punch card marketplace 2218 by being configured to buy, sell, or exchange punches or loyalty points with other mobile devices, servers, other computing devices, or accounts associated with any of the same. The transaction module 212 may be further configured to ask a user if a loyalty point account 2402 will be used as payment to the merchant when the mobile device has accumulated a predetermined number of loyalty points. If the user indicates that the loyalty points will be used as a payment to the merchant, the transaction module 212 may remove the predetermined number of loyalty points from the loyalty point account as part of the transaction. This functionality of the transaction module 212 is similar to the decision point 2322 of the process 2300 shown in
The memory 204 of the mobile device 104 may include multiple loyalty point accounts 2402. The loyalty point accounts 2402 may each correspond to a respective merchant and track a number of purchases made by the mobile device 104 at that merchant. In some implementations, a loyalty point account may be shared across multiple merchants. For example, multiple merchants may agree to a shared framework for providing and redeeming loyalty points so that the account can be redeemed at any of the participating merchants.
In addition to the loyalty point accounts 2402, the memory 204 may include a point management module 2404 and a messaging module 2406. The point management module 2404 may increase a number of loyalty points in a loyalty point account 2402 when the transaction module 212 completes the transaction with the merchant and remove debit loyalty points from the loyalty point account 2402 when loyalty points are provided as payment to the merchant. Unlike paper punch cards or point systems, it may not necessary to provide any tangible object to the merchant, rather the loyalty point account 2204 can remain established in or accessible by the memory 204 of the mobile device 104 and the loyalty points may be removed or transferred to the merchant.
The loyalty points may be accepted by the merchant as payment when the number of loyalty points equals or exceeds a predetermined number. Some merchants have both physical and web stores and transactions on the web that are associated with the user identifier 208 may be the basis for crediting loyalty points to the loyalty point account 2402. In other words, when the user associated with the user identifier 208 stored in the memory 204 of the computing device 104 completes a purchase from the merchant (i.e., even purchases made without the mobile device 104), the point managment module 2404 is configured to add points to the loyalty point account 2402. With this functionality, the user does not miss out on accumulating loyalty points if he or she shops at the merchant in a way that does not use the mobile device 104.
The messaging module 2406 may be configured to receive messages from the merchant such as via wireless transmission received by the network interface 232. In some implementations, the messages may be sent from the merchant when the mobile device is within a threshold distance of the merchant. For example, the messages could notify the user of a number of loyalty points remaining until a number of loyalty points stored in the loyalty point account 2402 equals a predetermined number required by the merchant to redeem the loyalty points for a good or service. The messages could also notify the user that he or she will receive a higher number of loyalty points (e.g., double points) for a future transaction. The messages may also remind the user of the goods or service that he or she can receive from the merchant when the predetermined number of loyalty points are presented as payment. For example, the message may state that “you're only two loyalty points away from receiving a free tall latte” or “stop by your nearby taco store and you'll receive two-for-one loyalty points.”
The redemption may be implemented electronically either through a direct connection with the merchant or via a network as described above. In some implementations, the user interface 2500 itself may be presented to an employee of the merchant and the employee may “cancel” the punch card by, for example, entering a code into the mobile device 104. Similarly, a bar code or other machine-readable image may be shown on the user interface 2500 and scanned by the merchant in order to implement redemption of the punch card. The mobile device 104 may later connect to a server and the local synchronize punch card information with information stored on the server.
The example punch card 2504 is a punch card for a coffee shop. This punch card 2504 has ten punches, which for this merchant is the predetermined number of punches to receive a free coffee. In some implementations, punch cards that have enough punches to redeem for a good or service (e.g., punch card 2502 for a small taco, or punch card 2504 for a coffee) may be visually emphasized by highlighting, coloration, changes in size, order, prominence on the visually display, and the like.
The third example punch card 2506 included in the user interface 2500 is for a punch card that can be redeemed at multiple associated merchants. This punch card 2506 has two out of a required ten punches needed to receive a free or discounted good/service at any one of the associated merchants. The user of the mobile device 104 may decide that he or she does not want to continue accumulating punches for the associated merchants and elect to trade these two punches on the punch card marketplace 2220 for another type of punch such as a “taco” punch. While a few example punch cards have been illustrated, other implementations may emply any other type of similar or different punch cards. Furthermore, while one example design has been illustrated, other implementations may emply any other similar or different type of design.
Conclusion
These processes discussed above are each illustrated as a collection of blocks in a logical flow graph, which represent a sequence of operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the blocks represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks can be combined in any order and/or in parallel to implement the process.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as illustrative forms of implementing the claims.
This application claims the benefit of U.S. Provisional Application Nos. 61/316,527 filed on Mar. 23, 2010 and 61/351,743 filed on Jun. 4, 2010 both of which are incorporated by reference herein in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5294472 | Arnold et al. | Mar 1994 | A |
| 5914472 | Foladare et al. | Jun 1999 | A |
| 6108650 | Musk et al. | Aug 2000 | A |
| 6173269 | Solokl et al. | Jan 2001 | B1 |
| 6327348 | Walker et al. | Dec 2001 | B1 |
| 6343279 | Bissonette et al. | Jan 2002 | B1 |
| 6505046 | Baker | Jan 2003 | B1 |
| 6597770 | Walker et al. | Jul 2003 | B2 |
| 6738749 | Chasko | May 2004 | B1 |
| 6756879 | Shuster | Jun 2004 | B2 |
| 7392534 | Lu et al. | Jun 2008 | B2 |
| 7434723 | White et al. | Oct 2008 | B1 |
| 7657489 | Stambaugh | Feb 2010 | B2 |
| 7725390 | Plant | May 2010 | B2 |
| 7739197 | Jambunathan et al. | Jun 2010 | B2 |
| 7788281 | Cole et al. | Aug 2010 | B2 |
| 7813717 | Huotari et al. | Oct 2010 | B2 |
| 7840222 | Hampel et al. | Nov 2010 | B2 |
| 7853786 | Fultz et al. | Dec 2010 | B1 |
| 7873708 | Durand et al. | Jan 2011 | B2 |
| 7899742 | Benkert et al. | Mar 2011 | B2 |
| 7900847 | Lindahl et al. | Mar 2011 | B2 |
| 8050991 | Popovic et al. | Nov 2011 | B2 |
| 8099109 | Altman et al. | Jan 2012 | B2 |
| 8116731 | Buhrmann et al. | Feb 2012 | B2 |
| 8135624 | Ramalingam et al. | Mar 2012 | B1 |
| 8213898 | Choti et al. | Jul 2012 | B2 |
| 8255698 | Li et al. | Aug 2012 | B2 |
| 8326767 | Ramanujan et al. | Dec 2012 | B1 |
| 8447651 | Scholl et al. | May 2013 | B1 |
| 8521131 | Ramalingam et al. | Aug 2013 | B1 |
| 8606322 | Sabol | Dec 2013 | B2 |
| 8744488 | Cousins et al. | Jun 2014 | B2 |
| 8849310 | Fan et al. | Sep 2014 | B2 |
| 8863307 | Sorek | Oct 2014 | B2 |
| 9107064 | Ramalingam et al. | Aug 2015 | B1 |
| 20010025257 | Sato | Sep 2001 | A1 |
| 20010051911 | Marks et al. | Dec 2001 | A1 |
| 20020046116 | Hohle et al. | Apr 2002 | A1 |
| 20020065713 | Awada et al. | May 2002 | A1 |
| 20020077876 | O'Meara et al. | Jun 2002 | A1 |
| 20020091568 | Kraft et al. | Jul 2002 | A1 |
| 20020123938 | Yu et al. | Sep 2002 | A1 |
| 20020133467 | Hobson | Sep 2002 | A1 |
| 20020143638 | August et al. | Oct 2002 | A1 |
| 20030159066 | Staw et al. | Aug 2003 | A1 |
| 20030208386 | Brondrup | Nov 2003 | A1 |
| 20030208684 | Camacho et al. | Nov 2003 | A1 |
| 20030212609 | Blair et al. | Nov 2003 | A1 |
| 20030220835 | Barnes, Jr. | Nov 2003 | A1 |
| 20040002897 | Vishik | Jan 2004 | A1 |
| 20040019563 | Sines et al. | Jan 2004 | A1 |
| 20040039694 | Dunn et al. | Feb 2004 | A1 |
| 20040056101 | Barkan et al. | Mar 2004 | A1 |
| 20040093620 | Iino et al. | May 2004 | A1 |
| 20050004840 | Wanninger | Jan 2005 | A1 |
| 20050021773 | Shiga et al. | Jan 2005 | A1 |
| 20050177442 | Sullivan et al. | Aug 2005 | A1 |
| 20050221843 | Friedman et al. | Oct 2005 | A1 |
| 20050228719 | Roberts et al. | Oct 2005 | A1 |
| 20050234771 | Register et al. | Oct 2005 | A1 |
| 20050240472 | Postrel | Oct 2005 | A1 |
| 20050267812 | Jensen et al. | Dec 2005 | A1 |
| 20050288719 | Zhang et al. | Dec 2005 | A1 |
| 20060047576 | Aaltonen et al. | Mar 2006 | A1 |
| 20060111955 | Winter et al. | May 2006 | A1 |
| 20060164189 | Tohya et al. | Jul 2006 | A1 |
| 20060235795 | Johnson et al. | Oct 2006 | A1 |
| 20060235796 | Johnson et al. | Oct 2006 | A1 |
| 20060242017 | Libes et al. | Oct 2006 | A1 |
| 20070084913 | Weston | Apr 2007 | A1 |
| 20070088610 | Chen | Apr 2007 | A1 |
| 20070118426 | Barnes, Jr. | May 2007 | A1 |
| 20070136140 | Smith, Jr. | Jun 2007 | A1 |
| 20070291710 | Fadell | Dec 2007 | A1 |
| 20080004949 | Flake et al. | Jan 2008 | A1 |
| 20080005104 | Flake et al. | Jan 2008 | A1 |
| 20080010121 | McIntosh | Jan 2008 | A1 |
| 20080027810 | Lerner et al. | Jan 2008 | A1 |
| 20080033637 | Kuhlman et al. | Feb 2008 | A1 |
| 20080040233 | Wildman et al. | Feb 2008 | A1 |
| 20080040274 | Uzo | Feb 2008 | A1 |
| 20080086767 | Kulkarni et al. | Apr 2008 | A1 |
| 20080140522 | Tutone | Jun 2008 | A1 |
| 20080154654 | Niessen et al. | Jun 2008 | A1 |
| 20080154765 | Wolfe | Jun 2008 | A1 |
| 20080154847 | Chellapilla et al. | Jun 2008 | A1 |
| 20080167991 | Carlson et al. | Jul 2008 | A1 |
| 20080183576 | Kim et al. | Jul 2008 | A1 |
| 20080183675 | Schwarz et al. | Jul 2008 | A1 |
| 20080201226 | Carlson et al. | Aug 2008 | A1 |
| 20080208739 | Phillips | Aug 2008 | A1 |
| 20080215475 | Ramer et al. | Sep 2008 | A1 |
| 20080221997 | Wolfe | Sep 2008 | A1 |
| 20080228600 | Treyz et al. | Sep 2008 | A1 |
| 20080262928 | Michaelis | Oct 2008 | A1 |
| 20080268868 | Maitland | Oct 2008 | A1 |
| 20080275768 | Berman et al. | Nov 2008 | A1 |
| 20080281677 | Toms et al. | Nov 2008 | A1 |
| 20080281702 | Kirkwood | Nov 2008 | A1 |
| 20080318559 | Porco | Dec 2008 | A1 |
| 20090005973 | Salo et al. | Jan 2009 | A1 |
| 20090006203 | Fordyce, III et al. | Jan 2009 | A1 |
| 20090024477 | Kramer et al. | Jan 2009 | A1 |
| 20090024700 | Garg et al. | Jan 2009 | A1 |
| 20090030779 | Tollinger et al. | Jan 2009 | A1 |
| 20090061884 | Rajan et al. | Mar 2009 | A1 |
| 20090076896 | DeWitt et al. | Mar 2009 | A1 |
| 20090076925 | DeWitt et al. | Mar 2009 | A1 |
| 20090125380 | Otto et al. | May 2009 | A1 |
| 20090125396 | Otto et al. | May 2009 | A1 |
| 20090132417 | Scipioni et al. | May 2009 | A1 |
| 20090138302 | Breznik et al. | May 2009 | A1 |
| 20090143966 | Jacobson et al. | Jun 2009 | A1 |
| 20090150218 | Brunner et al. | Jun 2009 | A1 |
| 20090152343 | Carter et al. | Jun 2009 | A1 |
| 20090157547 | Ruckart | Jun 2009 | A1 |
| 20090187463 | DaCosta | Jul 2009 | A1 |
| 20090187466 | Carter et al. | Jul 2009 | A1 |
| 20090187488 | Shamilian | Jul 2009 | A1 |
| 20090187492 | Hammad et al. | Jul 2009 | A1 |
| 20090198607 | Badger et al. | Aug 2009 | A1 |
| 20090199107 | Lewis et al. | Aug 2009 | A1 |
| 20090216646 | Seven et al. | Aug 2009 | A1 |
| 20090222346 | Greene et al. | Sep 2009 | A1 |
| 20090228325 | Simmons et al. | Sep 2009 | A1 |
| 20090240582 | Sheldon-Neal et al. | Sep 2009 | A1 |
| 20090240622 | Zandonadi | Sep 2009 | A1 |
| 20090249497 | Fitzgerald et al. | Oct 2009 | A1 |
| 20090253408 | Fitzgerald et al. | Oct 2009 | A1 |
| 20090254930 | Lo et al. | Oct 2009 | A1 |
| 20090271275 | Regmi et al. | Oct 2009 | A1 |
| 20090281945 | Shakkarwar | Nov 2009 | A1 |
| 20090287558 | Seth et al. | Nov 2009 | A1 |
| 20090292642 | Han | Nov 2009 | A1 |
| 20090299857 | Brubaker | Dec 2009 | A1 |
| 20090313129 | Rothschild | Dec 2009 | A1 |
| 20090327135 | Nguyen et al. | Dec 2009 | A1 |
| 20090327151 | Carlson et al. | Dec 2009 | A1 |
| 20100004997 | Mehta et al. | Jan 2010 | A1 |
| 20100006641 | Boutcher et al. | Jan 2010 | A1 |
| 20100006642 | Boutcher et al. | Jan 2010 | A1 |
| 20100030592 | Evans et al. | Feb 2010 | A1 |
| 20100030646 | Riise et al. | Feb 2010 | A1 |
| 20100030651 | Matotek et al. | Feb 2010 | A1 |
| 20100032339 | Hasegawa et al. | Feb 2010 | A1 |
| 20100041419 | Svendsen et al. | Feb 2010 | A1 |
| 20100042421 | Bai et al. | Feb 2010 | A1 |
| 20100049615 | Rose | Feb 2010 | A1 |
| 20100057530 | Parivash et al. | Mar 2010 | A1 |
| 20100063891 | Townsend et al. | Mar 2010 | A1 |
| 20100070334 | Monteverde | Mar 2010 | A1 |
| 20100070365 | Siotia et al. | Mar 2010 | A1 |
| 20100076829 | Bishop | Mar 2010 | A1 |
| 20100076849 | Bishop | Mar 2010 | A1 |
| 20100077036 | DeLuca et al. | Mar 2010 | A1 |
| 20100082420 | Trifiletti et al. | Apr 2010 | A1 |
| 20100082445 | Hodge et al. | Apr 2010 | A1 |
| 20100088188 | Kumar et al. | Apr 2010 | A1 |
| 20100100454 | Sines et al. | Apr 2010 | A1 |
| 20100106611 | Paulsen et al. | Apr 2010 | A1 |
| 20100114775 | Griffin | May 2010 | A1 |
| 20100121717 | Chen | May 2010 | A1 |
| 20100138294 | Bussmann et al. | Jun 2010 | A1 |
| 20100138344 | Wong et al. | Jun 2010 | A1 |
| 20100145723 | Hudson et al. | Jun 2010 | A1 |
| 20100145778 | Fordyce, III et al. | Jun 2010 | A1 |
| 20100146607 | Piepenbrink et al. | Jun 2010 | A1 |
| 20100156933 | Jones et al. | Jun 2010 | A1 |
| 20100169179 | Ramer et al. | Jul 2010 | A1 |
| 20100185504 | Rajan et al. | Jul 2010 | A1 |
| 20100190510 | Maranhas et al. | Jul 2010 | A1 |
| 20100191551 | Drance et al. | Jul 2010 | A1 |
| 20100191578 | Tran et al. | Jul 2010 | A1 |
| 20100192230 | Steeves et al. | Jul 2010 | A1 |
| 20100205167 | Tunstall-Pedoe et al. | Aug 2010 | A1 |
| 20100217525 | King et al. | Aug 2010 | A1 |
| 20100223184 | Perlman | Sep 2010 | A1 |
| 20100241495 | Maniyar et al. | Sep 2010 | A1 |
| 20100241496 | Gupta et al. | Sep 2010 | A1 |
| 20100250368 | Porco | Sep 2010 | A1 |
| 20100257054 | Martin et al. | Oct 2010 | A1 |
| 20100260388 | Garrett et al. | Oct 2010 | A1 |
| 20100262449 | Monteforte et al. | Oct 2010 | A1 |
| 20100274655 | Postrel | Oct 2010 | A1 |
| 20100293065 | Brody et al. | Nov 2010 | A1 |
| 20100306099 | Hirson et al. | Dec 2010 | A1 |
| 20100312630 | Krutchik et al. | Dec 2010 | A1 |
| 20100312645 | Niejadlik et al. | Dec 2010 | A1 |
| 20100312646 | Gupta et al. | Dec 2010 | A1 |
| 20100323716 | Jaffri | Dec 2010 | A1 |
| 20100324977 | Dragt | Dec 2010 | A1 |
| 20100332339 | Patel et al. | Dec 2010 | A1 |
| 20110010238 | Postrel | Jan 2011 | A1 |
| 20110015987 | Chakraborty et al. | Jan 2011 | A1 |
| 20110022424 | VonDerheide | Jan 2011 | A1 |
| 20110022483 | Hammad | Jan 2011 | A1 |
| 20110022517 | Hammad | Jan 2011 | A1 |
| 20110029403 | Xu | Feb 2011 | A1 |
| 20110053559 | Klein | Mar 2011 | A1 |
| 20110055005 | Lang | Mar 2011 | A1 |
| 20110057027 | Grossman et al. | Mar 2011 | A1 |
| 20110060640 | Thompson et al. | Mar 2011 | A1 |
| 20110065419 | Book et al. | Mar 2011 | A1 |
| 20110082735 | Kannan et al. | Apr 2011 | A1 |
| 20110087430 | Boss et al. | Apr 2011 | A1 |
| 20110093318 | Guday et al. | Apr 2011 | A1 |
| 20110106613 | Felt et al. | May 2011 | A1 |
| 20110112892 | Tarantino | May 2011 | A1 |
| 20110131627 | Abendroth et al. | Jun 2011 | A1 |
| 20110137804 | Peterson | Jun 2011 | A1 |
| 20110140841 | Bona et al. | Jun 2011 | A1 |
| 20110184793 | Bohannon et al. | Jul 2011 | A1 |
| 20110189981 | Faith et al. | Aug 2011 | A1 |
| 20110191152 | Schwartz | Aug 2011 | A1 |
| 20110191161 | Dai | Aug 2011 | A1 |
| 20110191237 | Faith et al. | Aug 2011 | A1 |
| 20110202416 | Buer et al. | Aug 2011 | A1 |
| 20110238476 | Carr et al. | Sep 2011 | A1 |
| 20110238514 | Ramalingam et al. | Sep 2011 | A1 |
| 20110238517 | Ramalingam et al. | Sep 2011 | A1 |
| 20110270618 | Banerjee et al. | Nov 2011 | A1 |
| 20110289004 | Prakash et al. | Nov 2011 | A1 |
| 20110302016 | Haddad | Dec 2011 | A1 |
| 20120010931 | Mehra et al. | Jan 2012 | A1 |
| 20120010938 | Standley et al. | Jan 2012 | A1 |
| 20120185317 | Wong | Jul 2012 | A1 |
| 20120259722 | Mikurak | Oct 2012 | A1 |
| 20120323703 | Hillier | Dec 2012 | A1 |
| 20140300540 | Beadle et al. | Oct 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 101689268 | Mar 2010 | CN |
| 101919274 | Dec 2010 | CN |
| 2000134147 | May 2000 | JP |
| 2001222593 | Aug 2001 | JP |
| 2001357337 | Dec 2001 | JP |
| 2002099971 | Apr 2002 | JP |
| 2002175354 | Jun 2002 | JP |
| 2002288502 | Oct 2002 | JP |
| 2003022481 | Jan 2003 | JP |
| 2003090730 | Mar 2003 | JP |
| 2004264986 | Sep 2004 | JP |
| 2004341684 | Dec 2004 | JP |
| 2006164189 | Jun 2006 | JP |
| 2007208444 | Aug 2007 | JP |
| 2007522564 | Aug 2007 | JP |
| 2008022395 | Jan 2008 | JP |
| 2008199221 | Aug 2008 | JP |
| 2009020036 | Jan 2009 | JP |
| 2009205684 | Sep 2009 | JP |
| 2009224868 | Oct 2009 | JP |
| 2009538093 | Oct 2009 | JP |
| 2009282618 | Dec 2009 | JP |
| 2009283989 | Dec 2009 | JP |
| 2011188256 | Sep 2011 | JP |
| 2012510681 | May 2012 | JP |
| 2012529085 | Nov 2012 | JP |
| 1020070105106 | Oct 2007 | KR |
| 20090080000 | Jul 2009 | KR |
| 20090104068 | Oct 2009 | KR |
| WO 2008067543 | Jun 2008 | WO |
| 2010015995 | Feb 2010 | WO |
| WO2010065235 | Jun 2010 | WO |
| WO2010138891 | Dec 2010 | WO |
| Entry |
|---|
| U.S. Appl. No. 12/976,533, filed Dec. 22, 2010, Harsha Ramalingam, “Mobile Payments Using Point-of-sale Infrastructure”. |
| U.S. Appl. No. 13/027,913, filed Feb. 15, 2011, Harsha Ramalingam, et al., “User Profile and Geolocation for Efficient Transactions”. |
| Dictionary.com, “Broadcast”, retrived at <<http://dictionary.reference.com/browse/broadcast>> on Feb. 6, 2012, 4 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/820,705, dated Feb. 27,2012, Harsha Ramalingam et al., “Transaction Completion Based on Geolocation Arrival”, 15 pages. |
| Non-Final Office Aciotn for U.S. Appl. No. 12/820,743, dated Feb. 27, 2012, Harsha Ramalingam et al, “Hierarchical Device Relationships for Geolocation-Based Transactions”, 18 pages. |
| WebWire, “BooksOnBoard Adds Google Checkout, Offers Discount on Google Checkout Purchases”, Jun. 11, 2008, retrived from Google News Apr. 6, 2012, pp. 1-pp. 2. |
| “MGM Grand, MacroView Labs—Mobile App Developers for iPhone, Android, Blackberries”, retrieved on Jan. 13, 2011 at <<http://www.macroviewlabs.com/mgmgrand>>, 5 pages. |
| PCT Search Report dated May 12, 2011 for PCT Application No. PCT/US11/28825. |
| Collins, “Smartphones to be used as Hotel Room Keys”, Telegraph Media Group Limited, May 25, 2010, Retrieved on Jun. 2, 2010 at <<http://www.telegraph.co.uk/travel/hotels/7762522/Smartphones-to-be-used-as-hotel-room-keys.html>> pp. 1-2. |
| Deleon, “Holiday Inn to Trial Mobile-as-room-key Program Next Month”, TechCrunch, May 25, 2010, Retrieved on Jun. 2, 2010 at <<http://www.mobilecrunch.com/2010/05/25/holiday-inn-to-trial-mobile-as-room-key-program-next-month/>> 1 pg. |
| “Placecast Raises $3 Million for Location-Based Mobile Marketing Technology”, The Good NET Guide, Retrieved on Mar. 25, 2010 at <<http://thegoodnetguide.com/03/placecast-raises-3-million-for-location-based-mobile-marketing-technology/>>, 1 pg. |
| Starbucks Card Mobile App, “Using Your Starbucks Card is Now Even Faster and Easier With the Starbucks Card Mobile App”, Retrieved on Apr. 22, 2010 at <<http://www.starbucks.com/coffeehouse/mobile-apps/starbucks-card-mobile>>, pp. 1-2. |
| U.S. Appl. No. 61/14210, Garrett. |
| Office action for U.S. Appl. No. 12/820,949, dated Nov. 9, 2012, Ramalingam et al, “Transaction Tracking and Incentives”, 11 pages. |
| Final Office Aciotn for U.S. Appl. No. 12/820,743, dated Jun. 21, 2012, Harsha Ramalingam et al, “Hierarchical Device Relationships for Geolocation-Based Transactions”, 24 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/371,038, dated Jul. 23, 2012, Harsha Ramalingam et al., 8 pages. |
| Final Office Action for U.S. Appl. No. 12/820,705, dated Jul. 25, 2012, Harsha Ramalingam et al., “Transaction Completion Based on Geolocation Arrival”, 16 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/820,854, dated Jul. 27, 2012, Harsha Ramalingam et al., “Location-Based Marketing to Mobile Devices”, 16 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/468,714, dated Aug. 16, 2012, Harsha Ramalingam, “Mobile Payments Using Point-of-sale Infrastructure”, 29 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/976,533, dated Aug. 16, 2012, Harsha Ramalingam, “Mobile Payments Using Point-of-sale Infrastructure”, 38 pages. |
| Final Office Action for U.S. Appl. No. 12/820,854, dated Oct. 22, 2013, Harsha Ramalingam, “Location-Based Marketing to Mobile Devices”, 21 pages. |
| Office Action for U.S. Appl. No. 12/820,854, dated Apr. 10, 2013, Ramalingam et al., “Location-Based Marketing to Mobile Devices”, 22 pages. |
| Office Action for U.S. Appl. No. 13/468,714, dated Apr. 11, 2013, Ramalingam, “Mobile Payments Using Point-of sale Infrastructure”, 35 pages. |
| Office Action for U.S. Appl. No. 12/976,533, dated Apr. 12, 2013, Ramalingam, “Mobile Payments Using Point-of-sale Infrastructure”, 44 pages. |
| Office action for U.S. Appl. No. 12/820,949, dated Jun. 20, 2013, Ramalingam et al, “Transaction Tracking and Incentives”, 20 pages. |
| Office action for U.S. Appl. No. 12/894,323, dated Jun. 24, 2013, Carr et al., “Converged Web-identity and Mobile Device Based Shopping”, 12 pages. |
| U.S. Appl. No. 12/820,816, filed Jun. 22, 2010, Harsha Ramalingam, “Mobile Device Security”. |
| Office action for U.S. Appl. No. 12/820,705, dated Jul. 12, 2013, Ramalingam et al, “Transaction Completion Based on Geolocation Arrival”, 16 pages. |
| Office action for U.S. Appl. No. 12/894,287, dated Jul. 16, 2013, Carr et al., “Location-based Coupons and Mobile Devices”, 18 pages. |
| U.S. Appl. No. 13/371,038, filed Feb. 10, 2012, Harsha Ramalingam et al., “User Profile and Geolocation for Efficient Transactions”. |
| Office action for U.S. Appl. No. 12/894,323, dated Dec. 12, 2012, Carr et al., “Converged Web-identity and Mobile Device Based Shopping”, 9 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/820,816, dated Dec. 31, 2012, Harsha Ramalingham et al., “Mobile Device Security”, 10 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/894,287, dated Dec. 5, 2012, Michael Carr et al., “Location-based Coupons and Mobile Devices”, 8 pages. |
| Final Office Action for U.S. Appl. No. 12/820,705, dated Dec. 5, 2013, Harsha Ramalingam, “Transaction Completion Based on Geolocation Arrival”, 14 pages. |
| Office action for U.S. Appl. No. 12/820,743, dated Dec. 27, 2013, Ramalingam et al., “Hierarchical Device Relationships for Geolocation-Based Transactions”, 26 pages. |
| U.S. Appl. No. 13/052,930, filed Mar. 21, 2011, Hart et al., “Advertisement Service”. |
| Final Office Action for U.S. Appl. No. 12/820,949, dated Jan. 6, 2014, Harsha Ramalingam, “Transaction and Tracking Incentives”, 22 pages. |
| Translated Japanese Office Action dated Dec. 10, 2013 for Japanese patent application No. 2013-500205, a counterpart foreign application of U.S. Pat. No. 8,140,403, 9 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/052,930, dated Jan. 2, 2013, Gregory M. Hart et al., “Advertisement Service”, 23 pages. |
| Office Action for U.S. Appl. No. 13/111,920, dated Oct. 2, 2013, Andrew J. Doane, “Location-Based Mobile Advertising”, 28 pages. |
| Office Action for U.S. Appl. No. 13/052,930, dated Dec. 16, 2013, Gregory M. Hart, “Advertisement Service”, 28 pages. |
| Office action for U.S. Appl. No. 13/052,930, dated Jul. 8, 2013, Hart et al., “Advertisement Service”, 20 pages. |
| PCT Search Report and Written Opinion for PCT application No. PCT/US12/29798, dated Jul. 5, 2012 , 7 pages. |
| Definition: Purchase, retrieved on Mar. 31, 2014 at <<dictionary.reference.com/browse/purchase?s=t>>, World English Dictionary 2009, 2 pages. |
| Extended European Search Report dated Feb. 26, 2014 for European patent application No. 11759940.7, 11 pages. |
| Office Action from U.S. Appl. No. 12/894,287, dated Mar. 27, 2014, Michael Carr, “Location-based Coupons and Mobile Devices”, 17 pages. |
| Final Office Action for U.S. Appl. No. 12/820,743, dated Apr. 10, 2014, Harsha Ramalingam, “Hierarchical Device Relationships for Geolocation-Based Transactions”, 24 pages. |
| Office Action for U.S. Appl. No. 12/820,705, dated Apr. 2, 2014, Harsha Ramalingam, “Transaction Completion Based on Geolocation Arrival”, 11 pages. |
| Office Action for U.S. Appl. No. 12/820,854, dated May 9, 2014, Harsha Ramalingam, “Location-Based Marketing to Mobile Devices”, 25 pages. |
| Office action for U.S. Appl. No. 13/111,920, dated Jun. 20, 2014, Doane et al., “Location-Based Mobile Advertising”, 31 pages. |
| Office action for U.S. Appl. No. 13/052,930, dated Jul. 1, 2014, Hart et al., “Advertisement Service”, 29 pages. |
| Canadian Office Action dated Aug. 29, 2014 for Canadian patent application No. 2794085, a foreign application of U.S. Appl. No. 12/820,672, 3 pages. |
| Extended European Search Report dated Oct. 31, 2014 for European Patent Application No. 12760316.5, 7 pages. |
| Translated Japanese Office Action dated Jul. 1, 2014 for Japanese patent application No. 2014-094659, a counterpart foreign application of U.S. Pat. No. 8,140,403, 4 pages. |
| Translated Japanese Office Action dated Jul. 29, 2014 for Japanese patent application No. 2013-553675, a counterpart foreign application of U.S. Appl. No. 13/052,930, 9 pages. |
| Translated Korean Office Action dated Oct. 17, 2014 for Korean patent application No. 10-2012-7024786, a counterpart foreign application of U.S. Appl. No. 12/820,672, 11 pages. |
| Office Action for U.S. Appl. No. 12/820,854, dated Nov. 5, 2014, Harsha Ramalingam, “Location-Based Marketing to Mobile Devices”, 23 pages. |
| Office Action for U.S. Appl. No. 12/894,287, dated Dec. 4, 2014, Michael Carr, “Location-based Coupons and Mobile Devices”, 24 pages. |
| Office action for U.S. Appl. No. 12/894,323, dated Sep. 11, 2014, Carr et al, “Converged Web-identity and Mobile Device Based Shopping”, 14 pages. |
| Office action for U.S. Appl. No. 12/820,705, dated Sep. 2, 2014, Ramalingam et al., “Transaction Completion Based on Geolocation Arrival”, 12 pages. |
| Office action for U.S. Appl. No. 12/820,743, dated Jul. 29, 2015, Ramalingam et al., “Hierarchical Device Relationships for Geolocation-Based Transactions”, 9 pages. |
| U.S. Appl. No. 12/820,672 , “Non-Final Office Action”, dated Mar. 24, 2011, 24 pages. |
| U.S. Appl. No. 12/820,672 , “Notice of Allowance”, dated Nov. 7, 2011, 10 pages. |
| U.S. Appl. No. 12/820,672 , “Restriction Requirement”, dated Jan. 27, 2011, 9 pages. |
| U.S. Appl. No. 12/820,705 , “Final Office Action”, dated Aug. 19, 2015, 15 pages. |
| U.S. Appl. No. 12/820,705 , “Final Office Action”, dated Jun. 17, 2016, 15 pages. |
| U.S. Appl. No. 12/820,705 , “Restriction Requirement”, dated Feb. 11, 2015, 7 pages. |
| U.S. Appl. No. 12/820,705 , “Restriction Requirement”, dated Nov. 22, 2011, 8 pages. |
| U.S. Appl. No. 12/820,743 , “Advisory Action”, dated Oct. 7, 2015. |
| U.S. Appl. No. 12/820,743 , “Final Office Action”, dated Jun. 29, 2016. |
| U.S. Appl. No. 12/820,743 , “Restriction Requirement”, dated Jan. 7, 2015. |
| U.S. Appl. No. 12/820,743 , “Restriction Requirement”, dated Nov. 18, 2011. |
| U.S. Appl. No. 12/820,854 , “Non-Final Office Action”, dated May 24, 2016, 19 pages. |
| U.S. Appl. No. 12/820,949 , “Advisory Action”, dated Apr. 16, 2014. |
| U.S. Appl. No. 12/820,949 , “Restriction Requirement”, dated Jul. 31, 2012. |
| U.S. Appl. No. 12/820,949 , filed Jun. 22, 2010, Titled: Transaction Tracking and Incentives. |
| U.S. Appl. No. 12/894,287 , “Advisory Action”, dated Dec. 19, 2013, 3 pages. |
| U.S. Appl. No. 12/894,287 , “Non-Final Office Action”, dated Sep. 3, 2015, 24 pages. |
| U.S. Appl. No. 12/894,287 , “Restriction Requirement”, dated Sep. 25, 2012, 7 pages. |
| U.S. Appl. No. 12/894,323 , “Notice of Allowance”, dated Feb. 2, 2015, 14 pages. |
| U.S. Appl. No. 12/894,323 , “Restriction Requirement”, dated Sep. 25, 2012, 7 pages. |
| U.S. Appl. No. 12/976,533 , “Final Office Action”, dated Jun. 3, 2016, 51 pages. |
| U.S. Appl. No. 12/976,533 , “Non-Final Office Action”, dated Sep. 23, 2015, 39 pages. |
| U.S. Appl. No. 13/027,913 , “Non-Final Office Action”, dated Mar. 29, 2011, 25 pages. |
| U.S. Appl. No. 13/027,913 , “Notice of Allowance”, dated Nov. 7, 2011, 21 pages. |
| U.S. Appl. No. 13/371,038 , “Notice of Allowance”, dated Oct. 11, 2012, 9 pages. |
| U.S. Appl. No. 13/371,038 , “Restriction Requirement”, dated Apr. 6, 2012, 7 pages. |
| U.S. Appl. No. 13/468,714 , “Non-Final Office Action”, dated Aug. 31, 2015, 36 pages. |
| U.S. Appl. No. 13/725,466 , “Non-Final Office Action”, dated Oct. 5, 2015, 20 pages. |
| U.S. Appl. No. 13/973,870 , “Corrected Notice of Allowability”, dated May 20, 2015, 7 pages. |
| U.S. Appl. No. 13/973,870 , “Notice of Allowance”, dated Apr. 3, 2015, 11 pages. |
| U.S. Appl. No. 14/726,380 , “Restriction Requirement”, dated Dec. 9, 2015, 7 pages. |
| U.S. Appl. No. 14/821,337 , “Corrected Notice of Allowability”, dated Apr. 11, 2016. |
| U.S. Appl. No. 14/821,337 , “Corrected Notice of Allowability”, dated Mar. 22, 2016. |
| U.S. Appl. No. 14/821,337 , “Corrected Notice of Allowability”, dated May 2, 2016. |
| CA2,794,085 , “Office Action”, dated Aug. 27, 2015, 4 pages. |
| CN201180015579.3 , “Office Action”, dated Oct. 16, 2015, 13 pages. |
| CN201280008527.8 , “Office Action”, dated Dec. 24, 2015, 16 pages. |
| JP2015-047434 , “Notice of Allowance”, dated Dec. 15, 2015, 6 pages. |
| KR10-2014-7035474 , “Office Action”, dated Oct. 29, 2015, 3 pages. |
| U.S. Appl. No. 12/820,705 , “Non-Final Office Action”, dated Feb. 9, 2016, 13 pages. |
| U.S. Appl. No. 12/820,743 , “Non-Final Office Action”, dated Feb. 1, 2016, 9 pages. |
| U.S. Appl. No. 12/894,287 , “Final Office Action”, dated Feb. 22, 2016, 29 pages. |
| U.S. Appl. No. 13/052,930 , “Final Office Action”, dated Feb. 2, 2016, 35 pages. |
| U.S. Appl. No. 13/111,920 , “Final Office Action”, dated Feb. 12, 2016, 34 pages. |
| U.S. Appl. No. 13/468,714 , “Final Office Action”, dated Feb. 25, 2016, 12 pages. |
| U.S. Appl. No. 13/725,466 , “Final Office Action”, dated Mar. 16, 2016, 28 pages. |
| U.S. Appl. No. 14/821,337 , “Notice of Allowance”, dated Mar. 11, 2016, 9 pages. |
| KR10-2015-7033998 , “Office Action”, dated Jan. 6, 2016, 6 pages. |
| CA2,830,268 , “Office Action”, dated Mar. 30, 2016, 5 pages. |
| U.S. Appl. No. 14/726,380, “Final Office Action,” dated Apr. 15, 2016, 36 pages. |
| U.S. Appl. No. 12/820,743 , “Notice of Allowance”, dated Apr. 12, 2017, 9 pages. |
| U.S. Appl. No. 12/820,949 , “Notice of Allowance”, dated May 23, 2017, 22 pages. |
| U.S. Appl. No. 13/111,920 , “Final Office Action”, dated Apr. 14, 2017, 36 pages. |
| U.S. Appl. No. 13/725,466 , “Non-Final Office Action”, dated Mar. 20, 2017, 29 pages. |
| KR10-2017-7002603 , “Office Action”, dated Mar. 7, 2017, 6 pages. |
| U.S. Appl. No. 12/820,705 , “Advisory Action”, dated Sep. 27, 2016, 3 pages. |
| U.S. Appl. No. 12/820,854 , “Final Office Action”, dated Aug. 31, 2016, 21 pages. |
| U.S. Appl. No. 12/894,287 , “Non-Final Office Action”, dated Jul. 29, 2016, 38 pages. |
| U.S. Appl. No. 13/111,920 , “Non-Final Office Action”, dated Sep. 14, 2016, 34 pages. |
| U.S. Appl. No. 14/726,380 , “Non-Final Office Action”, dated Aug. 9, 2016, 43 pages. |
| CA2,794,085 , “Office Action”, dated Sep. 15, 2016, 3 pages. |
| CN201180015579.3, “Decision to Grant”, dated Sep. 1, 2016, 2 pages. |
| CN201280008527.8 , “Office Action”, dated Aug. 4, 2016, 15 pages. |
| EP11759940.7 , “Office Action”, dated Aug. 17, 2016, 6 pages. |
| EP12760316.5 , “Office Action”, dated Aug. 9, 2016, 6 pages. |
| KR10-2015-07033998 , “Office Action”, dated Jul. 26, 2016, 7 pages. |
| Canadian Office Action dated Apr. 7, 2015 for Canadian patent application No. , a counterpart foreign application of U.S. Appl. No. 13/052,930, 5 pages. |
| Translated Chinese Office Action dated Mar. 10, 2015 for Chinese patent application No. 201180015579.3, a counterpart foreign application of U.S. Appl. No. 12/820,672, 23 pages. |
| Translated Japanese Office Action dated Mar. 31, 2015 for Japanese patent application No. 2015-047434, a counterpart foreign application of U.S. Appl. No. 12/820,672, 9 pages. |
| Translated Korean Office Action dated Jan. 28, 2015 for Korean patent application No. 10-2014-7035474, a counterpart foreign application of U.S. Appl. No. 12/820,672, 11 pages. |
| Translated Korean Office Action dated Apr. 24, 2015 for Korean patent application No. 10-2012-7024786,5 a counterpart foreign application of U.S. Appl. No. 12/820,672, 9 pages. |
| Office Action for U.S. Appl. No. 12/820,705, dated Apr. 17, 2015, Harsha Ramalingam, “Transaction Completion Based on Geolocation Arrival”, 23 pages. |
| Office action for U.S. Appl. No. 12/820,743, dated Apr. 3, 2015, Ramalingam et al., “Hierarchical Device Relationships for Geolocation-Based Transactions”, 21 pages. |
| Final Office Action for U.S. Appl. No. 12/894,287, dated Apr. 9, 2015, Michael Carr, “Location-based Coupons and Mobile Devices”, 24 pages. |
| Final Office Action for U.S. Appl. No. 12/820,854, dated Jun. 3, 2015, Harsha Ramalingam, “Location-Based Marketing to Mobile Devices”, 11 pages. |
| Office Action for U.S. Appl. No. 13/052,930, dated Jul. 10, 2015, Gregory M. Hart, “Advertisement Service”, 30 pages. |
| Office Action for U.S. Appl. No. 13/111,920, dated Jul. 10, 2015, Andrew J. Doane, “Location-Based Mobile Advertising”, 29 pages. |
| Office action for U.S. Appl. No. 14/726,380, dated Jul. 22, 2015, Carr et al., “Converged Web-Identity and Mobile Device Based Shopping”, 12 pages. |
| U.S. Appl. No. 13/052,930 , “Final Office Action”, dated Jul. 18, 2017, 39 pages. |
| U.S. Appl. No. 13/725,466 , “Final Office Action”, dated Aug. 4, 2017, 22 pages. |
| CA2,794,085 , “Office Action”, dated Aug. 14, 2017, 3 pages. |
| CA2,830,268 , “Office Action”, dated Sep. 20, 2017, 7 pages. |
| CN201280008527.8 , “Office Action”, dated Aug. 22, 2017, 9 pages. |
| EP17158535.9 , “Extended European Search Report”, dated Jul. 11, 2017, 7 pages. |
| U.S. Appl. No. 12/820,705 , “Notice of Allowance”, dated Dec. 16, 2016, 7 pages. |
| U.S. Appl. No. 12/894,287 , “Final Office Action”, dated Feb. 3, 2017, 24 pages. |
| U.S. Appl. No. 13/468,714 , “Notice of Allowance”, dated Feb. 28, 2017, 9 pages. |
| U.S. Appl. No. 14/726,380 , “Final Office Action”, dated Feb. 2, 2017, 47 pages. |
| CA2,830,268 , “Office Action”, dated Feb. 1, 2017, 14 pages. |
| CA2,921,085 , “Office Action”, dated Feb. 9, 2017, 3 pages. |
| CN201280008527.8 , “Office Action”, dated Jan. 24, 2017, 16 pages. |
| Alqerem et al., “Location Dependent Transaction for Mobile Environment”, International Conference on Information and Communication Technologies: From Theory to Applications, Piscataway, NJ, 2006, 2 pages. |
| Prabhu, “Transaction Processing in Mobile Database System”, University of Missouri—Kansas City, 2006. vol. 67/12-B of Dissertation Abstracts International, 1 page. |
| Number | Date | Country | |
|---|---|---|---|
| 61316527 | Mar 2010 | US | |
| 61351743 | Jun 2010 | US |
