(12) INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY(PCT)
`MACARAA
`
`(19) World Intellectual Property Organization
`International Bureau
`
`29 September 2011 (29.09.2011)
`
`(43) International Publication Date
`
`(10) International Publication Number
`WO 2011/119407 Al
`
`(51) International Patent Classification:
`G06Q 20/00 (2006.01)
`
`(21) International Application Number:
`PCT/US201 1/028825
`
`(22) International Filing Date:
`
`17 March 2011 (17.03.2011)
`English
`English
`
`(25) Filing Language:
`(26) Publication Language:
`.
`(30) Priority Data:
`61/316,52
`61/351,743
`12/820,672
`12/820,705
`12/894,287
`12/894,323
`
`23 March 2010 (23.03.2010)
`4 June 2010 (04.06.2010)
`22 June 2010 (22.06.2010)
`22 June 2010 (22.06.2010)
`30 September 2010 (30.09.2010)
`30 September 2010 (30.09.2010)
`
`US
`US
`US
`US
`US
`US
`
`CHUANG, James [US/US]; 410 Terry Avenue North,
`Seattle, WA 98109-5210 (US).
`
`(74) Agents: KIEM, Benjamin, A. et al.; Lee & Hayes,
`PLLC, 601 W.Riverside Ave, Suite 1400, Spokane, WA
`99201 (US).
`
`(81) Designated States (unless otherwise indicated, for every
`kind of national protection available): AE, AG, AL, AM,
`AO, AT, AU, AZ, BA, BB, BG, BH, BR, BW, BY, BZ,
`CA, CH, CL, CN, CO, CR, CU, CZ, DE, DK, DM, DO,
`DZ, EC, EE, EG, ES, FI, GB, GD, GE, GH, GM, GT,
`HN,HR, HU,ID,IL,IN, IS, JP, KE, KG, KM, KN,KP,
`KR. KZ, LA. LC, LK, LR, LS, LT, LU, LY, MA, Mb,
`ME, MG, MK, MN, MW, MX, MY, MZ, NA, NG, NL
`NO, NZ, OM,PE, PG, PH, PL, PT, RO, RS, RU, SC, SD,
`SE, SG, SK, SL, SM, ST, SV, SY, TH, TI, T™, TN, TR,
`TT, TZ, UA, UG, US, UZ, VC, VN, ZA, ZM, ZW.
`
`(84) Designated States (unless otherwise indicated, for every
`.
`kind of regional protection available): ARIPO (BW, GH,
`(71) Applicant (for all designated States except US): AMA-
`GM, KE, LR, LS, MW, MZ, NA, SD, SL, SZ, TZ, UG,
`ZON TECHNOLOGIESINC. [US/US]; PO Box 8102,
`ZM,ZW), Eurasian (AM, AZ, BY, KG, KZ, MD, RU,TJ,
`Reno, NV89507 (US).
`TM), European (AL, AT, BE, BG, CH, CY, CZ, DE, DK,
`(72) Inventors; and
`EE, ES, FI, FR, GB, GR, HR, HU,IE, IS, IT, LT, LU,
`(75)
`Inventors/Applicants (/or US only); RAMALINGAM,
`LV, MC, MK, MT, NL, NO,PL, PT, RO, RS, SE, SL, SK,
`Harsha [US/US]; 410 Terry Avenue North, Seattle, WA
`SM,TR), OAPI(BF, BJ, CF, CG, Cl, CM, GA, GN, GQ,
`98109-5210 (US). WALSH, Paul [IE/US]; 410 Terry
`GW, ML, MR, NE, SN, TD, TG).
`Avenue North, Seattle, WA 98109-5210 (US). CARR,
`Michael [US/US]; 410 Terry Avenue North, Seattle, WA Ppuyblished:
`,
`-
`.
`98109-5210 (US). LATHIA, Bhavnish [IN/US]; 410
`cas
`Terry Avenue North, Seattle, WA 98109-5210 (US). — with international search report (Art. 21(3))
`
`(54) Title: USER PROFILE AND GEOLOCATION FOR EFFICIENT TRANSACTIONS
`
`were
`
`pel
`
`AD
`DATABASE
`126
`
`A
`
`
`RADIO ANTENNA.114
`\,
`
`‘
`
`SATELLITE
`112
`\
`
`7
`
`°
`
`Ss
`ae SERVER(S)
`118
`
`‘ a & Mercian
`
`SeRVER
`18
`
`MOBILE
`
`¢
`
`120
`
`’
`
`PoINT-OF-
`SALE DEVICE
`
`MERCHANT 103
`
` Fig. 1
`
`(57) Abstract: Techniques for providing friction-free transactions using geolocation and user identifiers are described herein.
`These techniques may ascertain a user's location based on a location of a mobile device. A transaction between the user and a mer-
`chant may be completed with zero or minimal input from the user based on the geolocation of the mobile device and the user iden-
`lifiers. In some implementations, a transaction initiated earlier is completed when the mobile device arrives at the merchant. Addi-
`tionally, a parent-child or similar relationship may be established between multiple devices. Security on the mobile device based
`may be provided by biometric identification and calculation of variance from regular movement patterns. Advertisements may be
`sent to the mobile device based on bids from merchants near to the mobile device. Promotions may be sent to the mobile device
`when more than a threshold numberof mobile devices are located at the same merchant.
`
`y~~
`a
`tt
`“00
`u
`
`
`‘ AUTHENTCATION|~>s.com i
`126
`a
`122
`ONLINE RETAILER
`ere
`. AN
`IKFORMATION
`
`
`
`
`
`
`
`©2011/119407Ad[IAMTTIMANUTAITATANTRAAAA
`
`

`

`WO 2011/119407
`
`PCT/US2011/028825
`
`USER PROFILE AND GEOLOCATION FOR EFFICIENT TRANSACTIONS
`
`RELATED APPLICATIONS
`
`[0001]
`
`This application claims the benefit of U.S. Provisional Application Nos. 61/316,527
`
`filed on March 23, 2010 and 61/351,743 filed on June 4, 2010 and U.S. Patent Application Nos.
`
`12/820,672 filed on June 22, 2010, 12/820,705 filed on June 22, 2010, 12/894,287 filed on
`
`September30, 2010, and 12/894,323 filed on September 30, 2010.
`
`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 maturingfield.
`
`[0003]
`
`Consumers are also becoming increasingly comfortable with virtual interactions, such
`
`as online shopping. However,
`
`in spite of the relative convenience of the virtual world, as
`
`opposed to the brick-and-mortar world, friction and sccurity concerns still limit adoption of
`
`virtual interactions. For example, remembering passwords and maintaining multiple accounts
`
`create friction in virtual-world interactions. Additionally,
`
`the anonymity and lack of direct
`
`interaction between the consumer and the merchant create potential
`
`security problems.
`
`Accordingly, content designed specifically for mobile computing devices that eliminates the
`
`friction of transactions and addresses securities concerns will have great value for consumers.
`
`[0004] 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 goodsor 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
`
`

`

`WO 2011/119407
`
`PCT/US2011/028825
`
`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
`
`[0005]
`
`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 numberfirst appears. The use of the same reference numbers in different figures
`
`indicates similaror identical items.
`
`[0006]
`
`Fig. 1 showsanillustrative architecture forfacilitating efficient transactions between a
`
`user of a mobile device, a merchant, and an onlineretailer.
`
`[0007]
`
`Fig. 2 shows the mobile device from Fig. 1 in greater detail.
`
`[0008]
`
`Fig. 3 showsthe server(s) from Fig. 1 in greater detail.
`
`[0009]
`
`Fig. 4 showsthe user information from Fig. 1 in greater detail.
`
`[0010]
`
`Fig. 5 shows the merchantprofiles, and advertisement database from Fig.
`
`1 in greater
`
`detail.
`
`[0011]
`
`Fig. 6 is a flow diagram of an illustrative process for automatically completing a
`
`transaction between a user of a mobile device and a merchant.
`
`[0012]
`
`Fig. 7 is a flow diagram of anillustrative process for completing a purchase by sharing
`
`information about the mobile device user with a merchant.
`
`[0013]
`
`Fig. 8 is a flow diagram ofan illustrative process for setting up a mobile device to
`
`conduct low-friction (e.g., zero-interaction or single-interaction) transactions with a merchant.
`
`[0014]
`
`Fig. 9 shows anillustrative architecture for a user of a mobile device to complete a
`
`transaction with a merchant uponarrival at the geolocation of the merchant.
`
`[0015]
`
`Fig. 10 is a flow diagram of anillustrative process for completing a transaction with a
`
`merchant when a mobile device and the user of the mobile device arrives at the merchant.
`
`[0016]
`
`Fig. 11 showsanillustrative architecture for conducting transactions between a child
`
`device and a merchant mediated by a parent device.
`
`[0017]
`
`Fig. 12 is a flow diagram of an illustrative process for completing a transaction
`
`between a child device and a merchant and transmitting an indication of the transaction to a
`
`parent device.
`
`Nw
`
`

`

`WO 2011/119407
`
`PCT/US2011/028825
`
`[0018]
`
`Fig. 13 showsanillustrative map of temporal-geo-locations of a mobile device during
`
`a workday of a user of the mobile device.
`
`[0019]
`
`Fig. 14 is a flow diagram ofanillustrative process for securing a mobile device based
`
`on variance from a map of temporal-geo-locations.
`
`[0020]
`
`Fig. 15 is a flow diagram ofan illustrative process for securing a mobile device based
`
`on biometric data.
`
`[0021]
`
`Fig. 16 showsan illustrative architecture for providing merchant advertisements or
`
`promotions to mobile devices at or near the merchant.
`
`[0022]
`
`Fig. 17 is a flow diagram ofan illustrative process for presenting advertisements on a
`
`mobile device based on bids submitted by merchants.
`
`[0023]
`
`Fig. 18 is a flow diagram of an illustrative process for providing a promotion to
`
`mobile devices when a numberof mobile devices at a merchant exceeds a threshold.
`
`[0024]
`
`Fig. 19 is a flow diagram ofan illustrative process for sending a coupon to a mobile
`
`device.
`
`[0025]
`
`Fig. 20 is a flow diagram of an illustrative process for providing coupons to mobile
`
`devices based on aggregate group behavior.
`
`[0026]
`
`Fig. 21 is a flow diagram ofanillustrative process for activating a coupon on a mobile
`
`device in response to a userlogin,
`
`[0027]
`
`Fig. 22 showsanillustrative 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.
`
`[0028]
`
`Figs. 23A and 23B are a flow diagram ofan illustrative process for notifying a user of
`
`a mobile device when a nearby merchant has a goodorservice for sale that is of interest to the
`user.
`
`[0029]
`
`Fig. 24 is a flow diagram of an illustrative process for recommending a nearby
`
`merchant and an online goodorservice to a user of a mobile device.
`
`[0030]
`
`Fig. 25 shows an illustrative timeline in which an electronic document on a mobile
`
`device contains a couponthat is actrvated when the mobile device is located at a merchant.
`
`[0031]
`
`Fig. 26 is a flow diagram of an illustrative process for activating a coupon in an
`
`electronic document when a mobile device is located a merchant.
`
`

`

`WO 2011/119407
`
`PCT/US2011/028825
`
`DETAILED DESCRIPTION
`
`[0032] Many activities are defined in whole or part by the location at which those activities
`
`occur.
`
`In some instances, the activity can be inferred with a high likelihood of accuracy based
`
`on the location alone. For example, a car at a tollbooth likely there to pay the toll and pass
`
`through, a person waiting by a boarding gate for an airplane is likely a ticket holderfor the flight,
`
`a person with a reservation at a hotel is likely going to check in to the hotel when he or she
`
`arrives in the lobby. At some locations many types of activities may be probable, but there are
`
`certain activities that will only happenat those locations. For example, many things may happen
`
`at the entry to a house, but arming or disarming a home security system will only be done at that
`
`location. A mobile computing device that is location-aware and can predict or infer what a user
`
`may be doingat that location will be able to automate someactivities and provide a high level of
`
`user convenience.
`
`[0033]
`
`This disclosure is directed to, in part, facilitating transactions based on geolocation
`
`and unique useridentification. For instance, these transactions may include electronic commerce
`
`transactions or any other type of transaction. Innovations in electronic commerce, such as a one-
`
`click shopping cart, have made the “Internet shopping” experience smoother and have reduced
`
`friction perceived by the user. For instance, clicking a single button to complete a purchase
`
`requires fewer steps than entering a password, address, credit card number, and such. The
`
`reduction of steps, clicks, and the like reduces the friction in a transaction. Commerce in the
`
`brick-and-mortar world causes the consumer even more friction than transactions in the
`
`electronic commerce world in some instances. For example, describing the item one wishes to
`
`purchase, prescnting payment to a cashicr, waiting for the cashicr to process the payment, and
`
`eventually receiving the desired item is an example of a typical, and relatively high-friction,
`
`brick-and-mortar transaction.
`
`[0034]
`
`Access to the World Wide Web from mobile devices provides a platform for
`
`electronic commerce similar to Internet shopping from a desktop computer. Mobile computing
`
`devices, such as mobile phones, are often carried with users throughout their daily interactions in
`
`the brick-and-mortar world. Many of these mobile computing devices are equipped with Global
`
`Positioning System (GPS) functionality to determine a location of the device, and thus, a
`
`location of the corresponding user. This disclosure combines the location awareness of mobile
`
`devices with the relatively lowerfriction transactions of electronic commerceto create a friction-
`
`free or,
`
`in some instances, a “zero-click” solution for interactions between consumers and
`
`merchants in the brick-and-mortar world. Unique user identification provides a thread thatties
`
`together information abouta particular uscr(c.g., credit card data), a link betwecn that uscr and a
`
`4
`
`

`

`WO 2011/119407
`
`PCT/US2011/028825
`
`given mobile computing device, and the relationship that user wishes to have with a given
`
`merchant(e.g., opt in to zero-click purchasing).
`
`[0035]
`
`A merchant may include any humanorlegal person such as, but not limited to, sellers
`
`of goods or services that engages in transactions with customers. For example, a government
`
`may be a merchant in the context of providing governmentservices, privileges, and/or rights.
`
`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 beclassified as an online retailer and as a merchant.
`
`[0036] Mobile devices that provide wireless connection to the Internet (or other network)
`
`allow access to what may becalled 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 ofthe
`
`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.
`
`[0037]
`
`This disclosure is directed to,
`
`in part, providing information to a user of a mobile
`
`devicc. For instance, if a good or service that the uscr may wish to purchase is for salc 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.
`
`[0038]
`
`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.
`5
`
`

`

`WO 2011/119407
`
`PCT/US2011/028825
`
`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 berelated to the
`
`goods and/or services sold by the merchantor related to goods and/orservices 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 computerat each of those locations.
`
`[0039]
`
`The described techniques may be implemented in a numberof 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
`
`[0040]
`
`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’) and.
`
`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
`
`advertisements, 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, customerpreferences, and the like.
`
`[0041]
`
`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 anotherentity (e.g., a server computer) to allow the otherentity 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
`
`

`

`WO 2011/119407
`
`PCT/US2011/028825
`
`(e.g., WiFi hotspot) or from a locator signal broadcast from a known location, such as at the
`
`merchant 106.
`
`[0042]
`
`The device 104 and the merchant 106 may connect
`
`to a network 116.
`
`The
`
`network 116 may include any one or combination of multiple different types of networks, such
`
`as cable networks, local area networks, personal area networks, wide area networks, the Internet,
`
`wireless networks, ad hoc networks, mesh networks, and/or the like.
`
`In some implementations
`
`the satellite 112 and/or the radio antenna 114 may provide network connectivity to the mobile
`
`device 104 as well as provide geolocation. For example, the radio antenna 114 may provide
`
`network access
`
`to the mobile
`
`device
`
`104
`
`according to the
`
`International Mobile
`
`Telecommunications-2000
`
`standards
`
`(“3G network”)
`
`or
`
`the
`
`International Mobile
`
`Telecommunications Advanced standards (“4G network”). Other implementations may include
`
`one source of geolocation data such as the satellite 112 and a separate source of network
`
`connectivity such as a WiFi hotspot. The merchant 106 may connect to the network 116 through
`
`the merchant server 108 using any suitable mechanism suchas a wired or wireless connection.
`
`[0043]
`
`A one or more servers 118 may also be connected to the network 116 and configured
`
`to manage interaction between the mobile device 104 and the merchant 106.
`
`In some
`
`implementations, all or part of the interaction between the mobile device 104 and the merchant
`
`106 may be through a direct communications link 120 without passing through the server 118 or
`
`the network 116.
`
`The direct communication link 120 may be implemented by radio
`
`transmissions (e.g., IEEE 802.11, Bluetooth),
`
`infrared signals, radio frequency identification
`
`(RFID), magnetism (e.g., magnetic strips such as used on credit cards), display of a code on the
`
`devicc 104 to a human opcrator or to a scanning device at the merchant 106, and/or any other
`
`method of directly passing information between the mobile device 104 and the merchant 106.
`
`[0044]
`
`The server(s) 118 may house or otherwise have a connection to multiple data stores
`
`including user information 122, merchant profiles 124, an advertisement (“ad”) database 126,
`
`and/or other data stores. Generally, the user information 122 contains information about the
`
`user 102 associated with the mobile device 104. The user information 122 enables efficient and
`
`personalized interaction between the user 102 and the merchant 106. The merchant profiles 124
`
`generally contain information about one or more merchants including the merchant 106 with
`
`which the user 102 is interacting. Types of interaction between the merchant 106 and the
`
`user 102 includes advertising provided from the merchant 106 to the device 104 and purchasing
`
`a good and/or service from the merchant 106 when the user 102 is at the merchant location.
`
`Information for generating relevant advertisements may be contained in the advertisement
`
`database 126.
`
`Information about which goods and/or services the user is be interested in
`
`7
`
`

`

`WO 2011/119407
`
`PCT/US2011/028825
`
`purchasing may be contained in the user information 122. Each of the data stores will be
`
`discussed in greater detail below.
`
`[0045]
`
`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 122, merchant profiles 124, advertisement database 126, and other
`
`information is correctly correlated with the right entity (e.g., user 102 and/or point-of-sale
`
`device 110). The authentication module 124 will be discussed in greater detail below.
`
`[0046]
`
`One or more online retailers 128 may also be connected to the network 116. The
`
`online retailer(s) 128 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 128 and one or more
`
`merchants 106 located at multiple geolocations.
`
`Illustrative Mobile Device
`
`[0047]
`
`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
`
`uscr identification module 206 that
`
`in may turn contain a uscr identificr 208 and/or uscr
`
`information 210. The memory 204 may also contain a transaction module 212, and a security
`
`module 214, an electronic document 216, and a coupon activation module 218. The user
`
`identifier 208 may be a unique numberor 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 128 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 numberof the mobile device 104 may be linked with a user name and password whenthe
`
`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 identification 208 may be identifier between devices by moving the SIM
`
`card.
`
`[0048]
`
`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
`
`

`

`WO 2011/119407
`
`PCT/US2011/028825
`
`information, a home location, and/or map of the device’s 104 past movements, past transaction
`
`histories, and/or any other information related to the user 102.
`
`[0049]
`
`Thetransaction module 212 may recognize when the mobile device 104 is located at a
`
`merchant location and,
`
`in response, may facilitate a transaction with the merchant 106. The
`
`transaction may be based in part on the user information 210. The transaction module 212 may
`
`be configured with appropriate application programminginterfaces (APIs)to establish a standard
`
`communication protocol for receiving information from the merchant 106 (e.g., merchant name
`
`and requested payment) and providing corresponding information about the user 102 (e.g.,
`
`payment information and useridentification 208).
`
`In some implementations, the transaction
`
`module 212 is a software application that a user 102 mayinstall on his or her device 104 such as
`
`by downloading from a website.
`
`In other implementations, the transaction module 212 may be
`
`preinstalled by a manufacturer or retailer of the mobile device 104 and/or built into the mobile
`
`device 104 as a type of firmware or hardware. The transaction module 212 coordinates the user
`
`identification 208, user information 210, geolocation, and the like to facilitate transactions
`
`between the user 102 and the merchant 106.
`
`[0050]
`
`Given the ability of the mobile device 104 to serve as a platform for zero-click
`
`purchases, there is a need to provide security in order to prevent unauthorized charges. The
`
`security module 214 addresses this need by limiting functionality of the mobile device 104 and
`
`initiating security events in appropriate circumstances. The security module 214 may process
`
`login information, such as passwords and/or biometric information to authenticate the user 102
`
`and prevent other people from using the mobile device 104. The security module 214 may also
`
`analyze bchavior such as purchasing patterns and/or movementpatterns and infer that irregular
`
`behavior may indicate fraudulent or unauthorized activity and limit device functionality
`
`accordingly, as described below in greater detail.
`
`[0051]
`
`The memory 204 may also contain an electronic document 216. The electronic
`
`document 216 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 216 may include a
`
`coupon. The coupon may be associated with one or more merchants.
`
`[0052]
`
`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,
`
`9
`
`

`

`WO 2011/119407
`
`PCT/US2011/028825
`
`maps, web pages etc. Accordingly, the terms book and/or eBook may include any contentthatis
`
`in electronic or digital format.
`
`[0053]
`
`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.
`
`[0054]
`
`A couponactivation module 218 may regulate use and redemption of coupons based
`
`on geolocation and/or other factors. The coupon activation module 218 may activate a coupon
`
`when the mobile device 104 is located at a merchant 106. Prior to activation, the coupon
`
`activation module 218 may concealall or part of the coupon from the user 102. For example, the
`
`user reading an electronic document 214 may be unable to see a coupon included in that
`
`electronic document 214 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 214
`
`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.
`
`[0055] Mobile device 104 also includes one or more input and output deviccs 220. The
`
`output devices may comprise one or more display devices 222 including touch-screen displays
`
`that also function as an input device. An accelerometer 224 detects rotation or vibration of the
`
`mobile device 104. The accelerometer 224 may be a convenient mechanism for the user 102 to
`
`communicate an input to the mobile device 104 by slapping, shaking, twisting, and/or by making
`
`a motion that can be detected by the accelerometer 224. The mobile device 104 may also
`
`include a camera 226 capable of taking still or video pictures. An antenna 228 in the mobile
`
`device 104 may send and receive wireless signals from sources such as the radio antenna 114
`
`and satellite 112. The antenna 228 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 230, such as
`
`a microphone and a speaker used, for example,
`
`in an implementation in which the mobile
`
`device 104 functionsas a telephone.
`
`[0056]
`
`In
`
`some
`
`implementations,
`
`the mobile
`
`device
`
`104 may
`
`also
`
`include
`
`a
`
`calendar/clock 232, a location sensor 234, and a network interface 236. The calendar/clock 232
`
`may calculate time, date, and other data that can be derived from time data and date data.
`
`In
`
`some implementations, the calendar/clock 232 may communicate with the location sensor 234 to
`10
`
`