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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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
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
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.
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.
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.
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.
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.
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).
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
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.
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.
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.
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.
The user information 120 may provide separate data associated with each of the user identifiers 208-306 shown in
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.
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.
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.
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
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.
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.
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.
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.
The server(s) 118 may also have access to the user information 120 as shown in
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.
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
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
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
At operation 706, a geolocation of the mobile device is determined. The geolocation may be determined by the location sensor 230 shown in
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
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.
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
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.
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
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.
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.
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.
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.
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.
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
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
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.
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.
At operation 806, the geolocation of the mobile device is determined. The geolocation may be determined by the location sensor 230 shown in
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.
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.
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
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
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
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.
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.
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.
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
At time 1, the mobile device has an electronic document 212 stored in memory as shown in
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
Number | Name | Date | Kind |
---|---|---|---|
5914472 | Foladare et al. | Jun 1999 | A |
6108650 | Musk et al. | Aug 2000 | A |
6343279 | Bissonette et al. | Jan 2002 | B1 |
6505046 | Baker | Jan 2003 | B1 |
6738749 | Chasko | May 2004 | B1 |
6756879 | Shuster | Jun 2004 | B2 |
7392534 | Lu et al. | Jun 2008 | B2 |
7434723 | White et al. | Oct 2008 | B1 |
7657489 | Stambaugh | Feb 2010 | B2 |
7725390 | Plant | May 2010 | B2 |
7739197 | Jambunathan et al. | Jun 2010 | B2 |
7788281 | Cole et al. | Aug 2010 | B2 |
7813717 | Huotari et al. | Oct 2010 | B2 |
7840222 | Hampel et al. | Nov 2010 | B2 |
7853786 | Fultz et al. | Dec 2010 | B1 |
7873708 | Durand et al. | Jan 2011 | B2 |
7900847 | Lindahl et al. | Mar 2011 | B2 |
8050991 | Popovic et al. | Nov 2011 | B2 |
8099109 | Altman et al. | Jan 2012 | B2 |
8116731 | Buhrmann et al. | Feb 2012 | B2 |
8135624 | Ramalingam et al. | Mar 2012 | B1 |
8213898 | Choti et al. | Jul 2012 | B2 |
8255698 | Li et al. | Aug 2012 | B2 |
8326767 | Ramanujan et al. | Dec 2012 | B1 |
8521131 | Ramalingam et al. | Aug 2013 | B1 |
8606322 | Sabol | Dec 2013 | B2 |
8744488 | Cousins et al. | Jun 2014 | B2 |
8849310 | Fan et al. | Sep 2014 | B2 |
20010025257 | Sato | Sep 2001 | A1 |
20010051911 | Marks et al. | Dec 2001 | A1 |
20020046116 | Hohle et al. | Apr 2002 | A1 |
20020065713 | Awada et al. | May 2002 | A1 |
20020077876 | O'Meara et al. | Jun 2002 | A1 |
20020091568 | Kraft et al. | Jul 2002 | A1 |
20020123938 | Yu et al. | Sep 2002 | A1 |
20020143638 | August et al. | Oct 2002 | A1 |
20030159066 | Staw et al. | Aug 2003 | A1 |
20030208386 | Brondrup | Nov 2003 | A1 |
20030208684 | Camacho et al. | Nov 2003 | A1 |
20030212609 | Blair et al. | Nov 2003 | A1 |
20030220835 | Barnes, Jr. | Nov 2003 | A1 |
20040002897 | Vishik | Jan 2004 | A1 |
20040019563 | Sines et al. | Jan 2004 | A1 |
20040056101 | Barkan et al. | Mar 2004 | A1 |
20040093620 | Iino et al. | May 2004 | A1 |
20050004840 | Wanninger | Jan 2005 | A1 |
20050221843 | Friedman et al. | Oct 2005 | A1 |
20050228719 | Roberts et al. | Oct 2005 | A1 |
20050234771 | Register et al. | Oct 2005 | A1 |
20050240472 | Postrel | Oct 2005 | A1 |
20050267812 | Jensen et al. | Dec 2005 | A1 |
20060047576 | Aaltonen et al. | Mar 2006 | A1 |
20060111955 | Winter et al. | May 2006 | A1 |
20060235795 | Johnson et al. | Oct 2006 | A1 |
20060235796 | Johnson et al. | Oct 2006 | A1 |
20060242017 | Libes et al. | Oct 2006 | A1 |
20070084913 | Weston | Apr 2007 | A1 |
20070088610 | Chen | Apr 2007 | A1 |
20070118426 | Barnes, Jr. | May 2007 | A1 |
20070136140 | Smith, Jr. | Jun 2007 | A1 |
20070291710 | Fadell | Dec 2007 | A1 |
20080004949 | Flake et al. | Jan 2008 | A1 |
20080005104 | Flake et al. | Jan 2008 | A1 |
20080010121 | McIntosh | Jan 2008 | A1 |
20080040233 | Wildman et al. | Feb 2008 | A1 |
20080040274 | Uzo | Feb 2008 | A1 |
20080086767 | Kulkarni et al. | Apr 2008 | A1 |
20080140522 | Tutone | Jun 2008 | A1 |
20080154765 | Wolfe | Jun 2008 | A1 |
20080154847 | Chellapilla et al. | Jun 2008 | A1 |
20080167991 | Carlson et al. | Jul 2008 | A1 |
20080183576 | Kim et al. | Jul 2008 | A1 |
20080201226 | Carlson et al. | Aug 2008 | A1 |
20080208739 | Phillips | Aug 2008 | A1 |
20080215475 | Ramer et al. | Sep 2008 | A1 |
20080221997 | Wolfe | Sep 2008 | A1 |
20080228600 | Treyz et al. | Sep 2008 | A1 |
20080262928 | Michaelis | Oct 2008 | A1 |
20080268868 | Maitland | Oct 2008 | A1 |
20080275768 | Berman et al. | Nov 2008 | A1 |
20080281677 | Toms et al. | Nov 2008 | A1 |
20080281702 | Kirkwood | Nov 2008 | A1 |
20080318559 | Porco | Dec 2008 | A1 |
20090006203 | Fordyce, III et al. | Jan 2009 | A1 |
20090024700 | Garg et al. | Jan 2009 | A1 |
20090030779 | Tollinger et al. | Jan 2009 | A1 |
20090061884 | Rajan et al. | Mar 2009 | A1 |
20090076896 | DeWitt et al. | Mar 2009 | A1 |
20090076925 | DeWitt et al. | Mar 2009 | A1 |
20090125380 | Otto et al. | May 2009 | A1 |
20090125396 | Otto et al. | May 2009 | A1 |
20090132417 | Scipioni et al. | May 2009 | A1 |
20090138302 | Breznik et al. | May 2009 | A1 |
20090143966 | Jacobson et al. | Jun 2009 | A1 |
20090150218 | Brunner et al. | Jun 2009 | A1 |
20090152343 | Carter et al. | Jun 2009 | A1 |
20090157547 | Ruckart | Jun 2009 | A1 |
20090187463 | DaCosta | Jul 2009 | A1 |
20090187466 | Carter et al. | Jul 2009 | A1 |
20090187488 | Shamilian | Jul 2009 | A1 |
20090187492 | Hammad et al. | Jul 2009 | A1 |
20090198607 | Badger et al. | Aug 2009 | A1 |
20090216646 | Seven et al. | Aug 2009 | A1 |
20090222346 | Greene et al. | Sep 2009 | A1 |
20090228325 | Simmons et al. | Sep 2009 | A1 |
20090240582 | Sheldon-Neal et al. | Sep 2009 | A1 |
20090240622 | Zandonadi | Sep 2009 | A1 |
20090271275 | Regmi et al. | Oct 2009 | A1 |
20090281945 | Shakkarwar | Nov 2009 | A1 |
20090292642 | Han | Nov 2009 | A1 |
20090299857 | Brubaker | Dec 2009 | A1 |
20090327135 | Nguyen et al. | Dec 2009 | A1 |
20090327151 | Carlson et al. | Dec 2009 | A1 |
20100004997 | Mehta et al. | Jan 2010 | A1 |
20100006641 | Boutcher et al. | Jan 2010 | A1 |
20100006642 | Boutcher et al. | Jan 2010 | A1 |
20100030651 | Matotek et al. | Feb 2010 | A1 |
20100041419 | Svendsen et al. | Feb 2010 | A1 |
20100042421 | Bai et al. | Feb 2010 | A1 |
20100049615 | Rose et al. | Feb 2010 | A1 |
20100057530 | Parivash et al. | Mar 2010 | A1 |
20100063891 | Townsend et al. | Mar 2010 | A1 |
20100070334 | Monteverde | Mar 2010 | A1 |
20100070365 | Siotia et al. | Mar 2010 | A1 |
20100076829 | Bishop | Mar 2010 | A1 |
20100076849 | Bishop | Mar 2010 | A1 |
20100077036 | DeLuca et al. | Mar 2010 | A1 |
20100082420 | Trifiletti et al. | Apr 2010 | A1 |
20100082445 | Hodge et al. | Apr 2010 | A1 |
20100088188 | Kumar et al. | Apr 2010 | A1 |
20100100454 | Sines et al. | Apr 2010 | A1 |
20100106611 | Paulsen et al. | Apr 2010 | A1 |
20100121717 | Chen | May 2010 | A1 |
20100138294 | Bussmann et al. | Jun 2010 | A1 |
20100138344 | Wong et al. | Jun 2010 | A1 |
20100145723 | Hudson et al. | Jun 2010 | A1 |
20100145778 | Fordyce, III et al. | Jun 2010 | A1 |
20100146607 | Piepenbrink et al. | Jun 2010 | A1 |
20100156933 | Jones et al. | Jun 2010 | A1 |
20100169179 | Ramer et al. | Jul 2010 | A1 |
20100190510 | Maranhas et al. | Jul 2010 | A1 |
20100191551 | Drance et al. | Jul 2010 | A1 |
20100191578 | Tran et al. | Jul 2010 | A1 |
20100192230 | Steeves et al. | Jul 2010 | A1 |
20100205167 | Tunstall-Pedoe et al. | Aug 2010 | A1 |
20100217525 | King et al. | Aug 2010 | A1 |
20100241495 | Maniyar et al. | Sep 2010 | A1 |
20100241496 | Gupta et al. | Sep 2010 | A1 |
20100250368 | Porco | Sep 2010 | A1 |
20100260388 | Garrett et al. | Oct 2010 | A1 |
20100262449 | Monteforte et al. | Oct 2010 | A1 |
20100274655 | Postrel | Oct 2010 | A1 |
20100293065 | Brody et al. | Nov 2010 | A1 |
20100306099 | Hirson et al. | Dec 2010 | A1 |
20100312630 | Krutchik et al. | Dec 2010 | A1 |
20100312645 | Niejadlik et al. | Dec 2010 | A1 |
20100312646 | Gupta et al. | Dec 2010 | A1 |
20100323716 | Jaffri | Dec 2010 | A1 |
20100324977 | Dragt | Dec 2010 | A1 |
20100332339 | Patel et al. | Dec 2010 | A1 |
20110010238 | Postrel | Jan 2011 | A1 |
20110015987 | Chakraborty et al. | Jan 2011 | A1 |
20110022424 | VonDerheide | Jan 2011 | A1 |
20110022483 | Hammad | Jan 2011 | A1 |
20110022517 | Hammad | Jan 2011 | A1 |
20110029403 | Xu | Feb 2011 | A1 |
20110053559 | Klein | Mar 2011 | A1 |
20110055005 | Lang | Mar 2011 | A1 |
20110057027 | Grossman et al. | Mar 2011 | A1 |
20110060640 | Thompson et al. | Mar 2011 | A1 |
20110065419 | Book et al. | Mar 2011 | A1 |
20110082735 | Kannan et al. | Apr 2011 | A1 |
20110087430 | Boss et al. | Apr 2011 | A1 |
20110093318 | Guday et al. | Apr 2011 | A1 |
20110106613 | Felt et al. | May 2011 | A1 |
20110112892 | Tarantino | May 2011 | A1 |
20110131627 | Abendroth et al. | Jun 2011 | A1 |
20110137804 | Peterson | Jun 2011 | A1 |
20110140841 | Bona et al. | Jun 2011 | A1 |
20110184793 | Bohannon et al. | Jul 2011 | A1 |
20110189981 | Faith et al. | Aug 2011 | A1 |
20110191152 | Schwartz | Aug 2011 | A1 |
20110191161 | Dai | Aug 2011 | A1 |
20110191237 | Faith et al. | Aug 2011 | A1 |
20110202416 | Buer et al. | Aug 2011 | A1 |
20110238517 | Ramalingam et al. | Sep 2011 | A1 |
20110270618 | Banerjee et al. | Nov 2011 | A1 |
20110289004 | Prakash et al. | Nov 2011 | A1 |
20110302016 | Haddad | Dec 2011 | A1 |
20120010931 | Mehra et al. | Jan 2012 | A1 |
20120010938 | Standley et al. | Jan 2012 | A1 |
20120185317 | Wong | Jul 2012 | A1 |
20120259722 | Mikurak | Oct 2012 | A1 |
20120323703 | Hillier | Dec 2012 | A1 |
Number | Date | Country |
---|---|---|
2000134147 | May 2000 | JP |
2001222593 | Aug 2001 | JP |
2001357337 | Dec 2001 | JP |
2002175354 | Jun 2002 | JP |
2002288502 | Oct 2002 | JP |
2003022481 | Jan 2003 | JP |
2003090730 | Mar 2003 | JP |
2004341684 | Dec 2004 | JP |
2006164189 | Jun 2006 | JP |
2007522564 | Aug 2007 | JP |
2009205684 | Sep 2009 | JP |
2009282618 | Dec 2009 | JP |
2012510681 | May 2012 | JP |
2012529085 | Nov 2012 | JP |
WO2010065235 | Jun 2010 | WO |
WO2010138891 | Dec 2010 | WO |
Entry |
---|
Collins, “Smartphones to be used as Hotel Room Keys”, Telegraph Media Group Limited, May 25, 2010, Retrieved on Jun. 2, 2010 at <<http://www.telegraph.co.uk/travel/hotels/7762522/Smartphones-to-be-used-as-hotel-room-keys.html>> pp. 1-2. |
Deleon, “Holiday Inn to Trial Mobile-as-room-key Program Next Month”, TechCrunch, May 25, 2010, Retrieved on Jun. 2, 2010 at <<http://www.mobilecrunch.com/2010/05/25/holiday-inn-to-trial-mobile-as-room-key-program-next-month/>> 1 pg. |
“Placecast Raises $3 Million for Location-Based Mobile Marketing Technology”, The Good NET Guide, Retrieved on Mar. 25, 2010 at <<http://thegoodnetguide.com/03/placecast-raises-3-million-for-location-based-mobile-marketing-technology/>>, 1 pg. |
Starbucks Card Mobile App, “Using Your Starbucks Card is Now Even Faster and Easier With the Starbucks Card Mobile App”, Retrieved on Apr. 22, 2010 at <<http://www.starbucks.com/coffeehouse/mobile-apps/starbucks-card-mobile>>, pp. 1-2. |
“MGM Grand, MacroView Labs—Mobile App Developers for iPhone, Android, Blackberries”, retrieved on Jan. 13, 2011 at <<http://www.macroviewlabs.com/mgmgrand>>, 5 pages. |
PCT Search Report mailed on May 12, 2011 for PCT Application No. PCT/US11/28825. |
Alqerem et al., “Location Dependent Transaction for Mobile Environment”, International Conference on Information and Communication Technologies: From Theory to Applications, Piscataway, NJ, 2006, 2 pages. |
Prabhu, “Transaction Processing in Mobile Database System”, University of Missouri—Kansas City, 2006. vol. 67/12—B of Dissertation Abstracts International, 1 page. |
U.S. Appl. No. 61/142,100, Garrett. |
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. |
Non-Final Office Action for U.S. Appl. No. 13/371,038, mailed on Jul. 23, 2012, Harsha Ramalingam et al., 8 pages. |
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. |
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. |
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. |
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. |
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. |
U.S. Appl. No. 12/976,533, filed Dec. 22, 2010, Harsha Ramalingam, “Mobile Payments Using Point-of-sale Infrastructure”. |
U.S. Appl. No. 13/027,913, filed Feb. 15, 2011, Harsha Ramalingam, et al., “User Profile and Geolocation for Efficient Transactions”. |
Dictionary.com, “Broadcast”, retrived at <<http://dictionary.reference.com/browse/broadcast>> on Feb. 6, 2012, 4 pages. |
Non-Final Office Action for U.S. Appl. No. 12/820,705, mailed on Feb. 27, 2012, Harsha Ramalingam et al., “Transaction Completion Based on Geolocation Arrival”, 15 pages. |
Non-Final Office Aciotn for U.S. Appl. No. 12/820,743, mailed on Feb. 27, 2012, Harsha Ramalingam et al, “Hierarchical Device Relationships for Geolocation-Based Transactions”, 18 pages. |
WebWire, “BooksOnBoard Adds Google Checkout, Offers Discount on Google Checkout Purchases”, Jun. 11, 2008, retrived from Google News Apr. 6, 2012, pp. 1-2. |
U.S. Appl. No. 13/371,038, filed Feb. 10, 2012, Harsha Ramalingam et al., “User Profile and Geolocation for Efficient Transactions”. |
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. |
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. |
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. |
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. |
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. |
Office action for U.S. Appl. No. 12/820,949, mailed on Nov. 9, 2012, Ramalingam et al, “Transaction Tracking and Incentives”, 11 pages. |
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. |
Definition: Purchase, retrieved on Mar. 31, 2014 at <<dictionary.reference.com/browse/purchase?s=t>>, World English Dictionary, 2009, 2 pages. |
Extended European Search Report mailed Feb. 26, 2014 for European patent application No. 11759940.7, 11 pages. |
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. |
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. |
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. |
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. |
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. |
Office action for U.S. Appl. No. 13/111,920, mailed on Jun. 20, 2014, Doane et al., “Location-Based Mobile Advertising”, 31 pages. |
Office action for U.S. Appl. No. 13/052,930, mailed on Jul. 1, 2014, Hart et al., “Advertisement Service”, 29 pages. |
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. |
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. |
Office action for U.S. Appl. No. 12/820,949, mailed on Jun. 20, 2013, Ramalingam et al, “Transaction Tracking and Incentives”, 20 pages. |
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. |
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. |
U.S. Appl. No. 13/052,930, filed Mar. 21, 2011, Hart et al., “Advertisement Service”. |
Final Office Action for U.S. Appl. No. 12/820,949, mailed on Jan. 6, 2014, Harsha Ramalingam, “Transaction Tracking and Incentives”, 22 pages. |
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. |
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. |
Office Action for U.S. Appl. No. 13/111,920, mailed on Oct. 2, 2013, Andrew J. Doane, “Location-Based Mobile Advertising”, 28 pages. |
Office Action for U.S. Appl. No. 13/052,930, mailed on Dec. 16, 2013, Gregory M. Hart, “Advertisement Service”, 28 pages. |
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. |
Office action for U.S. Appl. No. 13/052,930, mailed on Jul. 8, 2013, Hart et al., “Advertisement Service”, 20 pages. |
PCT Search Report for PCT application No. PCT/US12/29798, mailed Jul. 5, 2012 , 7 pages. |
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. |
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. |
Office Action for U.S. Appl. No. 12/820,913, mailed on Dec. 4, 2013, Harsha Ramalingam, “Transaction Bootstrapping to Create Relationships”, 24 pages. |
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. |
Extended European Search Report mailed Oct. 31, 2014 for European Patent Application No. 12760316.5, 7 pages. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Number | Date | Country | |
---|---|---|---|
20110238474 A1 | Sep 2011 | US |
Number | Date | Country | |
---|---|---|---|
61351743 | Jun 2010 | US | |
61316527 | Mar 2010 | US |