U.S. patent application number 14/021045 was filed with the patent office on 2014-07-03 for automatic wireless consumer checkins.
The applicant listed for this patent is John Hastings GRANBERY. Invention is credited to John Hastings GRANBERY.
Application Number | 20140188733 14/021045 |
Document ID | / |
Family ID | 51018312 |
Filed Date | 2014-07-03 |
United States Patent
Application |
20140188733 |
Kind Code |
A1 |
GRANBERY; John Hastings |
July 3, 2014 |
AUTOMATIC WIRELESS CONSUMER CHECKINS
Abstract
Computing systems and methods for facilitating consumer
transactions in retail and other establishments include
communication interfaces adapted to couple a computing system to a
plurality of third party phones or other mobile electronic devices,
storage components adapted to store user information, participating
merchant information, or any combination thereof, and processors in
communication with the communication interfaces and storage
components. The processors are adapted to facilitate the automatic
wireless checkins of third party users of the third party phones or
other mobile electronic devices at participating merchants. Such
automatic wireless checkins take place when the third party phones
or mobile electronic devices are simply present at the
participating merchants, without any affirmative activity by the
users at the participating merchants.
Inventors: |
GRANBERY; John Hastings;
(Los Altos, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
GRANBERY; John Hastings |
Los Altos |
CA |
US |
|
|
Family ID: |
51018312 |
Appl. No.: |
14/021045 |
Filed: |
September 9, 2013 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
61747918 |
Dec 31, 2012 |
|
|
|
Current U.S.
Class: |
705/64 ;
705/5 |
Current CPC
Class: |
G06Q 20/20 20130101;
G06Q 30/0261 20130101; H04W 88/02 20130101; G06Q 20/322 20130101;
G06Q 20/3226 20130101; H04W 4/021 20130101; H04W 4/023 20130101;
G06Q 20/3224 20130101; G06Q 20/202 20130101; G06Q 20/327 20130101;
H04L 49/201 20130101; G06Q 20/3829 20130101; G06Q 30/0267 20130101;
G06Q 20/32 20130101; G06Q 20/3278 20130101 |
Class at
Publication: |
705/64 ;
705/5 |
International
Class: |
G06Q 20/32 20060101
G06Q020/32; G06Q 20/20 20060101 G06Q020/20 |
Claims
1. A computing system, comprising: one or more communication
interfaces adapted to couple the computing system to a plurality of
third party mobile electronic devices; one or more storage
components adapted to store user information, participating
merchant information, or any combination thereof; and one or more
processors in communication with the one or more communication
interfaces and the one or more storage components, said one or more
processors being adapted to facilitate the automatic wireless
checkins of third party users of the third party mobile electronic
devices at participating merchants, wherein said automatic wireless
checkins take place when the third party mobile electronic devices
are simply present at the participating merchants without any
affirmative activity by the users at the participating
merchants.
2. The computing system of claim 1, wherein said automatic wireless
checkins are facilitated using Bluetooth low energy protocols and
communications.
3. The computing system of claim 1, wherein said one or more
processors are further adapted to facilitate output presentations
on the third party mobile electronic devices, the output
presentations including indications or information regarding the
automated wireless checkins.
4. The computing system of claim 1, wherein said one or more
processors are further adapted to provide application downloads to
the third party mobile devices.
5. A non-transitory medium having a plurality of machine-readable
instructions which, when executed by one or more processors of a
server controlled by a service provider, are adapted to cause the
server to perform a method comprising: providing software code to
be used on a third party mobile computing device to a user thereof,
the software code including information regarding automatic
wireless checkins using said third party mobile computing device,
said providing being performed electronically by a processor;
enabling the third party mobile computing device to utilize a
Bluetooth low energy protocol to detect the presence of a nearby
merchant device using the provided software code, said detecting
occurring automatically without any affirmative action by the user;
facilitating a wireless communications exchange between the third
party mobile computing device and the nearby merchant device, said
exchange occurring automatically without any affirmative action by
the user; and checking in the user of the third party mobile
computing device as a known consumer at the merchant of the nearby
merchant device, said checking in occurring automatically without
any affirmative action by the user.
6. A method of automatically checking in a user at a merchant,
comprising: transmitting, by one or more merchant devices,
Bluetooth.TM. low energy (BLE) communications; sending, by the one
or more merchant devices, BLE communications to a connected user
device; receiving, by the one or more merchant devices, BLE
communications from the connected user device; and automatically
checking in, by the merchant device, a user of the user device with
the merchant based on the received BLE communications.
7. The method of claim 6, wherein transmitting BLE signals
comprises transmitting BLE signals including a generic universally
unique identifier (UUID).
8. The method of claim 6, wherein transmitting BLE signals
comprises transmitting BLE signals on an unencrypted channel.
9. The method of claim 6, wherein sending BLE communications
comprises sending metadata and a specific beacon token to the
connected user device.
10. The method of claim 6, wherein receiving BLE communications
comprises receiving an encrypted token from the connected user
device.
11. The method of claim 6, wherein checking in a user of the user
device comprises: sending, by the merchant device, the received
encrypted token to a remote server for decryption; and receiving,
by the merchant device, checkin instructions based on the decrypted
received encrypted token.
12. The method of claim 6, further comprising: determining if the
user device is near a point of sale device; and completing a
transaction at the point of sale device when the user is near the
point of sale device.
13. The method of claim 11, wherein the point of sale device
includes one of the one or more merchant devices.
14. The method of claim 6, wherein the one or merchant devices
comprise beacon devices for transmitting and receiving BLE
signals.
15. A method of automatically checking in at a merchant,
comprising: receiving, by a user device, Bluetooth.TM. low energy
(BLE) communications from one or more merchant devices, the BLE
communications including at least a generic universally unique
identifier (UUID); and sending, by the user device to the one or
more merchant devices, BLE communications, the BLE communications
including at least an encrypted token, wherein the one or more
merchant devices automatically checks in the user device based on
the sent encrypted token.
16. The method of claim 15, wherein receiving BLE communications
comprises receiving metadata and a specific beacon token.
17. The method of claim 15, wherein receiving BLE communications
comprises receiving BLE communications on an unencrypted
channel.
18. The method of claim 15, wherein the user device comprises a
mobile device.
19. The method of claim 15, wherein the one or merchant devices
comprise beacon devices for transmitting and receiving BLE
signals.
20. The method of claim 15, further comprising: receiving, by the
user device, at least one key and at least one user token; and
encrypting, by the user device, the token with that least one key.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] Pursuant to 35 U.S.C. .sctn.119(e), this application claims
priority to the filing date of U.S. Provisional Application No.
61/747,918, entitled "AUTOMATIC WIRELESS CONSUMER CHECKINS," filed
Dec. 31, 2012, which is incorporated by reference herein in its
entirety.
TECHNICAL FIELD
[0002] The present disclosure relates generally to systems and
devices that facilitate consumer transactions, and more
particularly to systems and devices for consumer transactions that
utilize personal mobile devices of consumers.
BACKGROUND
[0003] Computer systems and networks have facilitated the tasks of
buying, selling and transferring goods. For example, global
computer networks, such as the Internet, have allowed purchasers to
relatively quickly and efficiently seek and purchase goods online.
Similarly, global computer networks provide an efficient and
cost-effective medium for sellers to advertise, offer, provide, and
sell their goods. Electronic commerce companies provide buyers and
sellers with online services and the infrastructure to accept
orders of goods from remote purchasers, to perform the financial
transactions necessary to confirm and complete the sale of goods,
to ship or distribute the goods to remote purchasers, and to
perform other related logistics. Technology advances have also
allowed for a wider variety of devices and transaction types in the
retail and other marketplaces.
[0004] One example of a relatively new development within the realm
of electronic commerce is the ability to allow a consumer to pay
for a good or service at a point of sale through the use of his or
her smart phone or other personal mobile device. A user merely
needs to have an appropriate payment application or "app" on his or
her device, whereupon the user can present his or her phone or
other similar device at an appropriate time and location at a
retail or other establishment. The retailer or other seller or
service provider can then "checkin" the given user through some
process of reading his or her smart phone or other similar device,
after which the seller or service provider can accept payment or
credit through some form of communication with the checked in or
acknowledged device. This "checkin" ability to accept payment or
credit without the use of cash, checks, credit cards, or other
traditional payment means can be particularly helpful in many
settings.
[0005] Unfortunately, such setups are not without their own
drawbacks and inconvenient features. In many instances, the current
checkin process can be time consuming. For example, current checkin
procedures often require the customer to take out his or her phone
or other device at a point of sale in order to make a payment or
provide a credit. This often involves the device searching for the
appropriate wireless connection at the store, searching for the
store among many possible choices on the device, and/or manual user
input or selection on his or her personal mobile device, all of
which can take some inconvenient amount of time. Even small amounts
of time that are less than a minute can be frustrating where other
consumers are waiting in line behind the user at a register or
other point of sale.
BRIEF DESCRIPTION OF THE DRAWINGS
[0006] The included drawings are for illustrative purposes and
serve only to provide examples of possible systems and methods for
the disclosed automatic wireless consumer checkins. These drawings
in no way limit any changes in form and detail that may be made to
that which is disclosed by one skilled in the art without departing
from the spirit and scope of this disclosure.
[0007] FIG. 1 illustrates in block diagram format an exemplary
computing system adapted for implementing the purchase of goods or
services according to some embodiments.
[0008] FIG. 2 illustrates in block diagram format an exemplary
computer system suitable for implementing on one or more devices of
the computing system in FIG. 1 according to some embodiments.
[0009] FIG. 3 illustrates in block diagram format an exemplary
merchant layout and associated system components adapted for
implementing the purchase of goods or services using automatic
wireless consumer checkins according to some embodiments.
[0010] FIG. 4 provides a flowchart of an exemplary method of
facilitating payment or credit for a purchase by utilizing an
automated wireless consumer checkin according to some
embodiments.
[0011] FIG. 5 provides a flowchart of an exemplary method of
performing a handshake between a merchant dongle and a purchaser
mobile device on an unencrypted channel so as to facilitate a
payment or credit for a purchase according to some embodiments.
DETAILED DESCRIPTION
[0012] What is needed are systems and methods that provide for
faster or more automatic checkins where cellular phones or other
mobile devices are used for consumer transactions.
[0013] Exemplary applications of apparatuses and methods are
described in this section. These examples are being provided solely
to add context and aid in the understanding of the embodiments
disclosed herein. It will thus be apparent to one skilled in the
art that the disclosed embodiments may be practiced without some or
all of these specific details. In other instances, well known
process steps have not been described in detail in order to avoid
unnecessarily obscuring the disclosed embodiments. Other
applications are possible, such that the following examples should
not be taken as limiting.
[0014] In the following detailed description, references are made
to the accompanying drawings, which form a part of the description
and in which are shown, by way of illustration, specific
embodiments. Although these embodiments are described in sufficient
detail to enable one skilled in the art to practice the disclosed
embodiments, it is understood that these examples are not limiting,
such that other embodiments may be used, and changes may be made
without departing from the spirit and scope of the disclosure.
[0015] The disclosed embodiments relate to devices, systems and
methods involving activities with respect to the purchase of goods
or services, such as in a retail setting. In various particular
embodiments, the subject devices, systems or methods can involve
one or more user devices in communication over a network. Such a
network can facilitate the improved and purchase of goods or
services, such as through a more robust use of a cellular telephone
or other personal mobile device. The subject systems or methods can
utilize programs and/or associated hardware on user phones and
other mobile devices to facilitate the automated checkins of users
when they are at a cooperating or subscribing location. Users that
have been automatically checked in by such a system can then more
readily pay or provide credit for goods or services at a point of
sale in the establishment.
[0016] While the various examples disclosed herein focus on
particular aspects regarding the purchase of goods or services in a
retail or similar setting, it will be understood that the various
principles and embodiments disclosed herein can be applied to other
types of applications and arrangements involving consumer or
personal transactions as well. For example, automated checkins at a
library, private club, public venue or government building, may
also utilize one or more of the aspects and features found in the
various systems and methods provided.
Systems and Devices
[0017] Beginning with FIG. 1, an exemplary embodiment of a
computing system adapted for implementing the purchase of goods or
services is illustrated in block diagram format. As shown,
computing system 100 may comprise or implement a plurality of
servers and/or software components that operate to perform various
methodologies in accordance with the described embodiments.
Exemplary servers may include, for example, stand-alone and
enterprise-class servers operating a server OS such as a
MICROSOFT.RTM. OS, a UNIX.RTM. OS, a LINUX.RTM. OS, or other
suitable server-based OS. It can be appreciated that the servers
illustrated in FIG. 1 may be deployed in other ways and that the
operations performed and/or the services provided by such servers
may be combined or separated for a given implementation and may be
performed by a greater number or fewer number of servers. One or
more servers may be operated and/or maintained by the same or
different entities.
[0018] Computing system 100 can include, among various devices,
servers, databases and other elements, a client 102 that may
comprise or employ one or more client devices 104, such as a
laptop, a mobile computing device, a PC, and/or any other computing
device having computing and/or communications capabilities in
accordance with the described embodiments. In particular, it is
specifically contemplated that client devices 104 can include a
cellular telephone or other similar mobile device that a user can
carry on or about his or her person and access readily.
[0019] Client devices 104 generally may provide one or more client
programs 106, such as system programs and application programs to
perform various computing and/or communications operations.
Exemplary system programs may include, without limitation, an
operating system (e.g., MICROSOFT.RTM. OS, UNIX.RTM. OS, LINUX.RTM.
OS, Symbian OS.TM., Embedix OS, Binary Run-time Environment for
Wireless (BREW) OS, JavaOS, a Wireless Application Protocol (WAP)
OS, and others), device drivers, programming tools, utility
programs, software libraries, application programming interfaces
(APIs), and so forth. Exemplary application programs may include,
without limitation, a web browser application, messaging
applications (e.g., e-mail, IM, SMS, MMS, telephone, voicemail,
VoIP, video messaging), contacts application, calendar application,
electronic document application, database application, media
application (e.g., music, video, television), location-based
services (LBS) application (e.g., GPS, mapping, directions,
point-of-interest, locator), and so forth. One or more of client
programs 106 may display various graphical user interfaces (GUIs)
to present information to and/or receive information from one or
more of client devices 104.
[0020] As shown, client 102 can be communicatively coupled via one
or more networks 108 to a network-based system 110. Network-based
system 110 may be structured, arranged, and/or configured to allow
client 102 to establish one or more communications sessions with
network-based system 110 using various computing devices 104 and/or
client programs 106. Accordingly, a communications session between
client 102 and network-based system 110 may involve the
unidirectional and/or bidirectional exchange of information and may
occur over one or more types of networks 108 depending on the mode
of communication. While the embodiment of FIG. 1 illustrates a
computing system 100 deployed in a client-server operating
environment, it is to be understood that other suitable operating
environments and/or architectures may be used in accordance with
the described embodiments.
[0021] Data and/or voice communications between client 102 and the
network-based system 110 may be sent and received over one or more
networks 108 such as the Internet, a WAN, a WWAN, a WLAN, a mobile
telephone network, a landline telephone network, a VoIP network, as
well as other suitable networks. For example, client 102 may
communicate with network-based system 110 over the Internet or
other suitable WAN by sending and or receiving information via
interaction with a web site, e-mail, IM session, and/or video
messaging session. Any of a wide variety of suitable communication
types between client 102 and system 110 can take place, as will be
readily appreciated. In particular, wireless communications of any
suitable form may take place between client 102 and system 110,
such as that which often occurs in the case of mobile phones or
other personal mobile devices.
[0022] In various embodiments, computing system 100 can include,
among other elements, a third party 112, which may comprise or
employ a third-party server 114 hosting a third-party application
116. In various implementations, third-party server 314 and/or
third-party application 116 may host a web site associated with or
employed by a third party 112. For example, third-party server 114
and/or third-party application 116 may enable network-based system
110 to provide client 102 with additional services and/or
information, such as advertisements or promotions regarding sale
items. In some embodiments, one or more of client programs 106 may
be used to access network-based system 110 via third party 112. For
example, client 102 may use a web client to access and/or receive
content from network-based system 110 after initially communicating
with a third-party web site 112.
[0023] Network-based system 110 may comprise one or more
communications servers 120 to provide suitable interfaces that
enable communication using various modes of communication and/or
via one or more networks 108. Communications servers 120 can
include a web server 122, an API server 124, and/or a messaging
server 126 to provide interfaces to one or more application servers
130. Application servers 130 of network-based system 110 may be
structured, arranged, and/or configured to provide various online
marketplace and/or purchasing services to users that access
network-based system 110. In various embodiments, client 102 may
communicate with applications servers 130 of network-based system
110 via one or more of a web interface provided by web server 122,
a programmatic interface provided by API server 124, and/or a
messaging interface provided by messaging server 126. It can be
appreciated that web server 122, API server 124, and messaging
server 126 may be structured, arranged, and/or configured to
communicate with various types of client devices 104 and/or client
programs 106 and may interoperate with each other in some
implementations.
[0024] Web server 122 may be arranged to communicate with web
clients and/or applications such as a web browser, web browser
toolbar, desktop widget, mobile widget, web-based application,
web-based interpreter, virtual machine, and so forth. API server
124 may be arranged to communicate with various client programs 106
and/or a third-party application 116 comprising an implementation
of API for network-based system 110. Messaging server 126 may be
arranged to communicate with various messaging clients and/or
applications such as e-mail, IM, SMS, MMS, telephone, VoIP, video
messaging, and so forth, and messaging server 126 may provide a
messaging interface to enable access by client 102 and/or third
party 112 to the various services and functions provided by
application servers 130.
[0025] When implemented as an online goods and services
marketplace, application servers 130 of network-based system 110
may provide various online marketplace services including, for
example, account services, buying services, selling services,
listing catalog services, dynamic content management services,
delivery services, payment services, and notification services.
Application servers 130 may include an account server 132, a buying
server 134, a selling server 136, a listing catalog server 138, a
dynamic content management server 140, a payment server 142, a
notification server 144, and/or a delivery server 146 structured
and arranged to provide such online marketplace services.
[0026] Application servers 130, in turn, may be coupled to and
capable of accessing one or more databases 150 including a
subscriber database 152, an active events database 154, and/or a
transaction database 156. Databases 150 generally may store and
maintain various types of information for use by application
servers 130 and may comprise or be implemented by various types of
computer storage devices (e.g., servers, memory) and/or database
structures (e.g., relational, object-oriented, hierarchical,
dimensional, network) in accordance with the described
embodiments.
[0027] Continuing with FIG. 2, an exemplary computer system 200
suitable for implementing on one or more devices of the computing
system in FIG. 1 is depicted in block diagram format. In various
implementations, a device that includes computer system 200 may
comprise a personal computing device (e.g., a smart or mobile
phone, a computing tablet, a personal computer, laptop, PDA,
Bluetooth device, key FOB, badge, etc.) that is capable of
communicating with a network. The goods or services provider may
utilize a network computing device (e.g., a network server) capable
of communicating with the network. It should be appreciated that
each of the devices utilized by users, goods and services
providers, and payment providers may be implemented as computer
system 200 in a manner as follows.
[0028] Computer system 200 can include a bus 202 or other
communication mechanism for communicating information data,
signals, and information between various components of computer
system 200. Components include an input/output (I/O) component 204
that processes a user action, such as selecting keys from a
keypad/keyboard, selecting one or more buttons or links, etc., and
sends a corresponding signal to bus 202. I/O component 204 may also
include an output component, such as a display 211 and a cursor
control 213 (such as a keyboard, keypad, mouse, etc.). An optional
audio input/output component 205 may also be included to allow a
user to use voice for inputting information by converting audio
signals. Audio I/O component 205 may allow the user to hear audio.
A transceiver or network interface 206 transmits and receives
signals between computer system 200 and other devices, such as
another user device, a merchant server, or a payment provider
server via a network. In various embodiments, such as for many
cellular telephone and other mobile device embodiments, this
transmission can be wireless, although other transmission mediums
and methods may also be suitable. A processor 212, which can be a
micro-controller, digital signal processor (DSP), or other
processing component, processes these various signals, such as for
display on computer system 200 or transmission to other devices
over a network 260 via a communication link 218. Again,
communication link 218 can simply be a wireless communication form
in some embodiments. Processor 212 may also control transmission of
information, such as cookies or IP addresses, to other devices.
[0029] Components of computer system 200 also include a system
memory component 214 (e.g., RAM), a static storage component 216
(e.g., ROM), and/or a disk drive 217. Computer system 200 performs
specific operations by processor 212 and other components by
executing one or more sequences of instructions contained in system
memory component 214. Logic may be encoded in a computer readable
medium, which may refer to any medium that participates in
providing instructions to processor 212 for execution. Such a
medium may take many forms, including but not limited to,
non-volatile media, volatile media, and transmission media. In
various implementations, non-volatile media includes optical or
magnetic disks, volatile media includes dynamic memory, such as
system memory component 214, and transmission media includes
coaxial cables, copper wire, and fiber optics, including wires that
comprise bus 202. In one embodiment, the logic is encoded in
non-transitory computer readable medium. In one example,
transmission media may take the form of acoustic or light waves,
such as those generated during radio wave, optical, and infrared
data communications.
[0030] Some common forms of computer readable media includes, for
example, floppy disk, flexible disk, hard disk, magnetic tape, any
other magnetic medium, CD-ROM, any other optical medium, punch
cards, paper tape, any other physical medium with patterns of
holes, RAM, PROM, EPROM, FLASH-EPROM, any other memory chip or
cartridge, or any other medium from which a computer is adapted to
read.
[0031] In various embodiments of the present disclosure, execution
of instruction sequences to practice the present disclosure may be
performed by computer system 200. In various other embodiments of
the present disclosure, a plurality of computer systems 200 coupled
by communication link 218 to the network (e.g., such as a LAN,
WLAN, PTSN, and/or various other wired or wireless networks,
including telecommunications, mobile, and cellular phone networks)
may perform instruction sequences to practice the present
disclosure in coordination with one another.
[0032] Where applicable, various embodiments provided by the
present disclosure may be implemented using hardware, software, or
combinations of hardware and software. Also, where applicable, the
various hardware components and/or software components set forth
herein may be combined into composite components comprising
software, hardware, and/or both without departing from the spirit
of the present disclosure. Where applicable, the various hardware
components and/or software components set forth herein may be
separated into sub-components comprising software, hardware, or
both without departing from the scope of the present disclosure. In
addition, where applicable, it is contemplated that software
components may be implemented as hardware components and
vice-versa.
[0033] Software, in accordance with the present disclosure, such as
program code and/or data, may be stored on one or more computer
readable mediums. It is also contemplated that software identified
herein may be implemented using one or more general purpose or
specific purpose computers and/or computer systems, networked
and/or otherwise. Such software may be stored and/or used at one or
more locations along or throughout the system, at client 102,
network-based system 110, or both.
Automatic Wireless Checkins
[0034] As will be readily appreciated, the foregoing networks,
systems, devices, methods and variations thereof can be used to
implement an automated checkin of users at a cooperating or
subscribing establishment, such that subsequent purchase
transactions and other activities can be more streamlined and
convenient. Rather than having users resort to known procedures
involving wireless checkins with their own personal mobile devices
at a point of sale, a more user friendly system involving the use
of Bluetooth Low Energy ("BLE") in association with separate user
phones, other mobile devices or any suitable user computing devices
can be provided. One or more applications or "apps" can be provided
for download and use on private consumer phones and mobile devices
to help facilitate the use of the automated checkin process. In
various embodiments, such automated checkins can be facilitated by
a transaction service provider, such as, for example, PayPal Inc.
of San Jose, Calif.
[0035] Bluetooth low energy ("BLE") is a relatively new feature of
Bluetooth 4.0 wireless radio technology. BLE is intended for
primarily low-power and low-latency applications for wireless
devices within a short range, such as up to about 50 meters.
Devices using BLE utilize a protocol having intermittent
communications, smaller amounts of data transfer and bandwidths, as
well as low duty cycles. As such, BLE can consume only a fraction
of the power of traditional Bluetooth enabled products for
Bluetooth communications. In many cases, BLE products will be able
to operate more than a year on a tiny battery without recharging.
The use of BLE can allow for a wider variety of applications in
relatively low power devices, such as smart phones and other
personal mobile devices.
[0036] In various embodiments, it is specifically contemplated that
personal smart phones and other mobile devices that are equipped
with BLE capabilities can be provided with programs or "apps" that
leverage the use of these capabilities to allow for the automated
checkins of owners or users carrying those devices when they are
merely in or at a participating establishment. BLE allows for
constant passive scanning for Bluetooth peripherals. A suitable
program or app on a user device can be set to run frequently in the
background under a BLE protocol, always monitoring for a
significant change in location and/or presence of an appropriate
BLE peripheral at a merchant or vendor. When the owner or user of
the phone or personal mobile device enters a store or other
participating location, he or she would pass by a BLE peripheral by
the entrance or at some other appropriate location. This merchant
or third party run BLE peripheral can be sending out a signal, such
as for advertising a checkin service with a universally unique
identifier ("UUID") and store information.
[0037] It is worth noting that the communication process between
the merchant dongle or other beacon and the purchaser smart phone
or other mobile device can take place on an unencrypted channel.
This is significant in that the communications between the devices
actually involve a financial transaction, the details of which can
be detected by any party due to the unencrypted nature of the
communication. While the use of an unencrypted channel provides
greater speed and flexibility for the use of many different
devices, certain precautions should be taken to protect the
sensitive nature of the financial or other consumer transaction.
This can be accomplished by providing, for example, tokens for the
devices to identify each other only in a generic fashion, with all
sensitive information being retained remotely by a financial
processing entity or other service provider. Also, since
communications take place over unencrypted channels, there is no
reason for a device to retain long term specific identifiers or
information that is typically needed for bonded or encrypted
communications.
[0038] The smart phone or other mobile user device would wirelessly
detect or "see" this outside BLE peripheral due to the constant
background running of the app under a BLE protocol. Once detection
is made at a low or lowest energy level and duty cycle, a ramp up
in energy, duty cycle, and/or other operating parameters can take
place so that a handshake and checkin can take place automatically
between the user device and the merchant device. In particular, the
privately or separately owned mobile phone or other mobile user
device can connect to the service at the store, merchant or other
location, encrypt a payment token along with the beacon token and
write it to the service. If the merchant possesses the necessary
keys to decrypt the payment token, the information could then be
decrypted and used directly by the merchant themself.
Alternatively, the information may be passed by the peripheral or
other component up to a remote third party payment provider, such
as for example, PayPal. The third party provider can then decrypt
the payment token and execute a checkin at the establishment on
behalf of the customer or user. Later, when the customer or user
approaches a checkout aisle or other point of sale, another BLE
peripheral advertising a checkout service can be present. Various
checks and processes can then take place based on the transmit
power and received power of the BLE peripheral, mobile user device,
or both, and the phone or other mobile device can again write
credentials to the checkout service. This associates the customer
with a particular register. Checkout can then proceed as normal for
a checkin payment. In some embodiments, after an initial checkin,
the mobile user device may be capable of advertising a one-time use
UUID for a BLE peripheral. When the BLE peripheral receives the
advertised UUID, the BLE would attempt to establish communications
with the mobile device.
[0039] In order for the actual handshake and communication between
the dongle or beacon and the user mobile device to be effective
over an unencrypted channel, it is important that both devices
already be initialized and signed up for the same remote third
party service provider, such as Paypal or any other suitable
provider. Each device can then be provided with public encryption
keys, private encryption keys and payment tokens prior to meeting
each other, such that the devices are able to recognize each other
as belonging to the proper service when the signals are detected
and the handshake begins. Information is then exchanged purely by
way of keys and payment tokens, such that no sensitive information
is ever exchanged over the unencrypted channel. Details of such key
and token provisions, as well as the handshake process and
protocols are provided below with respect to FIG. 5.
[0040] With the use of BLE and appropriate apps or programs on user
devices, this entire process can be automated in many instances.
This can save significant amounts of time and inconvenience for
many consumers at the point of sale. In some embodiments, a beep,
other sound, vibration, visual display or other output from the
smart phone or other mobile user device can be provided upon
automatic checkin. This can simply provide a notice to the user
that they are now checked in at the establishment. Different sounds
or indicators on a display can confirm to the user which
establishment(s) the user is currently checked in, such as where
malls or other locations having multiple vendors in a small area
might be applicable. In this manner, a user can be made aware that
he or she is checked in and is able to readily shop here and check
out quickly.
[0041] In various further embodiments, other procedures can be
implemented to take advantage of the knowledge that a user is at a
given merchant location and that a purchase or other point of sale
activity might be imminent. The bidirectional nature of BLE can
allow for a more robust experience and interaction between the
merchant, user, and/or third party payment service provider. For
example, advertising and promotional offers can be directed to a
known user from the merchant, the payment service provider, or
both. These items can rely on a known history and other parameters
applicable to the specific user. For example, notices can be
provided regarding sales or promotions on items or related items
that are known to be of interest or the subject of past purchases
by a known user. Also, a step-up procedure to assess risk can be
implemented, such that the user can be prompted for a PIN or other
identifier if there is any concern over risk for that user or about
a particular purchase. In addition, a customized offer of credit
can be made for the user based upon various known factors in the
associated customer account, history or profile. In various
embodiments, a signal to the phone or device to buzz or emit a
sound or display can be provided if the merchant or third party
payment service provider might need a PIN or other verification at
the time of purchase.
[0042] In various embodiments, the one or more processors 212 can
be located on a remote server, such as a third party payment
service provider server, while the display and user inputs can be
located onsite at a store or other participating location, such as
on a register, and/or also on a mobile user device, such as a smart
phone. Processor(s) 212 can be adapted to facilitate an automatic
check in process, and can be further adapted to accept and process
a request to purchase goods upon checkout. Other services can be
provided by processor(s) 212, such as any of the actions or
services set forth herein.
[0043] FIG. 3 illustrates in block diagram format an exemplary
merchant layout and associated system components adapted for
implementing the purchase of goods or services using automatic
wireless consumer checkins according to some embodiments. It will
be readily appreciated that this merchant layout is only provided
for purposes of illustration, and that many other types of layouts,
devices, procedures and the like could be effectively implemented
using the various principles of the present disclosure.
[0044] Merchant layout 300 includes an indoor store floor having a
number of BLE signaling devices 310. These devices can be
distributed strategically throughout the store or establishment,
such as near the front door, at central locations, and/or at
locations of high volume traffic within the establishment. One or
more third party mobile user devices 102, such as phones, PDAs,
tablets or the like, can interact with one or more of the signaling
devices 310 throughout the store. Preferably, only one interaction
with a signaling device 310 is needed for a checkin, although it
may be useful for an establishment to know where a user is located
and/or user travel and shopping patterns or habits within a store.
Such further information can be used to provide further advertising
and promotional offers (e.g., related to something at or near where
the user is physically located), and/or to authenticate the actual
user versus one who may have stolen or is otherwise using the
mobile device in an unauthorized fashion. Such further
authentication can involve checking known user traffic and shopping
patterns against what is currently happening for a given
device.
[0045] An actual automatic checkin process can involve a subscribed
or affirmatively active user entering a store or establishment,
whereupon the phone or other user device on the person of the user
has a low level background program running that detects a low level
BLE signal from one or more devices 310 in the store. The phone or
device 102 can then "wake up" and communicate on a more active
level with the store device 310. A UUID and token can be generated
and assigned to the user device for a particular time, location and
session, with appropriate expiration and other safeguards in place
to protect against fraud or other misuse. For example, a period of
one or two hours might suffice for a typical checkin session or
event.
[0046] The UUID, token, and other informational items can be
exchanged between the store device and the user device, whereupon
the user device (and user) are "checked in" at that location and
are ready to make a purchase or otherwise check out at some later
time. Other informational items exchanged or provided can include
the store type, name and number, store location or address, actual
or likely items of interest or purchase for the user, a user
history at that location, similar locations, and/or overall, the
uniquely identified user, a maximum amount of credit or currency
available overall to the user for an automated purchase, the amount
of credit or currency that may be used without a PIN or other
affirmative user authentication being required, among other
possibilities. This information can be stored on the user device
for a session or longer, can be provided to the store or other
establishment, and can also be provided to a remotely owned and
controlled separate payment service provider.
[0047] After checkin, various intermediate transactions, offers,
credit or risk assessments can take place, whereupon check out or
purchase can take place at any of a number of terminals or
registers 320. If needed, authentication of the user can be had by
way of a manual PIN entry, a fingerprint scan, a manual facial
recognition by store personnel, and/or the like. In an automated
fashion, one or more of the terminal 320 can also be equipped with
BLE signaling and communication devices, such that the presence or
close proximity of one or more checked in devices 102 can be read.
Automated or automatic check in processes can utilize GPS,
triangulation, a signal strength of the different devices 102 to
different terminals, and/or the like to estimate where a particular
device 102 is located in the checkout process.
[0048] In some embodiments, a display readout of several possible
devices can be presented to store personnel, such that the right
device or user can be readily picked from a subset of all presently
checked in devices and customers. For example, the 3 or 5 most
likely devices/users for a given checked in customer that is trying
to check out can be presented on a terminal 320 for a store clerk.
A quick verification of the correct device/user can be made by the
clerk, whereupon the final payment and check out process is quickly
consummated and finished. In the event that the small subset of 3
or 5 most likely devices does not have the correct device for the
customer that is immediately before the clerk, an available input
can allow the clerk to expand the possible number of likely choices
to 10, 20 or even all currently checked in devices. In the event
that the present customer/user/device can still not be found on the
menu of selections available to the clerk, then a re-checkin
process can take place at the terminal 320 itself.
Methods
[0049] Although a wide variety of applications and methods
involving the use of BLE to facilitate automatic wireless consumer
checkins might be envisioned, one basic method is illustrated here.
Turning next to FIG. 4, a flowchart of an exemplary method of
facilitating an automatic wireless consumer checkin is provided. In
particular, such a method can involve using or operating any of the
various computing components, devices, systems and/or networks
described above. It will be readily appreciated that not every
method step set forth in this flowchart is always necessary, and
that further steps not set forth herein may also be included.
Furthermore, the exact order of steps may be altered as desired for
various applications.
[0050] Beginning with a start step 400, a first process step 402
can involve an application, app or other suitable program being
provided to a third party user phone or other mobile computing
device. Such providing can be performed electronically by a
processor, such as on a separately owned server located remotely
from the mobile device user. As will be readily appreciated, this
providing can be facilitated by the remote processor, such as
through an app store or other processor or server owned by another
separate party that communicates directly with third party mobile
phones and user devices. The app or program can include software
code to run a number of functions, including code or information
regarding automatic wireless checkins using the phone or other
personal mobile device.
[0051] At a subsequent process step 404, suitable BLE signals can
be broadcast from one or more merchant controlled devices at a
suitable store, merchant or other participating establishment. At
least one of these BLE signals can then be detected by the third
party mobile phone when it comes within range of the BLE signals at
process step 406. Again, this detection can be accomplished by
enabling the third party phone or other mobile computing device to
utilize a Bluetooth low energy protocol to detect the presence of a
nearby merchant device using the provided software code. This
detecting can occur automatically without any affirmative action by
the user, as the program or app can run continuously or semi
continuously or intermittently in automated fashion in the
background and at low energy and bandwidth levels under a BLE
protocol.
[0052] At the next process step 408, a wireless communications
exchange between the third party phone or mobile computing device
and the nearby merchant device can take place. Such an exchange can
involve a handshake, exchange of pertinent information and the
like, as will be readily appreciated by one of skill in the art.
Again, said exchange can occur automatically without any
affirmative action by the user of the phone or mobile device. Upon
a proper exchange and verification of information, a following
process step 410 can involve the owner or user of the phone or
other mobile device being checked into the merchant, either on the
merchant computer system, on a remote payment service provider
system, or both. Again, this checking in of the user or owner of
the user device takes in automatically without any affirmative
action by the user.
[0053] Additional process steps after checkin can then take place
as a result of the automatic checkin. For example, a next step 412
can involve detecting the user approaching, waiting in line, and/or
trying to pay at a register or other point of sale at the merchant
or other participating establishment. This step effectively detects
the previously checked in user device, which is now close to or in
the process of making a purchase or otherwise checking out. A
proper matching inquiry can take place at the register or point of
sale at decision step 414. This can involve a register, terminal or
bank of same or other point of sale devices detecting numerous
checked in user devices at or near a point of sale. One or more
automated, manual or mixed processes can then be used to make sure
that the right user is being charged for a given transaction, as
noted above.
[0054] In the event that a proper match cannot be made at step 414,
then the process can revert to process step 406 in order to checkin
the device and user in a manner that can be used. Once a proper
match (and recheckin, if necessary) is found or made at inquiry
414, then the method can continue to process step 416, where the
transaction can be completed, payment or credit can be had, and the
user can be checked out. The method then finishes at end step 418.
Further steps not depicted can include, for example, reviewing
signal strengths or other personal identifiers as part of the
proper matching process at step 414. Still further steps can
include providing offers or advertisements to the known user while
he or she is at the participating establishment, assessing for risk
in a possible transaction by the known user, extending credit
offers, or requiring a PIN or other personal identifier of the user
where certain transactions are determined to be more risky than
less risky ones. In the event of less risky transactions, a more
automated process can allow a user to check out and take goods
without any further need for identification, cash, cards, payment,
receipts or the like, in a very convenient and streamlined
fashion.
[0055] Turning lastly to FIG. 5, a flowchart of an exemplary method
of performing a handshake between a merchant dongle and a purchaser
mobile device on an unencrypted channel so as to facilitate a
payment or credit for a purchase according to some embodiments.
Again, such a method can involve using or operating a merchant
dongle, consumer smart phone, and/or any of the other various
computing components, devices, systems and/or networks described
above. It will again be readily appreciated that not every method
step set forth in this flowchart is always necessary, that further
steps not set forth herein may also be included, and/or that the
exact order of steps may be altered as desired for various
applications.
[0056] Beginning with a start step 1000, a first process step 1002
is made with respect to signing up a given user device to a remote
service provider, such as Paypal. This can involve installing an
application on the user device, registering the user, and
initializing the application with the registered user. At this
point, the device can then be given a set of advance one-time use
payment tokens and associated keys at process step 1004. In some
embodiments, the associated keys may include a pair of symmetric
keys. These user tokens can each have, for example, a user
identifier, a token value, a key serial number and an AES or other
crypto key, as will be readily appreciated by one of skill in the
art. Such user tokens can be assigned by a backend service provider
server, such as that which might be the remote service provider
noted above. At process step 1006, records of these assigned keys
and user tokens are stored on database(s) at the remote service
provider, such that it can be known to the provider who such a
token belongs to when it is put into use.
[0057] At a following process step 1008, one or more merchant
beacons can also be supplied with a digital signatures and merchant
one-time use tokens. Each check-in and possible purchase or other
transaction can then be tracked using a one-time token from both
the user device and a merchant beacon or beacon system that checks
in the user device. As in the case of the user device above, the
keys and tokens for the beacon are also assigned by and stored at
the remote service provider for later reference, which can be done
at process step 1010. The user device and beacon are now in
condition for communications, check-ins and transactions.
[0058] At a subsequent process step 1012, a generic UUID is
constantly broadcast from the beacon. This UUID is detected and
verified as issued by the same service provider by the user device
at process step 1014. The user device and beacon then initiate
communications, whereupon metadata, a specific one-time use beacon
token, and a digital signature can be sent from the beacon to the
user device at process step 1016. The application on the user
device can then certify the beacon token and verify the digital
signature as being issued by the service provider by using a public
key from the service provider at process step 1018. Assuming that
the beacon token sent over is authentic, the user device then
selects one of its assigned one-time use user tokens at process
step 1020.
[0059] At a following process step 1022, the user device then
encrypts both its user token value and the beacon token value
together using the key associated with the user token, and then
sends this encrypted value back to the beacon, where it is received
at process step 1024. Again, all of these communications between
the user device and the beacon can be on an unencrypted channel, as
any other outside device that might be listening or noting these
open communications will not know what to make of the token values
without any reference table that knows where those tokens were
assigned. In fact, the beacon itself does not know what to make of
the combined encrypted value. Rather, the beacon simply forwards
this value on a back channel to the remote service provider server
at process step 1026. The remote server knows what to do with these
values, since it has the details of where and to whom all tokens
were assigned in various tables or other storage mechanisms on its
database(s).
[0060] As such, the remote server decrypts the combined encrypted
value at process step 1028 and verifies the authenticity and
ownership of both the user token and the beacon (i.e., merchant)
token. The remote server then approves of the user device and
provides affirmative check-in instructions back to the beacon at
process step 1030. It is worth noting that while the communications
between the user device and the beacon over BLE are unencrypted,
the communications between the beacon and the remote server are on
a separate more protected channel. Neither the user device nor any
other device need see these communications between beacon and
remote server of the service provider. As the user device is then
checked in and the one time use tokens for the user device and
beacon are both committed to this checkin and any resulting
transaction, one or more new tokens can then be optionally provided
to the user device and/or the beacon at process step 1032. The
remote server then marks both of these tokens as used on its
databases at process step 1034, whereupon the "handshake" checkin
process or method then ends at end step 1036.
[0061] In various embodiments, many respective one-time use tokens
can be stored on each of the various user devices and/or beacons at
any given time. Selection of a given token from the pool of
possible tokens can then be random, which adds some layer of
protection from potential fraud or misuse. Further, the
requirements that each token be used one time only, and that the
combined encrypted token values be verified by the backend provider
server tends to prevent or reduce the possibility of token replay
or bit fiddling by unscrupulous persons who might otherwise try to
make something of the unencrypted and open communications over BLE
channels. Again, these tokens can be replenished one at a time as
they are used and discarded or otherwise rendered unusable, such as
by part of a check in process. Alternatively, or in addition, each
user device and/or beacon can also request more tokens from the
remote service provider server independently as needed.
[0062] Other safety mechanisms to provide better security can
include expiration dates on each token, as well as a requirement
that the user device be in constant communication with one or more
beacons at the merchant from checkin through any checkout and
purchase or other transaction. In the event that communications are
lost or dropped, then a new checkin with new tokens may be required
if desired for security purposes. Further, it is also worth noting
that the third party user device does not need to access the
private keys of any beacon. Rather, the public keys are all that
are necessary for the backend server to verify and authenticate
tokens for both the user device and the beacon for checkin and
later transaction. In some embodiments, there may be only one pair
of public and private keys for all beacons at all merchants, with
the private key being on the backend server, and the public key
being provided to the mobile device.
[0063] Although the foregoing embodiments have been described in
detail by way of illustration and example for purposes of clarity
and understanding, it will be recognized that the above described
embodiments may be embodied in numerous other specific variations
and embodiments without departing from the spirit or essential
characteristics of the disclosure. Various changes and
modifications may be practiced, and it is understood that the
disclosed embodiments are not to be limited by the foregoing
details, but rather is to be defined by the scope of the
claims.
* * * * *