US 9,058,604 B2Grant
Converged web-identity and mobile device based shopping
Issue Date:2015-06-16
•17 Claims
•12 Drawing Sheets
Abstract
Techniques for providing information to a user of a mobile device based on an online or web-identity of the user and a geolocation of the mobile device are described herein. The user may be notified when a nearby merchant has a good or service for sale that matches a good or service in a list, such as a wish list, associated with the web-identity of the user. The users may also be provided access to a coupon within an electronic document when a mobile device storing the electronic document is located at a particular merchant. This convergence of geographical location of the user, as determined by the geolocation of his or her mobile device, with his or her web-identity can bring the online and off-line worlds closer together to provide relevant information for the user and improved marketing opportunities for merchants.
Metadata
Assignee
- Amazon Technologies, Inc.
Inventors
- Michael Carr
- Bhavnish H. Lathia
- James Hsiaosung Chuang
Application Information
Application Number:US 12/894,323
Filing Date:2010-09-30
Priority Date:2010-03-23
Art Unit:3681
Classifications
IPC:
G06Q30/02G06Q30/00G06Q20/10G06Q20/20G06Q20/40G06Q30/06
Field of Search:
G06Q 20/387G06Q 30/0207G06Q 30/0259G06Q 30/0261G06Q 30/0205
Patent Drawings (12 sheets)
Description
Related Applications
[0001] This application is related 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.
Background
[0002] 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 desktop computers. Development of content that recognizes the limitations while taking full advantage of the unique aspects of mobile computing devices is an active and maturing field.
[0003] Although some merchants have both online or web-based stores as well as brick-and-mortar stores, the online and brick-and-mortar worlds are largely separate. However, mobile computing devices allow someone to be both “online” and at a brick-and-mortar merchant simultaneously. For some transactions such as purchasing goods or services, consumers may be primarily concerned about price, convenience, and quality rather than the online or off-line format of the transaction. Additionally, advertising and marketing opportunities that cover both the brick-and-mortar and the online worlds may present additional ways for merchants to reach potential consumers. Accordingly, the convergence of an online presence and a real-world location can facilitate transactions and enhance advertising to the benefit of both consumers and merchants.
Brief Description of the Drawings
[0004] 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.
[0005] FIG. 1 shows an illustrative architecture in which a user of a mobile device, a merchant located at a specific geolocation, and an online retailer may interact.
[0006] FIG. 2 shows the mobile device from FIG. 1 in greater detail.
[0007] FIG. 3 shows the server(s) from FIG. 1 in greater detail.
[0008] FIG. 4 shows the user information from FIG. 1 in greater detail.
[0009] FIG. 5 shows the merchant profiles from FIG. 1 in greater detail.
[0010] FIG. 6 shows an illustrative architecture for a user of a mobile device to selectively interact with merchants having certain goods and/or services for sale within a predetermined proximity of the mobile device.
[0011] FIGS. 7 a and 7b are a flow diagram of an illustrative process for notifying a user of a mobile device when a nearby merchant has a good or service for sale that is of interest to the user.
[0012] FIG. 8 is a flow diagram of an illustrative process for recommending a nearby merchant and an online good or service to a user of a mobile device.
[0013] FIG. 9 shows an illustrative timeline in which an electronic document on a mobile device contains a coupon that is activated when the mobile device is located at a merchant.
[0014] FIG. 10 is a flow diagram of an illustrative process for activating a coupon in an electronic document when a mobile device is located a merchant.
Detailed Description
[0015] Mobile devices that provide wireless connection to the Internet (or other network) allow access to what may be called the “mobile web.” The mobile web may be accessed from a coffee shop, a park, an airport, a shopping mall, or any other location where there is a sufficient wireless signal. With the mobile web, access to the Internet is no longer limited to offices, libraries, dorm rooms, and such places with a computer and an Internet connection. Many of the mobile devices that provide access to the mobile web are also equipped with a Global Positioning System (GPS) or other type of location sensing technology. Therefore, the Internet accessed by a mobile device could be thought of “existing” at the specific geographic location or “geolocation” of the mobile device. Thus, content from the Internet (or from another source such as a local storage device) presented to a user of a mobile device may differ depending on a geolocation of the mobile device.
[0016] This disclosure is directed to, in part, providing information to a user of a mobile device. For instance, if a good or service that the user may wish to purchase is for sale at a nearby merchant, that information may be provided to the user. One source of information about the user carrying the mobile device may be that user's web-identity which could contains such information as past purchases made from online retail websites, a wish list of items selected by the user, web pages the user has frequently or recently viewed, and the like. The web-identity may suggest what types of good and/or services the user desires and the geolocation of the mobile device may suggest convenient, nearby brick-and-mortar merchants. This combination of web-identity and physical location may also be used to suggest that the user purchase a good or service from a nearby merchant instead of an online retailer.
[0017] This disclosure is directed to, in further part, providing additional access to content based on geolocation. The content may be a promotion, such as a coupon, that provides the user with a financial incentive to go to (along with his or her mobile device) a particular geolocation. The geolocation may be a merchant that wishes to bring potential customers into the store by making, for example, a coupon available only inside the store. The coupon may be related to the goods and/or services sold by the merchant or related to goods and/or services sold by an online retailer. The content may also be provided after the user goes to multiple locations (e.g., several merchants) and logs in or checks in with a server or other computer at each of those locations.
[0018] A merchant may include any human or legal person that is a seller of goods or services at a specific geolocation that engages in transactions with customers. An online retailer may also include any human or legal person that is a seller of goods or services, but an online retailer engages in remote transactions with customers over an electronic communications network (for example, but not limited to, website-based retailers). A single company may have both a web presence and brick-and-mortar stores so that aspects of the same company can be classified as an online retailer and as a merchant.
[0019] The described techniques 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
[0020] FIG. 1 shows an illustrative architecture 100 in which a representative user 102 employs a mobile device 104 to interact with a merchant 106. The merchant 106 may comprise a merchant server 108 and a point-of-sale device 110 (e.g., a “cash register”). In some implementations, there may be one merchant server 108 for several point-of-sale devices 110. The merchant server 108 may also include merchant applications that manage interactions between the merchant 106 and the mobile device 104. The merchant applications may include applications that regulate point-of-sale transactions, online transactions, the provisioning of promotions, coupons, information, and the like. The merchant server 108 may also store customer information about past or potential future customers. In some implementations, the customer information may comprise information such as personal information about the customer, customer preferences, and the like.
[0021] 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 computer) 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., Wi-Fi hotspot) or from a locator signal broadcast from a known location, such as at the merchant 106.
[0022] 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 Wi-Fi 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.
[0023] 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. The server(s) 118 may house or otherwise have a connection to multiple data stores including user information 120, merchant profiles 122, and/or other data stores. Generally, the user information 120 contains information about the user 102 associated with the mobile device 104. The user information 120 enables efficient and personalized interaction between the user 102 and the merchant 106. The merchant profiles 122 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 purchasing a good and/or service from the merchant 106 when the user 102 is at the merchant location. Information about which goods and/or services the user is be interested in purchasing may be contained in the user information 120. Both of the data stores will be discussed in greater detail below.
[0024] The server(s) 118 may also comprise an authentication module 124 that compares login information from the mobile device 104 and/or the merchant 106 to confirm that the correct user information 120, merchant profiles 122, and other information is correlated with the correct entity (e.g., user 102 and/or point-of-sale device 110). The authentication module 124 will be discussed in greater detail below.
[0025] One or more online retailers 126 may also be connected to the network 116. The online retailer(s) 126 may offer goods and/or services for sale over the network 116 without having a brick-and-mortar merchant location. Each of the mobile device 104, the merchant 106, the server(s) 118 and the online retailer(s) 126 may communicate with one another over the network 116. One company or store may have both an online retailer 126 and one or more merchants 106 located at multiple geolocations.
Illustrative Mobile Device
[0026] FIG. 2 is a schematic representation of the mobile device 104 of FIG. 1 . The mobile device 104 includes one or more processors 202 and a memory 204. The memory may contain a user identification module 206 that may in turn contain a user identifier 208 and/or user information 210. The user identifier 208 may be a unique number or code that uniquely identifies the user 102 of the mobile device 104. This user identifier 208 may be the same user identifier 208 that the user 102 uses for interacting with online retailers 126 and the like. In some implementations, the user identifier 208 may be entered by the user 102 into the mobile device 104 during a setup procedure such as by entering a user name and a password. In other implementations, the user identifier 208 may be included in hardware of the mobile device 104. For example, a unique serial number of the mobile device 104 may be linked with a user name and password when the user 102 purchases the device 104. As a further example, a subscriber identification module (SIM) on a removable SIM card within the device 104 may contain the user identifier 208. In this example, the user identifier 208 may be transferred between devices by moving the SIM card.
[0027] 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 wish list of goods and/or services, past transaction histories, and/or any other information related to the user 102. Information stored in the user identification module 206 may be similar to information in the user information data store 120 shown in FIG. 1 .
[0028] The memory 204 may also contain an electronic document 212. The electronic document may be any type of electronic document accessed by a computing device such as a word processing document, a spreadsheet document, an email, a web page, an eBook, and the like. In some implementations discussed below, the electronic document 212 may include a coupon. The coupon may be associated with one or more merchants.
[0029] The terms “book” and/or “eBook,” as used herein, include electronic or digital representations of printed works, as well as digital content that may include text, multimedia, hypertext, and/or hypermedia. Examples of printed and/or digital works include, but are not limited to, books, magazines, newspapers, periodicals, journals, reference materials, telephone books, textbooks, anthologies, instruction manuals, proceedings of meetings, forms, directories, maps, web pages etc. Accordingly, the terms book and/or eBook may include any content that is in electronic or digital format.
[0030] In some implementations, the mobile device 104 may facilitate transactions either online or with a merchant 106 while the user 102 is present at that merchant. Transactions may be fully completed using the mobile device 104 for initiating and paying for the transaction. Digital or electronic coupons may occasionally be provided to the mobile device 104. These coupons may provide a discount to the user 102 of the mobile device 104 when he or she makes a purchase.
[0031] A coupon activation module 214 may regulate use and redemption of coupons based on geolocation and/or other factors. The coupon activation module 214 may activate a coupon when the mobile device 104 is located at a merchant 106. Prior to activation, the coupon activation module 214 may conceal all or part of the coupon from the user 102. For example, the user reading an electronic document 212 may be unable to see a coupon included in that electronic document 212 unless the user takes the mobile device 104 inside a certain merchant 106. In other examples, the user 102 may know that the electronic document 212 contains a coupon, but be unable to view the amount of discount or other aspect of the coupon until the user 102 and the mobile device 104 are at the merchant 106.
[0032] 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 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 antenna 224 may, in some implementations, communicate directly with a merchant 106 such as by exchanging wireless signals with the point-of-sale device 110 located at the merchant 106. 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.
[0033] 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. 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).
[0034] 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. 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. In some implementations, the coupon activation module 214 may activate a coupon in response to a signal received from a merchant 106 via the network interface 232. In other implementations the coupon activation 214 module may activate a coupon when the mobile device 104 is within a predetermined proximity of a merchant associated with the coupon.
Illustrative Server
[0035] FIG. 3 is a schematic representation of the server(s) 118 of FIG. 1 . The one or more servers 118 may be implemented as a single computing device, a server farm comprising multiple servers, a distributed network, a cloud-computing configuration, and/or the like. The server(s) 118 comprises one or more processors 302 and a memory 304. The memory 304 may contain the same user identifier (1) 208 associated with the mobile device 104 FIG. 2 . In some implementations, memory 304 may contain thousands or even millions of separate user identifiers represented here as User ID (N) 306 where N is any number greater than one. Each user identifier may be associated with a respective mobile device.
[0036] The user identifier 208 represents a user 102 that is interacting with the server(s) 118 via a mobile device 104. The authentication module 124 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 124 of the server(s) 118 and the mobile device 104. The authentication module 124 may similarly authenticate the identity of merchants 106 and/or online retailers 126.
[0037] The server(s) 118 may also include a notification module 308. In some implementations, the notification module 308 on the server(s) 118 provides a notification in the form of an e-mail, text, or similar message to the mobile device 104. The notification may be sent when there is a match between a good and/or service of interest to the user 102 and a good and/or service offered by a merchant 106 within a predetermined proximity of the geolocation of the mobile device 104. In some implementations, the notification module 308 may send a notification to the merchant 106 informing the merchant that a nearby user 102 may be interested in a good or service offered by the merchant 106.
[0038] A recommendation module 310 stored on the server(s) 118 may provide recommendations to the mobile device 104. The recommendations may suggest to the user 102 of the mobile device 104 nearby merchants 106 that sell a good or service in which the user 102 may have an interest. The recommendation module 310 may also identify nearby merchants 106 that offer a discount in the form of a coupon or such to the user 102. In some implementations, the recommendation module 310 may also recommend goods or services for sale by online retailers 126. The recommendation of an online retailer 126 may be provided together with recommendation for a nearby merchant 106. Depending on the goods and/or services sold by the merchant 106 and the online retailer 126, the relationship may be one of competition or collaboration. In a relationship deemed to be competitive, the recommendation module 310 may inform the user 102 that a nearby merchant 106 and an online retailer 126 both offer the same in good or service for sale. However, in a relationship deemed to be complementary, the online retailer 126 may offer something that is not available from the nearby merchant 106 but may enhance or complement a good or service sold by that merchant 106.
[0039] The server(s) 118 may also facilitate advertising via communications (e.g., notifications, recommendations, and the like) sent from or on behalf of the merchant 106 to the mobile device 104. For example, an entity that controls the server(s) 118 may generate revenue by charging merchants 106 and/or online retailers 126 for the privilege of being included in notifications sent from the notification module 308 and/or recommendations sent from the recommendation module 310. A payment module 312 in the server(s) 118 may receive and process payments from merchants 106 and/or online retailers 126. The payments may be in the form of a “virtual” currency or points that are accepted as payment by the entity that controls the server(s) 118 but are not a standard currency. Users 102 may opt in to receive notifications and recommendations provided by the server(s) 118. The payment received by the payment module 312 may be structured as a flat fee, a per unit fee, or determined by bidding between various merchants 106 and/or online retailers 126. The operator of the server 118 may structure the payment system so as to maximize revenue paid by the merchants 106 and/or online retailers 126.
[0040] FIG. 4 is a data store including user information 120 that may be included within or connected to the server(s) 118. The user information 120 may contain some or all of the same information stored as user information 210 on the mobile device 104. In some implementations, the user information 120 stored on the server(s) 118 may be used to backup or restore the user information 210 on the mobile device 104 if, for example, the mobile device 104 is lost or damaged.
[0041] The user information 120 may provide separate data associated with each of the user identifiers 208-306 shown in FIG. 3 . For example, User ID (1) 208 may be associated with payment information 402, a user profile 404, a transaction record 406, and a list of goods and/or services of interest to the user 408. The payment information 402 may include such things as credit card or debit card numbers, bank account information, electronic payment system information, and/or the like. The user profile 404 may contain user preferences, lists of interests and hobbies, indications of which types of communications and/or transactions the user 102 has selected to receive, personal information such as preferences for a matchmaking service, and any other type of information associated with the user 102 and his or her User ID (1) 208. The transaction record 406 may contain a past transaction history comprising the identity of the seller (e.g., which merchant 106 or online retailer 126), time, geolocation, and subject of the transaction.
[0042] The list of items of interest to the user 408 may provide a list of goods and/or services that the user 102 might wish to purchase. The user's desires may be inferred from past activity by the user 102 in which he or she explicitly or implicitly indicated an interest in some good or service. For example, a list of previously viewed goods and/or services 410 may track those web pages or good/service descriptions that the user 102 has viewed previously in a web browser or another format. More definitive indications of the user's interest may be determined by reviewing the contents of a wish list 412 that the user 102 has generated himself or herself. The user 102 may establish a wish list on multiple online retailers 126, on another location such as a personal website, etc. and all of the different wish lists may be merged into the wish list 412 stored as part of the user information 120. An even stronger indication of what the user 102 is likely to buy may be determined by viewing the contents of an online shopping cart 414. The shopping cart 414 may represent those goods or services that the user 102 has begun, but not finished, purchasing from an online retailer 126. For some online retailers 126, a shopping cart may disappear if the user 102 does not complete the purchase within a fixed period of time, but for other online retailers 126 a virtual shopping cart may persist indefinitely. A user 102 could have multiple shopping carts at various online retailers 126 each containing one or more goods or services. The shopping cart 414 included in the user information 120 may represent an aggregation of the individual shopping carts from multiple different online retailers 126.
[0043] FIG. 5 is a data store including merchant profiles 122 that may be included within or connected to the server(s) 118. The merchant profiles 122 contain information about the merchant 106 such as geolocations 500 of the merchant's brick-and-mortar locations, goods and/or services 502 offered for sale by the merchant 106, one or more promotions 504 offered by the merchant, reviews and ratings of the merchant 506, and other data.
[0044] The geolocations 500 may be one source of data used to determine whether a mobile device 104 is “near” or within a predetermined proximity of a merchant location. In some implementations, the geolocations 500 may be stored as coordinates such as latitude and longitude and compared with a coordinates of the mobile device 104 such as latitude and longitude determined by a GPS. The goods and/or services 502 available at the merchant 106 may be a real-time or near real-time list of inventory or the identified goods and/or services 502 may indicate things that the merchant 106 typically offers for sale without regard to current availability.
[0045] The promotions 504 may include things such as coupons or discounts for the goods or services offered by the merchant. The promotions 504 may also be usable at a different merchant. For example, by logging in or checking in at a first merchant the user may receive a promotion that is redeemable at a second, different merchant. The first merchant may pay some or all of the costs associated with providing the promotion at the second merchant. The promotions 504 may, for example, give a discount to a user 102 based on the user information 120 for that user 102. For example, a merchant 106 may provide a coupon to a user 102 of a mobile device 104 for items that are included in a user's wish list 412. The coupons may provide a fixed discount or a percentage discount. For example, a coupon may provide the recipient with a fixed savings of $20 for any purchase of $50 or more. Alternatively, the coupon may provide a 50% off discount. Similarly, the coupon may provide for buy-one-get-one-free, buy-two-get-the-third-free, or similar types of discounts related to a number of items purchased.
[0046] The reviews and ratings 506 of the merchant may be provided by professional editors or reviewers or by voting or group rating from several users.
Illustrative Notifications and Recommendations Based on Geolocation
[0047] FIG. 6 shows an illustrative architecture 600 in which a representative user 102 receives information about nearby merchants on a mobile device 104. The user 102 and his or her mobile device 104 may be located near several merchants represented here as merchant (1) 602 merchant (2) 604, and merchant (3) 606. The merchants may be similar to the merchant 106 shown in FIG. 1 . The location of the mobile device 104 may be determined by the location sensor 230 shown in FIG. 2 . For example, the satellite 112 may provide global positioning information to the mobile device 104. The locations of the various merchants 602, 604, and 606 may be provided directly to the mobile device 104 (e.g., by wireless radio wave transmissions) or included as a geolocation 500 stored in a merchant profile 122 available to the server(s) 118. In this implementation, the server(s) 118 may compare a geolocation of the merchants 602, 604, and 606 with a geolocation of the mobile device 104 to determine the relative proximity of the user 102 with the merchants 602, 604, and 606.
[0048] The concept of “near” may be determined by a predetermined proximity, such as a circle 608, centered on the user 102 and the mobile device 104. The size of the circle 608, which may be represented by a radius, may vary based on geolocation of the mobile device 104, user preferences set by the user 102, a strength of wireless signals received by the mobile device 104, or other factors. The size of the circle 608 may also vary over time and vary based the nature of an interaction between the user 102 and the mobile device 104. Although illustrated here as a circle 608, the predetermined proximity relative to the mobile device 104 may have any shape. For example, if the user 102 is in an urban environment where streets are arranged in a regular grid pattern, the shape may be a square or rectangle.
[0049] The location of the circle 608 or the point about which the circle is centered may in some implementations be based on a fixed location rather than the current location of the mobile device 104. For example, the user 102 may provide his or her home, work, or other address. The user 102 may frequently shop around this fixed location and may also frequently return to this fixed location. Thus, in some implementations the user 102 may receive notifications of coupons that are useful at merchants near his or her home, office, etc. even when his or her mobile device 104 is at another geolocation.
[0050] The architecture 600 also shows a merchant (4) 610 and a merchant (5) 612 that are outside the predetermined proximity of the mobile device 104. In some implementations, information about these merchants 610 and 612 may not be provided to the user 102 because the merchants 610 and 612 are deemed too far away. Although three merchants 602, 604, and 606 are shown as being within the predetermined proximity and two merchants 610 and 612 are shown as being outside of the predetermined proximity, these numbers are only illustrative and any number of merchants (including zero) may be inside or outside of the predetermined proximity.
[0051] Each of the merchants 602, 604, 606, 610, and 612 may be associated with items 502 offered for sale by that merchant. The specific items that are available may be identified by the server(s) 118 in reference to the merchant profiles 122 of each of the respective merchants 602, 604, 606, 610, and 612.
[0052] The server(s) 118 may also have access to the user information 120 as shown in FIG. 4 . The user identifier 208 associated with the mobile device 104 and that user's user information 120 may allow the server(s) 118 to compare a list of items of interest 408 to the user with the goods and/or services 502 offered for sale by the various merchants. When there is a match and the matching merchant is within the circle 608 or predetermined proximity of the mobile device 104, the user 102 may be notified of the match.
[0053] One or more online retailers 126 may also be in communication with the server(s) 118 and or in communication with the mobile device 104. In some implementations, the server(s) 118 may compare goods and/or services offered by the online retailer(s) 126 with goods and/or services 502 offered by the nearby merchants 602, 604, and 606 and make a recommendation to the user 102 that includes either or both of the offerings from the online retailer(s) 126 and from the nearby merchants 602, 604, and 606.
[0054] The information provided to the user 102 in the form of a notification, recommendation, or communication may be a type of advertisement in which the nearby merchants 602, 604, and 606 compete with other brick-and-mortar merchants as well as the online retailers 126 to make a sale to the user 102. For example, the nearby merchants 602, 604, and 606 may use data from the “online world” such as the transaction record 406 or list of items of interest 408 to the user to try to drive brick-and-mortar sales. Alternatively, the merchants 602, 604, and 606 may submit lists of goods and/or services available for sale as well as promotions such as coupons to an online repository such as the merchant profiles 122 shown in FIGS. 1 and 5 . The online repository (e.g. server(s) 108 connected to the merchant profiles 122) may analyze characteristics of the users to determine which users receive promotions or notifications regarding the merchants 602, 604, and 606. Conversely, the online retailers 126 may have information about their items sent together with information about the items 502 at the local merchants 602, 604, and 606. If the online retailers 126 can offer a lower price, this may dissuade the user 102 from making a purchase from the brick-and-mortar merchant. Other types of competitive and collaborative relationships between online retailers and off-line merchants that utilize geolocation of the mobile device 104 and user information 120 are discussed below.
[0055] FIGS. 7 a and 7b illustrates a process 700 for sending a notification about items available at a merchant to a user of a mobile device. At operation 702, an identifier of a user is received from a mobile device. The identifier of the user may be the same or similar to the user identifier 208 shown in FIGS. 2-4 .
[0056] At operation 704, items of interest to the user may be identified. Identification of which items are of interest to the user may be based on the identifier of the user. The items of interest to the user may be a list of goods and/or services that the user has previously viewed, a wish list of goods and/or services, a list of goods and/or services included in a shopping cart that the user has with an online retailer, items identified in a user profile associated with the user, or another similar source of information about the user's interests. The user profile may be similar to the user profile 404 shown in FIG. 4 . For example, the user may also manually select categories of goods and/or services of interest and these categories may be stored as part of the user profile. The user profile may also be linked to a social network or list of friends and items of interest to the user may be inferred from items or interest, including items purchased, by friends or social network contacts. The user profile may also be partially or entirely imported from an external source such as a website managing the social network. The identifier of the user may provide access to the user's account on the social network (or other) site, and thus, provide access to an external user profile.
[0057] At operation 706, a geolocation of the mobile device is determined. The geolocation may be determined by the location sensor 230 shown in FIG. 2 .
[0058] At operation 708, a merchant or plurality of merchants is identified that is within a predetermined proximity of the geolocation of the mobile device. The merchant(s) may be identified by referencing a map of merchant locations and comparing the map with the geolocation of the mobile device to determine distances between the mobile device and various merchants. The predetermined proximity may be a distance such as a radius that forms a circle around the user as shown in FIG. 6 .
[0059] At operation 710 the items identified at operation 704 are compared with items offered by the merchant identified at operation 708. Conversely, the items offered by the merchant at operation 708 may be compared with the items identified at operation 704. This way, the merchant may identify if its offered items are similar to any of the items of interest to the user. The offered items may include any goods and/or services in the inventory of that merchant.
[0060] In one implementation, the geolocation of the merchant and the currently in stock items of the merchant may be received from the merchant at operation 712. For example, the merchant may submit its geolocation and list of current inventory to a server for incorporation in a merchant profile such as the merchant profiles 122 shown in FIG. 5 . A server, such as the server(s) 118 discussed above, may compare the items of interest to the user and the merchant's inventory without revealing any of the user's information to the merchant. This may allow the user to receive the benefit of knowing when a nearby merchant is offering items that match, or are related to, his or her interests without having to reveal information to the merchant.
[0061] In another implementation, a list of the items of interest to the user is provided to the merchant at operation 714. The comparison may be performed by the merchant and then a response may be received from the merchant at operation 716. Either or both of the user and the server may receive the response. The response may indicate a “yes” or “no” depending on if the merchant has items that match the user's interests. The response may also indicate a payment or payment commitment from the merchant to the source (e.g., the server) that identified the items of interest to the user. Providing the items of interest to the user directly to the merchant may allow the list to be compared with the merchant's inventory without requiring a server. This may be appropriate when the mobile device can communicate directly with the merchant, but the mobile device is unable to access a network connection for communicating with a server.
[0062] Irrespective of the techniques used for making the comparison, at operation 718, it is determined whether or not the merchant offers items of interest to the user or items related to items of interest to the user. For example, if a baseball is an item of interest to the user it may be inferred that a bat or glove, although not direct matches, would also be of interest to the user. If no match exists, process 700 proceeds along the “no” path and returns to operation 706. As the mobile device moves, different merchants may come within the predetermined proximity of the mobile device and one of these new merchants may offer an item that is of interest to the user. If the merchant does offer an item of interest to the user, process 700 proceeds along the “yes” path. The following portions of process 700 are shown on FIG. 7 b.
[0063] At operation 720, a notification of the determination from operation 718 is generated. The notification may simply state that a match exists. However, the notification may also identify such things as which item of interest to the user is offered by the merchant, which nearby merchant offers that item for sale, a map to the merchant, a price of the good or service, any coupon or discount available for the good or service, a redemption period for the coupon or discount, a maximum number of items available per person, and/or other information.
[0064] When a plurality of merchants is identified at operation 708, the notification may include a list or map of those merchants. If the identified merchants are relatively nearby (e.g., within 100 yards) the notification may be a list of the merchants showing a distance to the merchants. If the identified merchants are farther away (e.g., within five miles) the notification may include a map showing the locations of the merchants. The notification may also include the price of the item at the merchants so that the user can easily compare prices.
[0065] At operation 722, a decision is made to contact or not to contact the merchant. This decision may be based on a user profile or other type of information about the user that is associated with the identifier of the user. When the merchant is not contacted, process 700 proceeds along the “no” path to operation 724.
[0066] At operation 724, the notification generated at operation 720 is sent to the mobile device. For example, the items identified at operation 704 may be a list of goods and/or services the user has on a shopping list for Christmas or another holiday. As the user, with his or her mobile device, moves through a shopping mall the mobile device may receive a series of notifications telling the user which items from his or her shopping list are at which stores. This may allow the user to quickly find and purchase the items on his or her list and this technique may also allow the user to find the merchant with the lowest price for items on the list.
[0067] If at operation 722 the decision is made to contact the merchant, then process 700 proceeds along “yes” path to operation 726. At operation 726, the notification generated at operation 720 is sent to the merchant. Once informed that the merchant offers items that are of interest to the user, the merchant may wish to contact the user of the mobile device with the hope of making a sale. The decision to contact the user may be based on an available and unused inventory of the merchant. For example, if the merchant is a service provider like a spa or a restaurant the merchant may have relatively fixed costs, and thus, be concerned about minimizing unused capacity. The merchant may decide how many users to contact and how aggressively to promote a item of interest to the user based on the merchant's excess capacity or excess inventory.
[0068] At operation 728, a payment may be received from the merchant. The payment may be received by a server implementing the process 700 such as, for example, the server(s) 118 shown in FIGS. 1 and 3 . The payment may be received and processed by the payment module 312 shown in FIG. 3 . Responsive to receiving the payment, the process 700 may proceed to operation 724 and send a notification to the mobile device. The payment amount may be arrived at through a bidding process between multiple merchants. For example, when more than one merchant within the predetermined proximity of the mobile device has the same good or service for sale, each of those merchants may place competitive bids and the merchant with the winning bid may be included in the notification sent to the mobile device at operation 724.
[0069] The notification to the mobile device sent at operation 724 may also included a coupon for one of the goods or services of interest to the user. Merchants may choose to have coupons included in the notification in order to encourage the user to purchase the good or service that matches his or her interests. The user's interest may be determined from the user information 120 shown in FIG. 4 . In some implementations, data mining techniques may be applied to the user information in order to infer the user's interests. For example, if the user's interests are derived from an online shopping cart the user has established with an online merchant, the merchant may provide a coupon that lowers the price of the goods or service to equal or less than the price offered by the online retailer. The online retailers may choose to reveal the contents of online shopping carts and the price of the items in those shopping carts to the merchants only if the merchants compensate the online retailer for “taking” the sale. For example, if the online retailer's profit margin generates profits of one dollar for the sale of a certain good, then the online retailer may provide shopping cart information to the merchant in exchange for a fee of one dollar. The fee may also be contingent on whether or not the user actually purchases the good from the merchant. In some implementations, payments from the merchant to an online retailer may be mediated by the server(s) 118.
[0070] As discussed above, the notification may also be a map showing locations of merchants that have items matching the items of interest to the user. For example, each indication on the map of a merchant location may provide additional information about that merchant (e.g., in a pop-up window) such as the list of matching or similar items, item prices, identification of coupons or deals available to the user the mobile device, and the like.
[0071] FIG. 8 illustrates a process 800 for providing recommendations of online purchases together with information about a nearby brick-and-mortar merchant. At operation 802, an identifier of a user is received from a mobile device. Similar to operation 702 shown in FIG. 7 , receiving an identifier of a user can function to associate information about the user with the mobile device.
[0072] At operation 804, a request for recommendation of a merchant that is within a predetermined proximity of the mobile device is received. In some implementations, the request may be sent manually by the user of the mobile device for example in response to the user pressing a “recommend nearby merchants” button. In other implementations, the request may be transmitted automatically by the mobile device.
[0073] At operation 806, the geolocation of the mobile device is determined. The geolocation may be determined by the location sensor 230 shown in FIG. 2 .
[0074] At operation 808, a merchant within the predetermined proximity of the mobile device that also provides a discount to the user of the mobile device is identified. The discount may be based on an attribute associated with the identifier of the user received at operation 802. For example, if the user is a member of a group that receives a discount at a particular merchant, then that merchant may be identified if the user-member is within the predetermined proximity. If the merchant is nearby the users home or work address then the contact information of the user may be a source of determining eligibility for a discount. Similarly, financial information of the user such as a type of credit card owned by the user or a credit score may provide the user with access to discounts that are not universally available. When more than one merchant within the predetermined proximity of the mobile device offers a discount to the user of the mobile device, a plurality of merchants within the predetermined proximity may be identified. The geolocations of each of the plurality of merchants may be used to generate a map, for example with “flags” or “pins” in the map showing the location of the merchants. This map may be sent to the mobile device of the user so that the user can navigate to and select from the plurality of merchants.
[0075] In some implementations, a merchant or merchants may be identified based on a transaction record 406 of the user. For example, the transaction record 406 may identify merchants with which the user has a pre-existing relationship. The transaction record 406 may also identify merchants at which the user has previously used a coupon or otherwise received a discount.
[0076] In other implementations, the merchant may be identified based on a list of goods and/or services 408 of interest to the user. This list 408 may be any of the types of lists shown in FIG. 4 such as a list of goods and/or services that the user has previously viewed, a wish list of goods and/or services, a list of goods and/or services in a shopping cart associated with the user or a list derived directly or indirectly from information in a user profile of the user. For example, the user's interest may be inferred by identifying those merchants at which the user has logged in to an online system from his or her mobile device.
[0077] In further implementations, a merchant may be identified based on ratings or reviews 810 of that merchant. The ratings and reviews 810 may be the same as the ratings and reviews 506 from the merchant profiles 122 shown in FIG. 5 . For example, only high-ranked merchants (e.g., four-star or five-star ranking) may be eligible to be identified. The use of ratings and/or reviews 810 to identify merchant may also involve social networking as a source for the ratings and reviews 810. Thus, ratings and/or reviews 810 from others the user's social network may be a source, or the sole source, of ratings and reviews 810 used to identify the merchant.
[0078] At operation 812, a recommendation of the merchant is sent to the mobile device. In some implementations, the recommendation may be generated and sent by the recommendation module 310 of the server(s) 118 that is shown in FIG. 3 . The recommendation provides user with information about a merchant that is both nearby and that provides a discount to the user.
[0079] The recommendation of the merchant may include a list of merchants 814 when multiple merchants within the predetermined proximity match the criteria specified by the user. The recommendation may also be accompanied by ratings or reviews 810 of the merchant derived from other users, professional reviews, and the like. The ratings and reviews 810 may also be included in the recommendation. If the ratings and reviews 810 were not used to identify the merchant at operation 808, the user may consider the ratings and reviews 810 when evaluating the recommendation. The recommendation may also included directions 816 to the merchant. In some implementations, a coupon 818 for the merchant may be included with the recommendation. The coupon 818 may provide an additional discount beyond the discount associated with the user identifier. The recommendation sent at operation 810 may also include any combination of the above features.
[0080] At operation 820, a recommendation for a good or service available from an online retailer is also sent to the mobile device. This recommendation may be generated by the recommendation module 310. The recommendation for the good or service available online may be an advertisement that encourages the user to purchase the good or service from the online retailer. The good or service available online may be competitive with the goods and/or services offered by the merchant recommended at operation 810. In other words, the user may be provided with information about where to purchase a good or service at a nearby merchant and information about how to purchase a same or similar good or service from an online retailer.
[0081] In some implementations, the online retailer may pay an advertising fee (e.g., to the entity that operates the server(s) 118) in order to have a recommendation sent to the mobile device. Conversely, the merchant may also be provided an opportunity to pay a fee to limit potential online competitors from having a recommendation piggybacked onto the recommendation of the merchant. For example, merchants may request that when they are included in a recommendation sent at operation 812 that the recommendation for an online good or service sent at operation 820 recommends something from that merchant's online store, recommends something from any online merchant except for a specified list of “rival” online merchants, or otherwise influence the recommendation provided that operation 820. The online retailer and the merchant may also compete or bid against each other for control of the recommendation provided at operation 820.
[0082] In other implementations, the good or service available from the online retailer may be a good or service that has been deemed complementary to the goods and/or services offered by the merchant. The user, the merchant, the online retailer, a server or any other entity may make determinations as to which goods and/or services are complementary.
Illustrative Promotions Based on Geolocation
[0083] FIG. 9 shows an illustrative timeline 900 showing activation of a coupon or other promotion when the mobile device 104 is at a merchant 106. The coupon, or other promotion, may be tied to a specific geolocation so that the user 102 can only redeem the coupon when he or she is located at a particular merchant 106. This may drive foot traffic to the merchant 106 because users may wish to activate and redeem the coupon. Even if the coupon is unrelated to the goods and/or services sold by the merchant 106, this may provide a benefit for the merchant 106 because the users once at the merchant 106 might purchase a good and/or service.
[0084] At time 1, the mobile device has an electronic document 212 stored in memory as shown in FIG. 2 . In some implementations, this electronic document 212 may be an electronic book or an eBook. The electronic document 212 includes an inactive coupon 902 within the document. The inactive coupon 902 may be included as part of the text or other content of the electronic document 212. The inactive coupon 902 may also be attached to or otherwise appended to the electronic document 212. The inactive coupon 902 may also be provided as a stand-alone product that is not included in an electronic document 212.
[0085] When the user 102 and the mobile device 104 are not located at the merchant 106 the inactive coupon 902 may remain inactive. The inactive/active status of the coupon may be regulated by the coupon activation module 214 of the mobile device 104 shown in FIG. 2 . In some implementations, the inactive coupon 902 may be concealed from the user 102 of the mobile device 104 until the mobile device 104 is located at the merchant 106. In other implementations, only one or more aspects of the coupon are concealed. Alternatively, all aspects of the coupon may be revealed to the user 102 even when the mobile device 104 is not located at the merchant 106. If the inactive coupon 902 is provided by itself without an electronic document 212, the existence of the inactive coupon 902 may not be wholly concealed from the user 102, but the specific nature of the “deal” or coupon may be concealed. For example, a user may be able to tell that he or she has an inactive coupon 902 from a certain merchant, but not know what the coupon is for or the size of the discount. Curiosity may drive foot traffic to the merchants that provide this type of partially-hidden coupon.
[0086] In some implementations in which the coupon is fully concealed, the coupon may function like a surprise or “Easter egg” that unexpectedly rewards the user. Once one person discovers the existence of the coupon, this information may spread informally or “virally” and can create a further incentive for additional people to obtain the electronic document 212. In implementations in which only some aspects of the coupon are concealed, the merchant at which the coupon can be redeemed may be exposed to the user 102, but other details such as the amount of discount may remain concealed.
[0087] At time 2, when the user 102 and the mobile device 104 arrive at the merchant 106, the coupon may become an active coupon 904. Activation may also be linked to time. A coupon may not become an active coupon 904 unless the current time matches a time specified by the inactive coupon 902. For example, in order to encourage repeat business a coupon may not be active until the following day. Thus, in some implementations, both time and place must be as specified in order for an inactive coupon 902 to become an active coupon 904.
[0088] Activation of the coupon may be implemented by the mobile device 104 receiving a signal from the point-of-sale device 110 or from the network 116. Activation may also be implemented by the coupon activation module 214 alone or in conjunction with other components of the mobile device 104 such as the location sensor 230 and/or the calendar/clock 228. The location sensor 230 may determine that the geolocation of the mobile device 104 corresponds to the geolocation of the merchant 106 and the coupon activation module 214 may activate the coupon. For coupons that are valid only during a certain time period, the calendar/clock 228 may also determine if the current time is within a time period specified for redemption of the coupon. At this point, any aspects of the coupon that were concealed may be revealed to the user 102.
[0089] FIG. 10 shows an illustrative process 1000 for activating and using a coupon in an electronic document. At operation 1002, an electronic document containing a coupon may be downloaded to a mobile device. Depending on the relative perceived value of the electronic document and of the coupon, the user of the mobile device may choose to initiate the download primarily to receive the electronic document or primarily to receive the coupon.
[0090] At operation 1004, all or part of the coupon may be concealed when the mobile device is not located at the merchant. This may tie the value of the coupon to the user's presence at the merchant. Thus, for example, a coffee shop may pay to have coupons placed in eBooks in order to bring people into the coffee shop to redeem the coupon with the hope that those people will buy something from the coffee shop.
[0091] At operation 1006, it is determined if the mobile device storing, in memory, the electronic document that contains the coupon is at the merchant. The mobile device may be characterized as being “at” the merchant when the mobile device is within a predetermined proximity of the merchant. The mobile device may also be determined to be at the merchant when the mobile device receives a signal from the merchant. The signal may be a “heartbeat” or “ping” that is transmitted only over a short distance. When the mobile device is at the merchant, process 1000 follows the “yes” path to operation 1008. When the mobile device is not at the merchant, process 1000 follows the “no” path and returns to operation 1004 where all or part of the coupon may remain concealed.
[0092] At operation 1008, any part of the coupon that was concealed may be revealed or shown to the user. At operation 1010 when the mobile device is at the merchant, the coupon is activated. In some implementations the coupon activation module 214 of the mobile device may activate the coupon. The coupon may be activated in response to determining that the mobile device is located at the merchant in operation 1006. The coupon may also be activated in response to a signal from the merchant 1012.
[0093] At operation 1014, a command from the user of the mobile device to use the coupon as part of purchase of a good or service is received. The command may be an explicit command to use the coupon or the command may be implicit in that the coupon is automatically applied when the purchase is transacted. The transaction may be a purchase of a good or service at the same merchant where the coupon was activated 1016 or the transaction may be with an online retailer 1018. The transaction with the online retailer 1018 may be completed by using the mobile device.
[0094] If the active coupon is redeemed at the merchant 1016, the active coupon may appear in the electronic document as a machine-readable code such as a barcode that can be presented to the point-of-sale device at the merchant. The active coupon may also be a code or pass phrase that the user can show or tell an employee of the merchant in order to receive the discount.
[0095] In implementations in which, the coupon is be activated at the merchant, but redeemable at an online retailer 1018. The mobile device may connect to a network from within the merchant to use the active coupon at an online retailer. The active coupon may remain active once activated even if the mobile device later leaves the merchant or, in other implementations, the active coupon may revert to an inactive coupon once the mobile device is no longer located at the merchant.
Claims
What is claimed is:
1. A mobile device comprising:
one or more processors;
a network interface communicatively coupled to the one or more processors; and
a memory communicatively coupled to the one or more processors, the memory comprising:
an electronic document including an inactive coupon associated with a merchant, the inactive coupon to remain inactive until it is determined that the mobile device is located at the merchant; and
a coupon activation module configured to:
conceal, at least temporarily, a first aspect of the inactive coupon from a user of the mobile device while exposing, on the mobile device, a second aspect of the inactive coupon, the second aspect specifying the merchant at which the inactive coupon, upon activation, is redeemable; and
activate, without user intervention and using a signal received from the merchant via the network interface, the inactive coupon to become an active coupon based at least in part on the mobile device being located at the merchant, and, subsequent to the activation, to revert the active coupon to the inactive coupon based at least in part on the mobile device no longer being located at the merchant.
2. The mobile device as recited in claim 1, wherein the mobile device comprises an electronic book reader device.
3. The mobile device as recited in claim 1, wherein the electronic document comprises an eBook.
4. The mobile device as recited in claim 1, wherein the active coupon is redeemable for a good or service from the merchant.
5. The mobile device as recited in claim 1, wherein the coupon activation module is further configured to conceal the inactive coupon from the user of the mobile device until the mobile device is located at the merchant.
6. The mobile device as recited in claim 1, further comprising a location sensor coupled to the one or more processors, the location sensor configured to determine a geolocation of the mobile device and compare the determined geolocation of the mobile device with a location of the merchant in order to determine when the mobile device is located at the merchant.
7. A computer-implemented method comprising:
under control of one or more computer systems configured with executable instructions, storing, in memory of a mobile device, an electronic document that includes an inactive coupon;
concealing, at least temporarily, a first part of the inactive coupon from a user of the mobile device while exposing, on the mobile device, a second part of the inactive coupon, the second part specifying a merchant at which the inactive coupon, upon activation, is redeemable;
determining that the mobile device is located at the merchant associated with the inactive coupon;
receiving, by a network interface of the mobile device, a signal from the merchant;
at least partly in response to the determining that the mobile device is located at the merchant, activating, without user intervention and using the signal received from the merchant via the network interface, the inactive coupon included in the electronic document to become an active coupon;
determining, subsequent to the activating, that the mobile device is no longer located at the merchant; and
deactivating the active coupon by reverting the active coupon to the inactive coupon at least partly in response to the determining that the mobile device is no longer located at the merchant.
8. The method as recited in claim 7, wherein the determining that the mobile device is located at the merchant comprises receiving a particular signal from the merchant at the mobile device.
9. The method as recited in claim 7, wherein the determining that the mobile device is located at the merchant comprises determining that the mobile device is located within a predetermined proximity of the merchant.
10. The method as recited in claim 7, further comprising receiving a command from a user of the mobile device to use the active coupon as part of a purchase of a good or service from the merchant.
11. The method as recited in claim 7, further comprising receiving a command from the user of the mobile device to use the active coupon as part of a purchase of a good or service from an online retailer, the purchase completed at least in part by the mobile device.
12. The method as recited in claim 7, further comprising downloading the electronic document including the inactive coupon to the mobile device.
13. The method as recited in claim 7, further comprising concealing all or part of the inactive coupon from the user of the mobile device when the mobile device is not located at the merchant.
14. One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by one or more processors, instruct a computing device to perform acts comprising:
storing, in memory of a mobile device, an electronic document that includes an inactive coupon;
refraining from revealing, at least temporarily, a first aspect of the inactive coupon included in the electronic document to a user of the mobile device while exposing, on the mobile device, a second aspect of the inactive coupon, the second aspect specifying a merchant at which the inactive coupon, upon activation, is redeemable;
determining that the merchant associated with the inactive coupon is within a predetermined proximity of a location of the mobile device;
receiving a signal from the merchant;
at least partly in response to the determining that the merchant is within the predetermined proximity of the location of the mobile device, activating, without user intervention and using the signal received from the merchant via a network interface of the mobile device, the inactive coupon included in the electronic document to become an active coupon;
determining, subsequent to the activating, that the merchant is no longer within the predetermined proximity of the location of the mobile device; and
deactivating the active coupon by reverting the active coupon to the inactive coupon at least partly in response to the determining that the merchant is no longer within the predetermined proximity of the location of the mobile device.
15. The one or more non-transitory computer-readable media as recited in claim 14, wherein the acts further comprise refraining from revealing the inactive coupon to the user of the mobile device until the mobile device is located within the predetermined proximity.
16. The one or more non-transitory computer-readable media as recited in claim 14, wherein the acts further comprise activating the inactive coupon in response to determining that a current time matches a predetermined time specified by the inactive coupon.
17. The one or more non-transitory computer-readable media as recited in claim 14, wherein the determining that the merchant associated with the inactive coupon is within the predetermined proximity of the location of the mobile device comprises receiving a particular signal from the merchant at the mobile device.
Patent Citations (210)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5914472(A) | 1999-06-01 | Foladare et al. | Applicant |
| US6108650(A) | 2000-08-01 | Musk et al. | Applicant |
| US6343279(B1) | 2002-01-01 | Bissonette et al. | Applicant |
| US6505046(B1) | 2003-01-01 | Baker | Applicant |
| US6738749(B1) | 2004-05-01 | Chasko | Applicant |
| US6756879(B2) | 2004-06-01 | Shuster | Applicant |
| US7392534(B2) | 2008-06-01 | Lu et al. | Applicant |
| US7434723(B1) | 2008-10-01 | White et al. | Applicant |
| US7657489(B2) | 2010-02-01 | Stambaugh | Applicant |
| US7725390(B2) | 2010-05-01 | Plant | Applicant |
| US7739197(B2) | 2010-06-01 | Jambunathan et al. | Applicant |
| US7788281(B2) | 2010-08-01 | Cole et al. | Applicant |
| US7813717(B2) | 2010-10-01 | Huotari et al. | Applicant |
| US7840222(B2) | 2010-11-01 | Hampel et al. | Applicant |
| US7853786(B1) | 2010-12-01 | Fultz et al. | Applicant |
| US7873708(B2) | 2011-01-01 | Durand et al. | Applicant |
| US7900847(B2) | 2011-03-01 | Lindahl et al. | Applicant |
| US8050991(B2) | 2011-11-01 | Popovic et al. | Applicant |
| US8099109(B2) | 2012-01-01 | Altman et al. | Applicant |
| US8116731(B2) | 2012-02-01 | Buhrmann et al. | Applicant |
| US8135624(B1) | 2012-03-01 | Ramalingam et al. | Applicant |
| US8213898(B2) | 2012-07-01 | Choti et al. | Applicant |
| US8255698(B2) | 2012-08-01 | Li et al. | Applicant |
| US8326767(B1) | 2012-12-01 | Ramanujan et al. | Applicant |
| US8521131(B1) | 2013-08-01 | Ramalingam et al. | Applicant |
| US8606322(B2) | 2013-12-01 | Sabol | Applicant |
| US8744488(B2) | 2014-06-01 | Cousins et al. | Applicant |
| US8849310(B2) | 2014-09-01 | Fan et al. | Applicant |
| US2001/0025257(A1) | 2001-09-01 | Sato | Applicant |
| US2001/0051911(A1) | 2001-12-01 | Marks et al. | Applicant |
| US2002/0046116(A1) | 2002-04-01 | Hohle et al. | Applicant |
| US2002/0065713(A1) | 2002-05-01 | Awada et al. | Applicant |
| US2002/0077876(A1) | 2002-06-01 | O'Meara et al. | Applicant |
| US2002/0091568(A1) | 2002-07-01 | Kraft et al. | Applicant |
| US2002/0123938(A1) | 2002-09-01 | Yu et al. | Applicant |
| US2002/0143638(A1) | 2002-10-01 | August et al. | Applicant |
| US2003/0159066(A1) | 2003-08-01 | Staw et al. | Applicant |
| US2003/0208386(A1) | 2003-11-01 | Brondrup | Applicant |
| US2003/0208684(A1) | 2003-11-01 | Camacho et al. | Applicant |
| US2003/0212609(A1) | 2003-11-01 | Blair et al. | Applicant |
| US2003/0220835(A1) | 2003-11-01 | Barnes, Jr. | Applicant |
| US2004/0002897(A1) | 2004-01-01 | Vishik | Applicant |
| US2004/0019563(A1) | 2004-01-01 | Sines et al. | Applicant |
| US2004/0056101(A1) | 2004-03-01 | Barkan et al. | Applicant |
| US2004/0093620(A1) | 2004-05-01 | Iino et al. | Applicant |
| US2005/0004840(A1) | 2005-01-01 | Wanninger | Applicant |
| US2005/0221843(A1) | 2005-10-01 | Friedman et al. | Applicant |
| US2005/0228719(A1) | 2005-10-01 | Roberts et al. | Examiner |
| US2005/0234771(A1) | 2005-10-01 | Register et al. | Applicant |
| US2005/0240472(A1) | 2005-10-01 | Postrel | Applicant |
| US2005/0267812(A1) | 2005-12-01 | Jensen et al. | Applicant |
| US2006/0047576(A1) | 2006-03-01 | Aaltonen et al. | Applicant |
| US2006/0111955(A1) | 2006-05-01 | Winter et al. | Applicant |
| US2006/0235795(A1) | 2006-10-01 | Johnson et al. | Applicant |
| US2006/0235796(A1) | 2006-10-01 | Johnson et al. | Applicant |
| US2006/0242017(A1) | 2006-10-01 | Libes et al. | Applicant |
| US2007/0084913(A1) | 2007-04-01 | Weston | Applicant |
| US2007/0088610(A1) | 2007-04-01 | Chen | Applicant |
| US2007/0118426(A1) | 2007-05-01 | Barnes, Jr. | Applicant |
| US2007/0136140(A1) | 2007-06-01 | Smith, Jr. | Applicant |
| US2007/0291710(A1) | 2007-12-01 | Fadell | Applicant |
| US2008/0004949(A1) | 2008-01-01 | Flake et al. | Applicant |
| US2008/0005104(A1) | 2008-01-01 | Flake et al. | Applicant |
| US2008/0010121(A1) | 2008-01-01 | McIntosh | Examiner |
| US2008/0040233(A1) | 2008-02-01 | Wildman et al. | Applicant |
| US2008/0040274(A1) | 2008-02-01 | Uzo | Applicant |
| US2008/0086767(A1) | 2008-04-01 | Kulkarni et al. | Applicant |
| US2008/0140522(A1) | 2008-06-01 | Tutone | Applicant |
| US2008/0154765(A1) | 2008-06-01 | Wolfe | Applicant |
| US2008/0154847(A1) | 2008-06-01 | Chellapilla et al. | Applicant |
| US2008/0167991(A1) | 2008-07-01 | Carlson et al. | Applicant |
| US2008/0183576(A1) | 2008-07-01 | Kim et al. | Applicant |
| US2008/0201226(A1) | 2008-08-01 | Carlson et al. | Applicant |
| US2008/0208739(A1) | 2008-08-01 | Phillips | Applicant |
| US2008/0215475(A1) | 2008-09-01 | Ramer et al. | Applicant |
| US2008/0221997(A1) | 2008-09-01 | Wolfe | Applicant |
| US2008/0228600(A1) | 2008-09-01 | Treyz et al. | Applicant |
| US2008/0262928(A1) | 2008-10-01 | Michaelis | Applicant |
| US2008/0268868(A1) | 2008-10-01 | Maitland | Examiner |
| US2008/0275768(A1) | 2008-11-01 | Berman et al. | Applicant |
| US2008/0281677(A1) | 2008-11-01 | Toms et al. | Applicant |
| US2008/0281702(A1) | 2008-11-01 | Kirkwood | Applicant |
| US2008/0318559(A1) | 2008-12-01 | Porco | Applicant |
| US2009/0006203(A1) | 2009-01-01 | Fordyce, III et al. | Applicant |
| US2009/0024700(A1) | 2009-01-01 | Garg et al. | Applicant |
| US2009/0030779(A1) | 2009-01-01 | Tollinger et al. | Applicant |
| US2009/0061884(A1) | 2009-03-01 | Rajan et al. | Applicant |
| US2009/0076896(A1) | 2009-03-01 | DeWitt et al. | Applicant |
| US2009/0076925(A1) | 2009-03-01 | DeWitt et al. | Applicant |
| US2009/0125380(A1) | 2009-05-01 | Otto et al. | Applicant |
| US2009/0125396(A1) | 2009-05-01 | Otto et al. | Applicant |
| US2009/0132417(A1) | 2009-05-01 | Scipioni et al. | Applicant |
| US2009/0138302(A1) | 2009-05-01 | Breznik et al. | Applicant |
| US2009/0143966(A1) | 2009-06-01 | Jacobson et al. | Applicant |
| US2009/0150218(A1) | 2009-06-01 | Brunner et al. | Examiner |
| US2009/0152343(A1) | 2009-06-01 | Carter et al. | Applicant |
| US2009/0157547(A1) | 2009-06-01 | Ruckart | Applicant |
| US2009/0187463(A1) | 2009-07-01 | DaCosta | Applicant |
| US2009/0187466(A1) | 2009-07-01 | Carter et al. | Examiner |
| US2009/0187488(A1) | 2009-07-01 | Shamilian | Applicant |
| US2009/0187492(A1) | 2009-07-01 | Hammad et al. | Applicant |
| US2009/0198607(A1) | 2009-08-01 | Badger et al. | Applicant |
| US2009/0216646(A1) | 2009-08-01 | Seven et al. | Applicant |
| US2009/0222346(A1) | 2009-09-01 | Greene et al. | Applicant |
| US2009/0228325(A1) | 2009-09-01 | Simmons et al. | Applicant |
| US2009/0240582(A1) | 2009-09-01 | Sheldon-Neal et al. | Applicant |
| US2009/0240622(A1) | 2009-09-01 | Zandonadi | Applicant |
| US2009/0271275(A1) | 2009-10-01 | Regmi et al. | Applicant |
| US2009/0281945(A1) | 2009-11-01 | Shakkarwar | Applicant |
| US2009/0292642(A1) | 2009-11-01 | Han | Applicant |
| US2009/0299857(A1) | 2009-12-01 | Brubaker | Applicant |
| US2009/0327135(A1) | 2009-12-01 | Nguyen et al. | Applicant |
| US2009/0327151(A1) | 2009-12-01 | Carlson et al. | Examiner |
| US2010/0004997(A1) | 2010-01-01 | Mehta et al. | Applicant |
| US2010/0006641(A1) | 2010-01-01 | Boutcher et al. | Applicant |
| US2010/0006642(A1) | 2010-01-01 | Boutcher et al. | Applicant |
| US2010/0030651(A1) | 2010-02-01 | Matotek et al. | Applicant |
| US2010/0041419(A1) | 2010-02-01 | Svendsen et al. | Applicant |
| US2010/0042421(A1) | 2010-02-01 | Bai et al. | Examiner |
| US2010/0049615(A1) | 2010-02-01 | Rose et al. | Applicant |
| US2010/0057530(A1) | 2010-03-01 | Parivash et al. | Applicant |
| US2010/0063891(A1) | 2010-03-01 | Townsend et al. | Applicant |
| US2010/0070334(A1) | 2010-03-01 | Monteverde | Applicant |
| US2010/0070365(A1) | 2010-03-01 | Siotia et al. | Applicant |
| US2010/0076829(A1) | 2010-03-01 | Bishop | Applicant |
| US2010/0076849(A1) | 2010-03-01 | Bishop | Examiner |
| US2010/0077036(A1) | 2010-03-01 | DeLuca et al. | Applicant |
| US2010/0082420(A1) | 2010-04-01 | Trifiletti et al. | Applicant |
| US2010/0082445(A1) | 2010-04-01 | Hodge et al. | Applicant |
| US2010/0088188(A1) | 2010-04-01 | Kumar et al. | Applicant |
| US2010/0100454(A1) | 2010-04-01 | Sines et al. | Applicant |
| US2010/0106611(A1) | 2010-04-01 | Paulsen et al. | Applicant |
| US2010/0121717(A1) | 2010-05-01 | Chen | Applicant |
| US2010/0138294(A1) | 2010-06-01 | Bussmann et al. | Applicant |
| US2010/0138344(A1) | 2010-06-01 | Wong et al. | Applicant |
| US2010/0145723(A1) | 2010-06-01 | Hudson et al. | Applicant |
| US2010/0145778(A1) | 2010-06-01 | Fordyce, III et al. | Applicant |
| US2010/0146607(A1) | 2010-06-01 | Piepenbrink et al. | Applicant |
| US2010/0156933(A1) | 2010-06-01 | Jones et al. | Applicant |
| US2010/0169179(A1) | 2010-07-01 | Ramer et al. | Examiner |
| US2010/0190510(A1) | 2010-07-01 | Maranhas et al. | Applicant |
| US2010/0191551(A1) | 2010-07-01 | Drance et al. | Applicant |
| US2010/0191578(A1) | 2010-07-01 | Tran et al. | Applicant |
| US2010/0192230(A1) | 2010-07-01 | Steeves et al. | Applicant |
| US2010/0205167(A1) | 2010-08-01 | Tunstall-Pedoe et al. | Applicant |
| US2010/0217525(A1) | 2010-08-01 | King et al. | Examiner |
| US2010/0241495(A1) | 2010-09-01 | Maniyar et al. | Applicant |
| US2010/0241496(A1) | 2010-09-01 | Gupta et al. | Applicant |
| US2010/0250368(A1) | 2010-09-01 | Porco | Examiner |
| US2010/0260388(A1) | 2010-10-01 | Garrett et al. | Applicant |
| US2010/0262449(A1) | 2010-10-01 | Monteforte et al. | Examiner |
| US2010/0274655(A1) | 2010-10-01 | Postrel | Applicant |
| US2010/0293065(A1) | 2010-11-01 | Brody et al. | Applicant |
| US2010/0306099(A1) | 2010-12-01 | Hirson et al. | Applicant |
| US2010/0312630(A1) | 2010-12-01 | Krutchik et al. | Applicant |
| US2010/0312645(A1) | 2010-12-01 | Niejadlik et al. | Applicant |
| US2010/0312646(A1) | 2010-12-01 | Gupta et al. | Applicant |
| US2010/0323716(A1) | 2010-12-01 | Jaffri | Applicant |
| US2010/0324977(A1) | 2010-12-01 | Dragt | Applicant |
| US2010/0332339(A1) | 2010-12-01 | Patel et al. | Applicant |
| US2011/0010238(A1) | 2011-01-01 | Postrel | Applicant |
| US2011/0015987(A1) | 2011-01-01 | Chakraborty et al. | Applicant |
| US2011/0022424(A1) | 2011-01-01 | VonDerheide | Applicant |
| US2011/0022483(A1) | 2011-01-01 | Hammad | Applicant |
| US2011/0022517(A1) | 2011-01-01 | Hammad | Applicant |
| US2011/0029403(A1) | 2011-02-01 | Xu | Applicant |
| US2011/0053559(A1) | 2011-03-01 | Klein | Applicant |
| US2011/0055005(A1) | 2011-03-01 | Lang | Applicant |
| US2011/0057027(A1) | 2011-03-01 | Grossman et al. | Applicant |
| US2011/0060640(A1) | 2011-03-01 | Thompson et al. | Applicant |
| US2011/0065419(A1) | 2011-03-01 | Book et al. | Applicant |
| US2011/0082735(A1) | 2011-04-01 | Kannan et al. | Applicant |
| US2011/0087430(A1) | 2011-04-01 | Boss et al. | Applicant |
| US2011/0093318(A1) | 2011-04-01 | Guday et al. | Applicant |
| US2011/0106613(A1) | 2011-05-01 | Felt et al. | Applicant |
| US2011/0112892(A1) | 2011-05-01 | Tarantino | Applicant |
| US2011/0131627(A1) | 2011-06-01 | Abendroth et al. | Applicant |
| US2011/0137804(A1) | 2011-06-01 | Peterson | Applicant |
| US2011/0140841(A1) | 2011-06-01 | Bona et al. | Applicant |
| US2011/0184793(A1) | 2011-07-01 | Bohannon et al. | Applicant |
| US2011/0189981(A1) | 2011-08-01 | Faith et al. | Applicant |
| US2011/0191152(A1) | 2011-08-01 | Schwartz | Applicant |
| US2011/0191161(A1) | 2011-08-01 | Dai | Applicant |
| US2011/0191237(A1) | 2011-08-01 | Faith et al. | Applicant |
| US2011/0202416(A1) | 2011-08-01 | Buer et al. | Applicant |
| US2011/0238517(A1) | 2011-09-01 | Ramalingam et al. | Applicant |
| US2011/0270618(A1) | 2011-11-01 | Banerjee et al. | Applicant |
| US2011/0289004(A1) | 2011-11-01 | Prakash et al. | Applicant |
| US2011/0302016(A1) | 2011-12-01 | Haddad | Applicant |
| US2012/0010931(A1) | 2012-01-01 | Mehra et al. | Applicant |
| US2012/0010938(A1) | 2012-01-01 | Standley et al. | Applicant |
| US2012/0185317(A1) | 2012-07-01 | Wong | Applicant |
| US2012/0259722(A1) | 2012-10-01 | Mikurak | Applicant |
| US2012/0323703(A1) | 2012-12-01 | Hillier | Applicant |
| JP2000134147 | 2000-05-01 | Applicant | |
| JP2001222593(A) | 2001-08-01 | Applicant | |
| JP2001357337(A) | 2001-12-01 | Applicant | |
| JP2002175354(A) | 2002-06-01 | Applicant | |
| JP2002288502(A) | 2002-10-01 | Applicant | |
| JP2003022481(A) | 2003-01-01 | Applicant | |
| JP2003090730 | 2003-03-01 | Applicant | |
| JP2004341684(A) | 2004-12-01 | Applicant | |
| JP2006164189 | 2006-06-01 | Applicant | |
| JP2007522564 | 2007-08-01 | Applicant | |
| JP2009205684 | 2009-09-01 | Applicant | |
| JP2009282618 | 2009-12-01 | Applicant | |
| JP2012510681 | 2012-05-01 | Applicant | |
| JP2012529085 | 2012-11-01 | Applicant | |
| WO2010065235 | 2010-06-01 | Applicant | |
| WO2010138891 | 2010-12-01 | Applicant |
Non-Patent Literature (68)
- 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.Applicant
- 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.Applicant
- “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.Applicant
- 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.Applicant
- “MGM Grand, MacroView Labs—Mobile App Developers for iPhone, Android, Blackberries”, retrieved on Jan. 13, 2011 at <<http://www.macroviewlabs.com/mgmgrand>>, 5 pages.Applicant
- PCT Search Report mailed on May 12, 2011 for PCT Application No. PCT/US11/28825.Applicant
- 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.Applicant
- Prabhu, “Transaction Processing in Mobile Database System”, University of Missouri—Kansas City, 2006. vol. 67/12—B of Dissertation Abstracts International, 1 page.Applicant
- U.S. Appl. No. 61/142,100, Garrett.Applicant
- Final Office Action for U.S. Appl. No. 12/820,743, mailed on Jun. 21, 2012, Harsha Ramalingam et al, “Hierarchical Device Relationships for Geolocation-Based Transactions”, 24 pages.Applicant
- Non-Final Office Action for U.S. Appl. No. 13/371,038, mailed on Jul. 23, 2012, Harsha Ramalingam et al., 8 pages.Applicant
- Final Office Action for U.S. Appl. No. 12/820,705, mailed on Jul. 25, 2012, Harsha Ramalingam et al., “Transaction Completion Based on Geolocation Arrival”, 16 pages.Applicant
- Non-Final Office Action for U.S. Appl. No. 12/820,854, mailed on Jul. 27, 2012, Harsha Ramalingam et al., “Location-Based Marketing to Mobile Devices”, 16 pages.Applicant
- Non-Final Office Action for U.S. Appl. No. 12/820,913, mailed on Jul. 31, 2012, Harsha Ramalingam et al. “Transaction Bootstrapping to Create Relationships”, 14 pages.Applicant
- Non-Final Office Action for U.S. Appl. No. 13/468,714, mailed on Aug. 16, 2012, Harsha Ramalingam, “Mobile Payments Using Point-of-sale Infrastructure”, 29 pages.Applicant
- Non-Final Office Action for U.S. Appl. No. 12/976,533, mailed on Aug. 16, 2012, Harsha Ramalingam, “Mobile Payments Using Point-of-sale Infrastructure”, 38 pages.Applicant
- U.S. Appl. No. 12/976,533, filed Dec. 22, 2010, Harsha Ramalingam, “Mobile Payments Using Point-of-sale Infrastructure”.Applicant
- U.S. Appl. No. 13/027,913, filed Feb. 15, 2011, Harsha Ramalingam, et al., “User Profile and Geolocation for Efficient Transactions”.Applicant
- Dictionary.com, “Broadcast”, retrived at <<http://dictionary.reference.com/browse/broadcast>> on Feb. 6, 2012, 4 pages.Applicant
- Non-Final Office Action for U.S. Appl. No. 12/820,705, mailed on Feb. 27, 2012, Harsha Ramalingam et al., “Transaction Completion Based on Geolocation Arrival”, 15 pages.Applicant
- Non-Final Office Aciotn for U.S. Appl. No. 12/820,743, mailed on Feb. 27, 2012, Harsha Ramalingam et al, “Hierarchical Device Relationships for Geolocation-Based Transactions”, 18 pages.Applicant
- WebWire, “BooksOnBoard Adds Google Checkout, Offers Discount on Google Checkout Purchases”, Jun. 11, 2008, retrived from Google News Apr. 6, 2012, pp. 1-2.Applicant
- U.S. Appl. No. 13/371,038, filed Feb. 10, 2012, Harsha Ramalingam et al., “User Profile and Geolocation for Efficient Transactions”.Applicant
- Non-Final Office Action for U.S. Appl. No. 12/820,816, mailed on Dec. 31, 2012, Harsha Ramalingham et al., “Mobile Device Security”, 10 pages.Applicant
- Office action for U.S. Appl. No. 12/820,913, mailed on Feb. 8, 2013, Ramalingam et al., “Transaction Bootstrapping to Create Relationships”, 19 pages.Applicant
- Office action for U.S. Appl. No. 12/820,854, mailed on Apr. 10, 2013, Ramalingam et al., “Location-Based Marketing to Mobile Devices”, 22 pages.Applicant
- Office action for U.S. Appl. No. 13/468,714, mailed on Apr. 11, 2013, Ramalingam, “Mobile Payments Using Point-of-sale Infrastructure”, 35 pages.Applicant
- Office action for U.S. Appl. No. 12/976,533, mailed on Apr. 12, 2013, Ramalingam, “Mobile Payments Using Point-of-sale Infrastructure”, 44 pages.Applicant
- Office action for U.S. Appl. No. 12/820,949, mailed on Nov. 9, 2012, Ramalingam et al, “Transaction Tracking and Incentives”, 11 pages.Applicant
- Non-Final Office Action for U.S. Appl. No. 12/894,287, mailed on Dec. 5, 2012, Michael Carr et al., “Location-based Coupons and Mobile Devices”, 8 pages.Applicant
- Definition: Purchase, retrieved on Mar. 31, 2014 at <<dictionary.reference.com/browse/purchase?s=t>>, World English Dictionary, 2009, 2 pages.Applicant
- Extended European Search Report mailed Feb. 26, 2014 for European patent application No. 11759940.7, 11 pages.Applicant
- Office Action from U.S. Appl. No. 12/894,287, mailed on Mar. 27, 2014, Michael Carr, “Location-based Coupons and Mobile Devices”, 17 pages.Applicant
- Final Office Action for U.S. Appl. No. 12/820,743, mailed on Apr. 10, 2014, Harsha Ramalingam, “Hierarchical Device Relationships for Geolocation-Based Transactions”, 24 pages.Applicant
- Office Action for U.S. Appl. No. 12/820,705, mailed on Apr. 2, 2014, Harsha Ramalingam, “Transaction Completion Based on Geolocation Arrival”, 11 pages.Applicant
- Final Office Action for U.S. Appl. No. 12/820,913, mailed on Apr. 9, 2014, Harsha Ramalingam, “Transaction Bootstrapping to Create Relationships”, 21 pages.Applicant
- Office Action for U.S. Appl. No. 12/820,854, mailed on May 9, 2014, Harsha Ramalingam, “Location-Based Marketing to Mobile Devices”, 25 pages.Applicant
- Office action for U.S. Appl. No. 13/111,920, mailed on Jun. 20, 2014, Doane et al., “Location-Based Mobile Advertising”, 31 pages.Applicant
- Office action for U.S. Appl. No. 13/052,930, mailed on Jul. 1, 2014, Hart et al., “Advertisement Service”, 29 pages.Applicant
- Translated copy of the Japanese Office Action mailed Jul. 1, 2014 for Japanese patent application No. 2014-094659, a counterpart foreign application of US patent No. 8,140,403, 4 pages.Applicant
- Translated copy of the Japanese Office Action mailed Jul. 29, 2014 for Japanese patent application No. 2013-553675, a counterpart foreign application of U.S. Appl. No. 13/052,930, 9 pages.Applicant
- Office action for U.S. Appl. No. 12/820,949, mailed on Jun. 20, 2013, Ramalingam et al, “Transaction Tracking and Incentives”, 20 pages.Applicant
- Office action for U.S. Appl. No. 12/820,705, mailed on Jul. 12, 2013, Ramalingam et al, “Transaction Completion Based on Geolocation Arrival”, 16 pages.Applicant
- Office action for U.S. Appl. No. 12/894,287, mailed on Jul. 16, 2013, Can et al., “Location-based Coupons and Mobile Devices”, 18 pages.Applicant
- U.S. Appl. No. 13/052,930, filed Mar. 21, 2011, Hart et al., “Advertisement Service”.Applicant
- Final Office Action for U.S. Appl. No. 12/820,949, mailed on Jan. 6, 2014, Harsha Ramalingam, “Transaction Tracking and Incentives”, 22 pages.Applicant
- Translated copy of the Japanese Office Action mailed Dec. 10, 2013 for Japanese patent application No. 2013-500205, a counterpart foreign application of US patent No. 8,140,403, 9 pages.Applicant
- Non-Final Office Action for U.S. Appl. No. 13/052,930, mailed on Jan. 2, 2013, Gregory M. Hart et al., “Advertisement Service”, 19 pages.Applicant
- Office Action for U.S. Appl. No. 13/111,920, mailed on Oct. 2, 2013, Andrew J. Doane, “Location-Based Mobile Advertising”, 28 pages.Applicant
- Office Action for U.S. Appl. No. 13/052,930, mailed on Dec. 16, 2013, Gregory M. Hart, “Advertisement Service”, 28 pages.Applicant
- Office action for U.S. Appl. No. 12/820,743, mailed on Dec. 27, 2013, Ramalingam et al., “Hierarchical Device Relationships for Geolocation-Based Transactions”, 26 pages.Applicant
- Office action for U.S. Appl. No. 13/052,930, mailed on Jul. 8, 2013, Hart et al., “Advertisement Service”, 20 pages.Applicant
- PCT Search Report for PCT application No. PCT/US12/29798, mailed Jul. 5, 2012 , 7 pages.Applicant
- Final Office Action for U.S. Appl. No. 12/820,854, mailed on Oct. 22, 2013, Harsha Ramalingam, “Location-Based Marketing to Mobile Devices”, 21 pages.Applicant
- Final Office Action for U.S. Appl. No. 12/820,705, mailed on Dec. 5, 2013, Harsha Ramalingam, “Transaction Completion Based on Geolocation Arrival”, 14 pages.Applicant
- Office Action for U.S. Appl. No. 12/820,913, mailed on Dec. 4, 2013, Harsha Ramalingam, “Transaction Bootstrapping to Create Relationships”, 24 pages.Applicant
- Canadian Office Action mailed Aug. 29, 2014 for Canadian patent application No. 2794085, a counterpart foreign application of U.S. Appl. No. 12/820,672, 3 pages.Applicant
- Extended European Search Report mailed Oct. 31, 2014 for European Patent Application No. 12760316.5, 7 pages.Applicant
- Translated Copy of the Korean Office Action mailed 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.Applicant
- Office Action for U.S. Appl. No. 12/820,854, mailed on Nov. 5, 2014, Harsha Ramalingam, “Location-Based Marketing to Mobile Devices” , 23 pages.Applicant
- Office Action for U.S. Appl. No. 12/894,287, mailed on Dec. 4, 2014, Michael Carr, “Location-based Coupons and Mobile Devices”, 24 pages.Applicant
- Office action for U.S. Appl. No. 12/820,913, mailed on Sep. 11, 2014, Ramalingam et al., “Transaction Bootstrapping to Create Relationships”, 15 pages.Applicant
- Office action for U.S. Appl. No. 12/820,705, mailed on Sep. 2, 2014, Ramalingam et al., “Transaction Completion Based on Geolocation Arrival”, 12 pages.Applicant
- Final Office Action for U.S. Appl. No. 12/894,287, mailed on Apr. 9, 2015, Michael Carr, “Location-based Coupons and Mobile Devices”, 24 pages.Applicant
- Final Office Action for U.S. Appl. No. 12/820,913, mailed on Apr. 24, 2014, Harsha Ramalingam, “Transaction Bootstrapping to Create Relationships”, 12 pages.Applicant
- Office Action for U.S. Appl. No. 12/820,705, mailed on Apr. 17, 2015, Harsha Ramalingam, “Transaction Completion Based on Geolocation Arrival”, 23 pages.Applicant
- Office action for U.S. Appl. No. 12/820,743, mailed on Apr. 3, 2015, Ramalingam et al., “Hierarchical Device Relationships for Geolocation-Based Transactions”, 21 pages.Applicant
- Office Action from the Canadian Patent Office for Canadian patent application No. 2830268, a counterpart foreign application of U.S. Appl. No. 13/052,930, mailed Apr. 7, 2015, 5 pages.Applicant