Patent Description:
Device identification is provided. Consistent with embodiments, a user reads a device ID from a dispensing device (e.g., a beverage dispenser like a fountain or post-mix beverage dispenser, kiosk, ATM, point-of-sale device, etc.) wirelessly with a mobile computing device when the mobile computing device is placed in close proximity to the dispensing device. The mobile computing device may send the device ID along with a user ID to a server in a notification from the mobile computing device. Using the user ID, the server may look up user preferences from a table on the server. Consistent with embodiments, rather than looking the user preferences up on the server, the user preferences may be sent from the mobile computing device to the server. The server may send the user preferences to the dispensing device that corresponds to the device ID. In response, the dispensing device displays a customized user interface based upon the user preferences.

In one aspect, there is provided a method comprising: transmitting, by a dispensing device, a wireless signal from the dispensing device in close proximity to the dispensing device, the wireless signal including a device identification of the dispensing device; receiving, at the dispensing device, an event notification, the event notification associated with a mobile device that received the wireless signal in close proximity to the dispensing device; displaying, in response to the event notification, a customized user interface, the customized user interface based on preference data or profile data included in the event notification, the preference data or profile data associated with a user of the mobile device; directly connecting, by the dispensing device, via a first wireless connection with the mobile device, the first wireless connection configured to exchange data between the dispensing device and the mobile device; wherein the dispensing device comprises a first access point for establishing the first wireless connection; and sending, by the dispensing device, second connection data to the mobile device, the second connection data comprising credentials for establishing a second wireless connection with a second access point, wherein the credentials comprise a service set identifier of the second access point and a password for the second access point, and wherein the second wireless connection has a greater bandwidth than the first wireless connection.

In another aspect, there is provided a dispensing device comprising: a display configured to enable interaction with the dispensing device; a first wireless communication module configured to broadcast a wireless signal in close proximity to the dispensing device based on a first wireless communication protocol, wherein the wireless signal comprises a device identification of the dispensing device; a second communication module configured to receive an event notification associated with a mobile device that received the wireless signal in close proximity to the dispensing device; a memory storage; and a processing unit coupled to the memory storage, wherein the processing unit is operative to: display a customized user interface on the display, the customized user interface based on preference data or profile data included in the event notification, the preference data or profile data associated with a user of the mobile device; wherein the second communication module is an access point for a local area network communication module configured to directly connect the dispensing device with the mobile device via a first wireless connection, the first wireless connection configured to exchange data between the dispensing device and the mobile device; wherein the dispensing device is configured to send second connection data to the mobile device, the second connection data comprises credentials for establishing a second wireless connection with a second access point, wherein the credentials comprise a service set identifier of the second access point and a password for the second access point, and wherein the second wireless connection has a greater bandwidth than the first wireless connection.

In yet another aspect, there is provided a method comprising: receiving, by a mobile computing device, a device identification when the mobile computing device is in close proximity to a dispensing device; obtaining, by the mobile computing device, first connection data for connecting to the dispensing device based on the device identification; creating, by the mobile computing device, a first connection with the dispensing device based on the first connection data; transmitting, by the mobile computing device over the first connection, an event notification to the dispensing device, the event notification comprising preference data or profile data corresponding to a user of the mobile computing device; obtaining, by the mobile computing device from the dispensing device, second connection data for connecting to a server, the second connection data comprising credentials for establishing a second connection, wherein the credentials comprise a service set identifier and a password. and wherein the second connection has a greater bandwidth than the first connection; creating, by the mobile computing device, a second connection with the server; and receiving, by the mobile computing device over the second connection, promotional data.

In another example, a method may include: detecting, by a mobile computing device, a proximity of a beverage dispenser; accessing, by the mobile computing device, an application on the mobile computing device, the application having pre-loaded credentials; and using the pre-loaded credentials to establish a communication path with the beverage dispenser.

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar elements. While embodiments of the disclosure may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the disclosure. Instead, the proper scope of the disclosure is defined by the appended claims.

Users may wish to interact with dispensing devices in customized or personalized ways. Dispensing devices may include a beverage dispenser like a fountain or post-mix beverage dispenser, vending machine, kiosk, ATM, point-of-sale device, or other unattended electronic devices with which a consumer may desire personalized interaction. While the term dispensing device is used throughout the examples provided in this specification, it is intended that all the uses of this term also refer to other public interaction terminals or unattended interaction devices with which a consumer would want to have a customized user interaction or otherwise exchange data.

A user may use a corresponding mobile computing device to establish a personalized interaction with a dispensing device. Because a number of users may establish a line or sequence of users (i.e., a queue) awaiting their turn to interact with a dispensing devices, a queuing problem may come about. The queuing problem may be further exacerbated when there are multiple dispensing devices within a confined area, such as within wireless communication range using WiFi, WiFi Direct, Bluetooth, or Bluetooth Low Energy communications. For example, there may be confusion as to which user in the queue is currently addressing the dispensing device and wishes to establish a personalized interaction with the dispensing device.

That is, multiple users may be in wireless communication range of one or more dispensing devices and it may not be readily ascertainable which user is actually addressing a particular dispensing device. While the signal strength of wireless communications signals between one or more mobile devices and a dispensing device may provide an indication of how far away from each other they are, the signal strength may vary between users in a queue based on uncontrolled variables such as whether a consumer has their mobile device in their hand, pocket, purse, or other holder. Accordingly, it is desirable to implement device authentication in which a mobile computing device and a dispensing device may be paired to interact in a customized or personalized way.

Consistent with embodiments of the disclosure, device authentication may be provided. For example, a mobile computing device may read a device identification (ID) of a dispensing device (e.g., a beverage dispenser, kiosk, ATM, vending machine, or other unattended electronic device with which consumers may desire personalized interaction, etc.) wirelessly when the mobile computing device is placed in close proximity to the dispensing device. For example, close proximity may be within wireless communication range between the mobile device and the dispensing device. The device ID may be an ID that uniquely identifies the dispensing device. The device ID may be broadcast from the dispensing device. For example, the device ID may be transmitted periodically from the dispensing device like a beacon pinging out the device identification. In some embodiments, a BLUETOOTH or BLUETOOTH LOW ENERGY (BLE) beacon or other beacon device may broadcast the device ID. The device ID may be transmitted in a signal with such low energy that the signal may only be readable by a mobile computing device in close proximity to the dispensing device, for example within <NUM> to <NUM> inches of the dispensing device and preferably within <NUM> inches. In other words, the device ID may only be readable by the mobile computing device when the mobile computing device is placed in close proximity (e.g., approximately <NUM> inches or otherwise within <NUM> to <NUM> inches) to the dispensing device.

That is, the signal with the device ID may be transmitted no greater than about <NUM> to <NUM> inches, preferably no greater than <NUM> inches, from the dispensing device. As such, the mobile computing device is most probably associated with a consumer who is currently addressing the dispensing device as opposed to a consumer further back in the queue waiting to address the dispensing device or in a queue for an adjacent dispensing device. In other words, the beacon may purposefully be configured to limit the transmission range of the signal with the device ID to limit the possibility of multiple mobile computing devices in the queue from receiving the signal. For example, a Bluetooth beacon with a typical transmission range of <NUM> meters or more may be purposefully limited to only transmit a signal within <NUM> to <NUM> inches.

In some embodiments, a BLE beacon on the dispensing device is configured to broadcast a unique device ID of the dispensing device. The BLE beacon may be configured to limit the range of the broadcast of the device ID to the extent that a user would need to place their mobile device adjacent (such as within <NUM> to <NUM> inches, preferably <NUM> inches) to the BLE beacon on the dispensing device. Therefore, while BLE beacons are generally able to enable wireless communication with mobile devices within around <NUM>, the BLE beacon of the pending disclosure may be configured to purposefully limit the range so as to emulate a user experience similar to an NFC communication exchange.

In some embodiments, the range of the BLE beacon may be extended to within <NUM> to <NUM> inches of the dispensing device such that a user may keep their mobile device in their pocket, purse, or other holder and still be able to receive the signal with the unique device ID of the dispensing device. That is, the range of the wireless signal with the device ID may be transmitted no more than about <NUM> to <NUM> inches from the dispensing device. In such embodiments, the range may be set so that a mobile device of a user addressing the dispensing device is the most probable device to receive the signal with the unique ID of the dispensing device, as opposed to a mobile device of a user further back in the queue or a mobile device of a user at an adjacent dispensing device. In some embodiments, shielding in the dispensing device or beamforming of the signal with the unique ID of the dispensing device may further limit a mobile device of a user at an adjacent dispensing device from receiving the signal.

The mobile computing device may have an application installed that corresponds to the dispensing device. For example, the mobile computing device may have a beverage dispenser application installed that corresponds to a particular brand or model of beverage dispenser, such as the Coca-Cola Freestyle mobile application for facilitating communication with Coca-Cola Freestyle beverage dispensers from THE COCA-COLA COMPANY of Atlanta, Georgia. Under the control of the application on the mobile computing device, the mobile computing device may extract the device ID from the aforementioned low energy signal. Then the application on the mobile computing device may validate the device ID as being a valid device ID and authenticate the paring of the mobile computing device and the dispensing device to facilitate further personalized interaction with the dispensing device.

For example, a mobile device with a beverage dispenser mobile application installed may receive a signal with a unique device ID from a beverage dispenser. The beverage dispenser mobile application may examine the unique device ID to verify that the beverage dispenser is a valid beverage dispenser with which the beverage dispenser mobile application may communicate.

In some embodiments, the mobile application on the mobile computing device may determine that the unique device ID is from a valid dispensing device with which it may communicate based on examining the device ID as a whole or a portion thereof. The device ID of valid dispensing devices may have a common prefix, suffix, or other portion of the device ID that is common to all valid dispensing devices. For example, all beverage dispensers that are valid for personalized interactions with a user may have a common prefix in their device ID that identifies them as valid beverage dispenser. Upon a mobile device with a corresponding beverage dispenser application receiving the device ID, the beverage dispenser mobile application may determine that the device ID is valid based on the prefix in the device ID. The device ID may also include a unique identifier for the dispensing device. For example, a beverage dispenser device ID may include a prefix as described above as well as an identifier that is unique to that particular beverage dispenser.

Because the mobile computing device receives the signal with the device ID, it is determined that a user of the mobile device is currently addressing the dispensing device that broadcast the device ID. Additionally, because the application installed on the mobile device that corresponds to the dispensing device determines that the device ID is a valid device ID, the dispensing device and the mobile computing device may be authenticated for additional personalized interactions with each other. Accordingly, the mobile computing device and the dispensing device may be paired or a personalized interaction may be facilitated on the dispensing device as described in more detail below.

After the mobile computing device and the dispensing device are paired or the dispensing device otherwise engaged in a personalized interaction, no other mobile computing device may pair with or otherwise communicate with the dispensing device until the pairing is released. In some embodiments, the dispensing device may discontinue broadcasting the device ID while paired with the mobile device or otherwise engaged in a personalized interaction.

Once the mobile computing device and dispensing device are authenticated for interaction with each other, and in some embodiments are paired and ready for further interaction, the mobile computing device may send the device ID, or a portion thereof, along with a user ID to a server in a notification from the mobile computing device. The notification may be sent to the server from the mobile computing device over a network (e.g. the Internet, a cellular network, combinations thereof, etc.), via the mobile computing device's data plan for example. The device ID or portion thereof received by the server from the mobile computing device may uniquely identify the dispensing device. For example, when a prefix, suffix, or other portion of the device ID is common to multiple dispensing devices, such common portions of the device ID may not be communicated to the server. In other words, only portions of the device ID that uniquely identify the dispensing device may be communicated to the server.

Using the user ID, the server may look up user preferences or a user profile corresponding to a user of the mobile device from a table on the server. The server may send over a network (e.g., the Internet) the user preferences, the user profile, or portions thereof to the dispensing device that corresponds to the device ID or portion thereof. In response, the dispensing device may display a customized user interface or otherwise facilitate a personalized interaction with the user based upon the user preferences sent by the server.

Consistent with embodiments of the disclosure, rather than a personalized interaction being facilitated via the aforementioned server, the mobile computing device and the dispensing device may connect directly via a wireless connection (e.g., WiFi). In this case, rather than looking the user preferences up on the server, the user preferences may be sent directly from the mobile computing device to the dispensing device over the wireless connection. To facilitate the wireless connection, the dispensing device may include a wireless access point. Furthermore, in addition to the device ID, the aforementioned low energy signal may also include a service set identification (SSID) and a password for the access point included with dispensing device.

Alternatively, the application on the mobile computing device may already have the SSID and password for connecting to the access point on the dispensing device. For example, all dispensing devices associated with the application may have the same SSID and password. The common SSID and password for dispensing device access points may be stored in a database accessible to the application, either on the mobile device itself, such as in a directory associated with the application on the mobile device, or in a remote database accessed by the mobile device via a network connection, such as a cellular network, the Internet, etc..

Under the control of the application on the mobile computing device, mobile computing device may extract from the aforementioned low energy signal or otherwise obtain the SSID and the password. In such an example, the dispensing devices may use common pre-loaded credentials (i.e., the same SSID and password or a limited set thereof) so that the mobile computing device can connect to the dispensing devices using the credentials stored in the application.

The application can be programmed to identify or otherwise detect when a dispensing device is within proximity of the mobile electronic device and automatically establish a communication path therebetween using the credentials. In the event multiple dispensing devices are located in close proximity, each of the dispensing devices can user one of a limited set of credentials. The application can be programmed to determine which of the dispensing devices has the most robust connection characteristics (e.g., highest signal strength) and automatically establish a connection therebetween. To accomplish this connection, the application can be programmed to select among the limited set of credentials and/or cycle through the limited set of credentials until a communication path is established with the selected beverage dispenser. Other configurations are possible.

Alternatively, upon the mobile computing device being authenticated for further interaction with the dispensing device, the mobile application may provide the SSID and password. Using the SSID and the password, the mobile computing device may connect directly via a wireless connection established with the dispensing device. The mobile computing device may send, over the established wireless connection, the user preferences to the dispensing device. In response, the dispensing device may display a customized user interface based upon the user preferences sent by mobile computing device.

Other data may be communicated between the mobile device and the dispensing device, such as order data (e.g., order identifier information, one or more product selections associated with a particular order, etc.), payment data (e.g., credit card information, payment token information, etc.), display data (e.g., data that is provided from the mobile device to be displayed on the dispenser such as picture data, customized display settings, etc.), selection data (e.g., selections of one or more products to be dispensed, etc.), and commands (e.g., using the mobile device as a remote to provide commands directly to the dispensing device for controlling the operation of the dispensing device).

Further, other communication paths could be used to communicate preference or profile data to the dispensing device, such as via an electronic mail address associated with the dispensing device (similar to how some networked printers work).

In other embodiments consistent with embodiments of the disclosure, another wireless connection may be established in addition to the wireless connection between the mobile computing device and the dispensing device. This other wireless connection may have greater bandwidth than the wireless connection between the mobile computing device and the dispensing device. For example, rather than or in addition to connecting to an access point in the dispensing device, the mobile computing device may connect to a second access point provided, for example, by a retail outlet in which the dispensing device is disposed.

For example, the dispensing device may be within transmission range of the second access point. Upon configuring the dispensing device to operate in the retail outlet, the dispensing device may be provided with the SSID and password for the second access point. The mobile computing device may obtain, from the dispensing device or elsewhere, a SSID and a password for the second access point provided by the retail outlet. In some embodiments, the mobile communication device may establish a communication session with the dispensing device via the first access point as described above. The dispensing device may then pass the SSID and password or other credentials for accessing the second access point to the application on the mobile device. The communication session between the dispensing device and the mobile device may then be closed The mobile computing device may then use the credentials provided by the dispensing device to establish another wireless connection; this time with the second access point provided, for example, by the retail outlet in which the dispensing device is disposed.

<FIG> shows a network architecture <NUM> for facilitating an individualized interaction between a mobile computing device and an electronic device. As shown in <FIG>, network architecture <NUM> may include a mobile computing device <NUM>, a dispensing device <NUM>, and a server <NUM>. Mobile computing device <NUM> may be utilized by a user <NUM> and may be in communication with dispensing device <NUM> and server <NUM>. The aforementioned network architecture for facilitating an individualized interaction between a mobile computing device and an electronic device may be described in related patent application <CIT>, the disclosure of which is incorporated herein, in its entirety, by reference.

Computing device <NUM> may include a computing device application <NUM>, a user ID <NUM>, preference data <NUM>, a scanner/camera <NUM>, a mobile computing device wireless interface <NUM>, and a near field communication (NFC) reader <NUM>. Computing device <NUM> may comprise, but is not limited to, a smartphone, a tablet computer, or a laptop computer that may be capable of executing one or more software application programs, such as application <NUM>. Computing device <NUM> may be practiced in a computing environment <NUM> described below with respect to <FIG>.

Dispensing device <NUM> may comprise a dispensing device wireless interface <NUM> and a display <NUM> that may provide personalized content <NUM>. Dispensing device <NUM> may further comprise a device ID <NUM>, a dispensing device application <NUM>, an NFC tag <NUM>, and a bar code <NUM>. Bar code <NUM> may comprise any machine-readable object (e.g., one-dimensional (<NUM>-D) or two-dimensional (<NUM>-D)) that may provide data relating to dispensing device <NUM>. Bar code <NUM> may be displayed on display <NUM>. Dispensing device <NUM> may be practiced in an operating environment such as an electronic device <NUM> as described with respect to <FIG>.

Server <NUM> may comprise a server application <NUM> and a table or database <NUM>. Table <NUM> may store preference data <NUM> related to user ID <NUM>. Server <NUM> may be practiced in an operating environment such as electronic device <NUM> as described with respect to <FIG>.

Scanner/camera <NUM> and may be capable of short range wireless communication via wireless interface <NUM>. Wireless interface <NUM> may be configured to provide short range wireless communications (e.g., <NUM>-<NUM> inches, more preferably less than <NUM> inches) via, but not limited to, NFC, BLUETOOTH wireless technology, BLUETOOH LOW ENERGY (BLE) wireless technology, and Wi-Fi. Preference data <NUM> may also be stored on server <NUM> or in a database accessible via server <NUM> and cross-referenced (e.g., via table <NUM>) with user ID <NUM>. User ID <NUM> may comprise an ID for user <NUM> of mobile computing device <NUM>. Preference data <NUM> may comprise preferences associated with user <NUM>. For example, preference data <NUM> may comprise a list of user <NUM>'s favorite beverages, games, products, and/or restaurants, a list of user <NUM>'s custom beverage mixes, and/or other information that can be used to personalize user <NUM>'s interaction with dispensing device <NUM>.

Application <NUM> may be configured to send user ID <NUM> and preference data <NUM> along with device ID <NUM> (e.g., retrieved from dispensing device <NUM>) in a notification <NUM> to server <NUM> for conducting an individualized or unique interaction with dispensing device <NUM>. Notification <NUM> may only include user ID <NUM> and device ID <NUM>. Upon receipt of device ID <NUM> and user ID <NUM>, server <NUM> may obtain and communicate preference data <NUM> (e.g., or a subset thereof) to dispensing device <NUM>.

Upon receiving device ID <NUM>, server <NUM> may determine that mobile computing device <NUM> (and hence user <NUM> of mobile computing device <NUM>) may be proximate to dispensing device <NUM>. Depending on how device ID <NUM> is obtained (e.g., scanning a barcode from dispensing device <NUM>, reading an NFC tag associated with dispensing device <NUM>, or receiving a BLUETOOH LOW ENERGY (BLE) wireless technology signal associated with dispensing device <NUM>), server <NUM> may further determine that user <NUM> is addressing or is otherwise ready to commence interaction with dispensing device <NUM>. This may be opposed to user <NUM> being in line to use dispensing device <NUM>, but not yet being ready to commence interaction with dispensing device <NUM>.

Device ID <NUM> may be retrieved without establishing a communication session between mobile computing device <NUM> and dispensing device <NUM>. For example, device ID <NUM> may be retrieved by using scanner/camera <NUM> in conjunction with application <NUM> to scan a barcode (e.g., a <NUM>-D or <NUM>-D barcode) or other symbol encoded with device ID <NUM> on dispensing device <NUM> (or displayed on display <NUM>). In other words, the barcode or other symbol may be rendered on display <NUM> of dispensing device <NUM>, or printed, embossed, shown on a sticker, or otherwise made visible on one or more surfaces of dispensing device <NUM>.

Device ID <NUM> may be retrieved by NFC reader <NUM> reading device ID <NUM> from NFC tag <NUM>. NFC tag <NUM> may be a passive or an active NFC tag that may store device ID <NUM>. NFC tag <NUM> may comprise an RFID tag where the ID associated with the RFID tag may comprise device ID <NUM>. NFC tag <NUM> may be placed inside a cabinet containing dispensing device <NUM> at a location such that NFC reader <NUM> on mobile computing device <NUM> may still read NFC tag <NUM>. By placing NFC tag <NUM> inside the cabinet, NFC tag <NUM> may be protected from tampering.

Device ID <NUM> may be retrieved by initiating a communication session between mobile computing device <NUM> and dispensing device <NUM>. For example, mobile computing device <NUM> may communicate via a wireless communication session (e.g., between mobile computing device wireless interface <NUM> and dispensing device wireless interface <NUM>) with dispensing device <NUM> using BLUETOOTH wireless technology, BLUETOOH LOW ENERGY (BLE) wireless technology, Wi-Fi or other wireless communication standards or technologies.

Consistent with embodiments, preference data <NUM> may be communicated directly from mobile computing device <NUM> to dispensing device <NUM> via a communications session between mobile computing device wireless interface <NUM> and dispensing device wireless interface <NUM>. For example, application <NUM> may pass preference data <NUM> to application <NUM> upon establishment of a communications session. Dispensing device <NUM> may comprise a computing device capable of executing one or more software application programs such as application <NUM>. Dispensing device <NUM> may also be configured to provide any number of consumer services and/or products, including, without limitation, the dispensing of food and/or beverage products, video gaming services, video services, advertisement services, financial services, etc. Dispensing device <NUM> may include fountain or post-mix beverage dispensing machines, vending machines, public gaming devices, automated teller machines or any other electronic device or kiosk configured to provide consumer products and/or services.

Similar to wireless interface <NUM> in mobile computing device <NUM>, wireless interface <NUM> in dispensing device <NUM> may be configured to provide short range wireless communications via NFC, BLUETOOTH wireless technology, BLUETOOH LOW ENERGY (BLE) wireless technology, Wi-Fi or other wireless technologies. Dispensing device <NUM> may be utilized to display personalized content <NUM> to user <NUM> based on preference data <NUM>. For example, personalized content <NUM> may include a selection of user <NUM>'s favorite beverages that may be available for purchase, advertisements targeted towards user <NUM>'s favorite products, etc..

Device ID <NUM> may comprise a unique identification of dispensing device <NUM>. Device ID <NUM> may be utilized for identifying dispensing device <NUM> among other similar devices in a network. Application <NUM> may be configured to send device ID <NUM> to mobile computing device <NUM> in response to a communication session initiated by user <NUM>. As discussed above, the communication session may comprise a short range wireless communication session during which device ID <NUM> may be sent to mobile computing device <NUM>. For example, device ID <NUM> may be encoded in an unpowered NFC tag <NUM> that may be affixed to dispensing device <NUM>. Device ID <NUM> may be communicated when user <NUM> touches or brings mobile computing device <NUM> in close proximity with NFC tag <NUM> or when a BLUETOOH LOW ENERGY (BLE) wireless technology signal is read from dispensing device <NUM>.

Device ID <NUM> may comprise stored data on dispensing device <NUM> and may be communicated in response to a data request made by user <NUM> during a Wi-Fi, or BLUETOOTH wireless technology session, or a BLUETOOH LOW ENERGY (BLE) wireless technology session with mobile computing device <NUM>. In addition, the communication session may comprise a scanning session initiated by user <NUM>. For example, device ID <NUM> may be encoded in a <NUM>-D or <NUM>-D barcode (e.g., a QR code) or other symbol that may be either physically affixed to dispensing device <NUM> or displayed by dispensing device <NUM> on display <NUM>.

Application <NUM>, executing on dispensing device <NUM>, may be configured to receive an event notification <NUM> from server <NUM>. Event notification <NUM> may include, for example, user ID <NUM> and preference data <NUM>. Event notification <NUM> may be sent after user ID <NUM>, device ID <NUM>, and preference data <NUM> are received by server <NUM>. Communication between application <NUM> on dispensing device <NUM> and application <NUM> on server <NUM> may be configured to utilize a server push technique in which a communication session (i.e., a server push <NUM>) may be initiated and established by dispensing device <NUM> prior to user <NUM>'s interaction with dispensing device <NUM>. Server push technology may include, but is not limited to, long polling, Comet, web sockets or Berkeley socket ("BSD") techniques. Server <NUM> may hold the sending of a response to data requests from dispensing device <NUM> until the requested data is available or a predetermined timeout event has occurred. Upon user ID <NUM> and preference data <NUM> being received by dispensing device <NUM>, application <NUM> may be configured to display personalized content <NUM> for user <NUM> on display <NUM>.

Server <NUM>, which may be in communication with mobile computing device <NUM> and dispensing device <NUM>, may comprise a computing device capable of executing one or more software application programs such as application <NUM>. Communication between server <NUM>, mobile computing device <NUM>, and dispensing device <NUM> may take place via respective device network connections (not shown) over a wide area network, such as the Internet. Server <NUM> may comprise a non-blocking socket input/output server platform that may utilize a server push technology (e.g., long polling or web sockets) where dispensing device <NUM> may initiate a network connection (e.g., server push <NUM>) with server <NUM> and keeps it open.

An example of a non-blocking socket input/output server platform may comprise the ELASTIC COMPUTE CLOUD ("EC2") web service (that may comprise an "infrastructure as a service" cloud computing platform) provided by AMAZON. of Seattle, Washington. The EC2 web service may further be utilized with Tornado that may comprise an open source scalable, non-blocking web server and web application framework. Embodiments of the disclosure may also be practiced in conjunction with other non-blocking socket servers and/or platforms from other providers and further, is not limited to any particular application, system, or platform.

Application <NUM> may be configured to receive user ID <NUM> and preference data <NUM> contained in notification <NUM> from mobile computing device <NUM> via an HTTP Application Programming Interface ("API"). Application <NUM> may receive user ID <NUM> and use table <NUM> to look up corresponding preference data <NUM>. Application <NUM> may further be configured to server push communications to dispensing device <NUM>. Application <NUM> may also be configured to delay the sending of responses to the HTTP requests from dispensing device <NUM> until the occurrence of one of a timeout or the receipt of notification <NUM>.

<FIG> shows network architecture <NUM> for facilitating an individualized interaction between mobile computing device <NUM> and dispensing device <NUM>. Network architecture <NUM> includes mobile computing device <NUM> including user ID <NUM> and, optionally, preference data <NUM>. Mobile computing device <NUM> may be in active communication with dispensing device <NUM> via BLUETOOTH wireless technology, BLUETOOH LOW ENERGY (BLE) wireless technology, Wi-Fi, or other wireless standards or technologies. Dispensing device <NUM>, which may store device ID <NUM>, may receive user ID <NUM> (and optionally, preference data <NUM>) from mobile computing device <NUM>. Dispensing device <NUM> may then send device ID <NUM> to server <NUM> and receive optional preference data <NUM> from server <NUM>. Server <NUM> may store table <NUM> that may include one or more user IDs <NUM> and, optionally, one or more instances of preference data <NUM>. As discussed above with respect to <FIG>, preference data <NUM> may be cross-referenced (e.g., via table <NUM>) with user ID <NUM>.

<FIG> shows a dispensing device <NUM>. Dispensing device <NUM> may comprise, but is not limited to, dispensing device <NUM>. As shown in <FIG>, dispensing device <NUM> may comprise various beverage bases or beverage base components such as beverage bases <NUM>, <NUM>, <NUM>, and <NUM> as well as flavors (i.e., flavoring agents, flavor concentrates, or flavor syrups) <NUM>, <NUM>, <NUM>, and <NUM>. Dispensing device <NUM> may further comprise other ingredients <NUM>, an application <NUM>, and a graphical user interface (GUI) <NUM>. The aforementioned dispensing device may be described in related patent application <CIT>, the disclosure of which is incorporated herein, in its entirety, by reference.

Beverage bases <NUM>, <NUM>, <NUM>, and <NUM> may be concentrated syrups. Beverage bases <NUM>, <NUM>, <NUM>, and <NUM> may be replaced with or additionally provided with beverage base components. Each of beverage bases <NUM>, <NUM>, <NUM>, and <NUM> or beverage base components and each of flavors <NUM>, <NUM>, <NUM>, and <NUM> may be separately stored or otherwise contained in individual removable cartridges that may be stored in dispensing device <NUM>.

Dispensing device <NUM> may identify the cartridges upon installation by a user or the user may be prompted to identify the cartridges when they are installed. The aforementioned beverage components (i.e., beverage bases or beverage base components and flavors) may be combined, along with other beverage ingredients <NUM>, to dispense various beverages or blended beverages (i.e., finished beverage products) from dispensing device <NUM>. Dispensing device <NUM> may also be configured to dispense beverage components individually. Dispensing device <NUM> may be configured to dispense beverage base components to form a beverage base. Other ingredients <NUM> may include diluents such as still or carbonated water, functional additives, or medicaments, for example. Other ingredients <NUM> may be installed in dispensing device <NUM>, pumped to dispensing device <NUM>, or both. The carbonated water may be produced in dispensing device <NUM> through mixing of CO<NUM> and still water such as in a carbonator or other device that produces carbonated water.

Application <NUM> may be configured to generate GUI <NUM> on a display screen (not shown) of the dispensing device <NUM>. GUI <NUM> may be utilized to select and individually dispense one or more beverages from dispensing device <NUM>. The beverages may be dispensed as beverage components in a continuous pour operation where one or more selected beverage components continue to be dispensed while a pour input is actuated by a user or in a batch pour operation whereby a predetermined volume of one or more selected beverage components are dispensed (e.g., one ounce at a time).

GUI <NUM> on dispensing device <NUM> may be addressed via a number of methods to select and dispense beverages. For example, the user may interact with GUI <NUM> via touch input to navigate one or more menus from which to select and dispense a beverage. As another example, the user may type in a code using an onscreen or physical keyboard (not shown) on dispensing device <NUM> to navigate one or more menus from which to select and dispense a beverage. As yet another example, the user (e.g., user <NUM>) may use mobile computing device <NUM> to scan a one or two-dimensional barcode (e.g., a QR code) or other symbol shown on a tag or sticker affixed to, printed on dispensing device <NUM> or displayed on a display (e.g., GUI <NUM>) of the dispensing device <NUM> to select a beverage for dispensing.

<FIG> is a flow chart setting forth the general stages involved in a method <NUM> consistent with an embodiment of the disclosure for providing device authentication. Method <NUM> may be implemented using network architecture <NUM> as described above with respect to <FIG>, <FIG>, and <FIG>. Ways to implement the stages of method <NUM> will be described in greater detail below.

Method <NUM> may begin at starting block <NUM> and proceed to stage <NUM> where dispensing device <NUM> may provide device identification <NUM>. Application <NUM> may display a user interface <NUM> on display <NUM>. As shown in <FIG>, user interface <NUM> may be utilized for selecting a menu associated with different product categories that may be dispensed from dispensing device <NUM>. User interface <NUM> may include a main menu of product categories <NUM>, <NUM>, <NUM>, <NUM> and <NUM> that may be selected by user <NUM>. Each of the aforementioned categories may correspond to various product categories such as all of a number of beverage brands available on dispensing device <NUM> (e.g., product category <NUM>), a caffeine-free beverage category (e.g., product category <NUM>), a featured category associated with beverages tied to one or more promotional or advertising campaigns (e.g., product category <NUM>), a flavor category in which beverages are organized corresponding to a particular fruit flavor or other particular flavor additive available on dispensing device <NUM> (e.g., product category <NUM>), and a low-calorie beverage category (e.g., product category <NUM>).

User interface <NUM> may also include a Help user control <NUM> that may be selected by user <NUM> to review instructions for selecting and dispensing a product from dispensing device <NUM>. User interface <NUM> may also include a language toggle user control <NUM> that may be selected by user <NUM> to change the language utilized. User interface <NUM> may also include a bar code <NUM> that may comprise a one or two-dimensional barcode (e.g., a QR code) or other symbol that may be utilized by user <NUM> to uniquely identify dispensing device <NUM> so as to enable a customized interaction or enable user <NUM> to remotely access dispensing device <NUM> from mobile computing device <NUM>. The aforementioned consumer customized interactions and remote access tasks are described in related patent application <CIT>, the disclosure of which is incorporated herein, in its entirety, by reference. User interface <NUM> may also include a user control <NUM> for directly accessing a product (e.g., water) from the main menu of product categories <NUM>-<NUM>. User control <NUM> may be utilized by a consumer who only wishes to quickly dispense a product without having to navigate through one or more of product categories <NUM>-<NUM>.

Consistent with embodiments of the disclosure, dispensing device <NUM> may transmit a wireless signal including device identification <NUM>. The wireless signal may comprise, but is not limited to, a Bluetooth low energy (BLE) signal. The wireless signal may be utilized by mobile computing device <NUM> to uniquely identify dispensing device <NUM> so as to enable a customized interaction or enable user <NUM> to remotely access dispensing device <NUM> from mobile computing device <NUM>. The wireless signal may comprise a low energy signal and may only be readable when a receiver (e.g., mobile computing device <NUM>) is in close proximity. For example, the wireless signal may only be readable by mobile computing device <NUM> when mobile computing device <NUM> is placed in close proximity (e.g., approximately <NUM> inches or otherwise within <NUM> to <NUM> inches, or the range of the BLE beacon may be extended to within <NUM> to <NUM> inches in some embodiments) to display <NUM>. This may eliminate the aforementioned queuing problem. The wireless signal, including device identification <NUM>, may be transmitted periodically, for example, like a beacon pinging out device identification <NUM>.

From stage <NUM>, where dispensing device <NUM> provides device identification <NUM>, method <NUM> may advance to stage <NUM> where dispensing device <NUM> may receive an event notification (e.g., event notification <NUM>) based upon provided device identification <NUM>. For example, user <NUM> may cause application <NUM> to execute on mobile computing device <NUM>. As a result, application <NUM> may cause a user interface <NUM> to be displayed on mobile computing device <NUM> as shown in <FIG>. User interface <NUM> may include a plurality of user options including, but not limited to, a connect option <NUM>.

From user interface <NUM>, user <NUM> may select connect option <NUM>. In response to user <NUM> selecting connect option <NUM>, application <NUM> may cause wireless interface <NUM> on mobile computing device <NUM> to seek the wireless signal (e.g., including device ID <NUM>) being transmitted by wireless interface <NUM> on dispensing device <NUM>. Mobile computing device <NUM> may receive the wireless signal including device ID <NUM> when mobile computing device <NUM> is placed in close proximity to dispensing device <NUM>. The wireless signal may comprise a low energy signal and may only be readable when a receiver (e.g., mobile computing device <NUM>) is in close proximity to, for example, display <NUM>.

Consistent with embodiments of the disclosure, dispensing device <NUM> may comprise a machine (e.g., a beverage dispensing machine) that user <NUM> wishes to have customized interaction with. Accordingly, user <NUM> may place mobile computing device <NUM> within a few inches of display <NUM>. As a result, mobile computing device <NUM> may receive the wireless signal including device ID <NUM>. Device ID <NUM> may uniquely identify dispensing device <NUM> or may just indicate a particular device type that dispensing device <NUM> comprises.

If device ID <NUM> just indicates a particular device type that dispensing device <NUM> comprises, location data (e.g., Global Position System (GPS) coordinates) of dispensing device <NUM> may also be used to uniquely identify dispensing device <NUM>. The location data may be created by mobile computing device <NUM> when it is near dispensing device <NUM> or may be received by mobile computing device <NUM> from dispensing device <NUM>. However, when dispensing device <NUM> is within a bank of similar devices (e.g., beverage dispensers), device ID <NUM> uniquely identify dispensing device <NUM> (rather than just it's type) may be used because the aforementioned location data (e.g., GPS coordinates) may not be granular enough to distinguish the devices within the bank.

Once the wireless signal is received, application <NUM> may process the wireless signal to extract device ID <NUM> from the wireless signal. As described above with respect to <FIG>, in response, mobile computing device <NUM> may send notification <NUM> to server <NUM> that may in turn send event notification <NUM> to dispensing device <NUM>. As stated above, event notification <NUM> may include user ID <NUM> and preference data <NUM>.

As shown in <FIG>, rather than going through server <NUM>, mobile computing device <NUM> may provide event notification <NUM> directly to dispensing device <NUM>. This may be accomplished over a two-way wireless connection (e.g., Wi-Fi) established between mobile computing device <NUM> and dispensing device <NUM> as illustrated by flow diagram <NUM> of <FIG>.

Mobile computing device <NUM> may obtain, for example, first connection data for connecting to dispensing device <NUM> from the low energy signal that provide received device ID <NUM>. (Stage <NUM>. ) For example, the first connection data may be embedded in the received device ID <NUM> and may comprise a service set identification (SSID) and a password for an access point associated with dispensing device <NUM> (e.g., wireless interface <NUM>). As described above, the device identification may be obtained by mobile computing device <NUM> when mobile computing device <NUM> is placed in close proximity (e.g., approximately <NUM> inches or otherwise within <NUM> to <NUM> inches) to display <NUM> of dispensing device <NUM>.

Using the first connection data, mobile computing device <NUM> may create (i.e., establish) the first connection with dispensing device <NUM> directly as shown in <FIG> without going through server <NUM> as shown in <FIG>. (Stage <NUM>. ) Once the first connection is established, mobile computing device <NUM> may transmit over the established first connection, event notification <NUM> to dispensing device <NUM>. (Stage <NUM>. ) Mobile computing device <NUM> may create event notification <NUM> comprising, for example, preference data <NUM> stored on mobile computing device <NUM>. In this way, event notification <NUM> may be provided directly to dispensing device <NUM> from mobile computing device <NUM> rather than going through server <NUM>. The event notification <NUM> may be provided directly over the two-way wireless connection (e.g., the first connection) established between mobile computing device <NUM> and dispensing device <NUM>.

Furthermore, an enterprise controlling dispensing device <NUM> may wish to provide a data file (e.g., promotional data) to mobile computing device <NUM> in response to user <NUM>'s customized interaction with dispensing device <NUM>. For example, dispensing device <NUM> may comprise a beverage dispenser and user <NUM> may have interacted with a customized user interface <NUM> (as described below) to cause dispensing device <NUM> to dispense a beverage. As a result, the enterprise controlling dispensing device <NUM> may wish to provide mobile computing device <NUM> with promotional data correspond to an advertisement (e.g., a video) relevant to the dispensed beverage. However, the first connection described above with respect to <FIG> may not have enough bandwidth for the promotional data and dispensing device <NUM> may not have capacity for the promotional data.

As shown in <FIG>, consistent with embodiments of the disclosure, a second connection may be established that may have greater bandwidth than the first connection. For example, rather than (or in addition to) connecting to an access point in dispensing device <NUM> to obtain the aforementioned promotional data, mobile computing device <NUM> may connect to an access point <NUM> as illustrated by flow diagram <NUM> of <FIG>. Access point <NUM> may be provided, for example, by a retail outlet in which dispensing device <NUM> is disposed.

Mobile computing device <NUM> may obtain, from dispensing device <NUM>, second connection data (stage <NUM>) for connecting to access point <NUM> provided by the retail outlet and use access point <NUM> to communicate with server <NUM> over a network <NUM> (e.g., the Internet). The second connection data may comprise an SSID and a password for access point <NUM> provided by the retail outlet. For example, the second connection data may be embedded in received device ID <NUM>. As described above, the device identification may be obtained by mobile computing device <NUM> when mobile computing device <NUM> is placed in close proximity (e.g., approximately <NUM> inches or otherwise within <NUM> to <NUM> inches) to display <NUM> of dispensing device <NUM>. Alternatively, the second connection data may be obtained by mobile computing device <NUM> from dispensing device <NUM> over the first connection after authenticating the mobile computing device <NUM> for further interaction with the dispensing device <NUM>. Mobile computing device <NUM> may receive the second connection data from other sources and is not limited to receiving the second connection data from dispensing device <NUM>.

Mobile computing device <NUM> may then establish the second connection with access point <NUM> using the obtained second connection data. (Stage <NUM>. ) By connecting to access point <NUM> provided by the retail outlet, mobile computing device <NUM> may use access point <NUM> to get to server <NUM> over network <NUM> through the establish the second connection. Mobile computing device <NUM> may then receive the promotional data from server <NUM> over the established second connection (stage <NUM>. ) Mobile computing device <NUM> may receive the promotional data from other sources over the second connection and is not limited to receiving the promotional data from server <NUM>.

Once dispensing device <NUM> receives event notification <NUM> based upon provided device identification <NUM> in stage <NUM>, method <NUM> may continue to stage <NUM> where dispensing device <NUM> may display, in response to receiving event notification <NUM>, customized user interface <NUM> on display <NUM> as shown in <FIG>. Customized user interface <NUM> may comprise a limited time offer (LTO) section <NUM>. Limited time offer section <NUM> may be based on received event notification <NUM>. Consistent with embodiments of the disclosure, limited time offer section <NUM> may only be displayed within customized user interface <NUM> when individualized interaction between mobile computing device <NUM> and dispensing device <NUM> has been established as described above with respect to <FIG>.

In addition to limited time offer section <NUM>, customized user interface <NUM> may comprise a custom mixes section <NUM>, a favorites section <NUM>, and a recommended section <NUM>. Each of limited time offer section <NUM>, custom mixes section <NUM>, favorites section <NUM>, and recommended section <NUM> may include one or more user selectable elements, when selected by user <NUM>, may cause dispensing device to dispense a beverage that may correspond to the selected user selectable element.

User selectable elements in limited time offer section <NUM> may correspond to beverages, brands, or beverage recipes that may be designated by an operator of dispensing device <NUM>. User selectable elements in limited time offer section <NUM> may correspond to beverages that may or may not comprise brand offerings. User selectable elements in limited time offer section <NUM> may correspond to mixes of one or more brand offerings, beverage bases, beverage base components, flavors, diluents, and/or sweeteners. For example, the operator of dispensing device <NUM> may comprise a movie theater that is promoting a particular movie. Consequently, a user selectable element in limited time offer section <NUM> may correspond to a beverage related to the promoted movie. In particular, a user selectable element in limited time offer section <NUM> may correspond to a beverage related to a beverage consumed in the promoted movie. As another example, the operator of dispensing device <NUM> may comprise a restaurant that is promoting a particular food offering. Consequently, a user selectable element in limited time offer section <NUM> may correspond to a beverage related to the promoted food offering. In particular, a user selectable element in limited time offer section <NUM> may correspond to a beverage that may enhance or otherwise be related to the promoted food offering.

User selectable elements in custom mixes section <NUM> may correspond to beverage recipes that user <NUM> may have designed or otherwise obtained. In other words, user selectable elements in custom mixes section <NUM> may correspond to beverages that may not comprise brand offerings, but may comprise mixes of one or more brand offerings, beverage bases, beverage base components, flavors, diluents, and/or sweeteners. Recipes for beverages displayed in custom mixes <NUM> may be stored and obtained by dispensing device <NUM> from preference data <NUM>.

User selectable elements in favorites section <NUM> may correspond to brand beverage offerings that user <NUM> may select most often or has other wise designated as favorite beverages. The identification of beverages displayed in favorites section <NUM> may be stored in preference data <NUM>.

User selectable elements in recommended section <NUM> may correspond to beverage offerings that an operator of a dispensing device wishes to offer or otherwise suggest that user <NUM> consume. The recommended beverage offerings corresponding to recommended section <NUM> may be determined or otherwise calculated based upon user <NUM>'s custom mixes and favorites identified in preference data <NUM>. For example, application <NUM> (running on dispensing device <NUM>) or application <NUM> (running on server <NUM>) may run a recommendation process that may calculate beverage recommendations for recommended section <NUM> based upon user <NUM>'s preference data <NUM> (e.g., user <NUM>'s custom mixes and/or favorites). After dispensing device <NUM> displays, in response to receiving event notification <NUM>, customized user interface <NUM> in stage <NUM>, method <NUM> may then end at stage <NUM>.

Consistent with embodiments of the disclose, the operator of dispensing device <NUM> may be able to select when customized user interface <NUM> may be displayed on display <NUM> and/or which sections of user interface <NUM> may be displayed on display <NUM>. For example, the choices provided by customized user interface <NUM> my cause potential users of dispensing device <NUM> to backup and have to wait. This may cause business issues for the operator of dispensing device <NUM> who may wish to turn off the ability for dispensing device <NUM> to provide customized user interface <NUM>. Or the operator of dispensing device <NUM> may wish to turn off the ability for dispensing device <NUM> to provide customized user interface <NUM> during certain time periods and to turn on the ability for dispensing device <NUM> to provide customized user interface <NUM> during other time periods. For example, for on-peak time periods, the operator may wish to turn off customized user interface <NUM> in order to improve operational efficiency. However, during off-pear time periods, the operator may wish to turn on customized user interface <NUM> because it may drive business in because consumers may wish to engage with customized user interface <NUM>.

<FIG> shows a control architecture <NUM> that may be used to control, for example, dispensing device <NUM> of <FIG>. As shown in <FIG>, control architecture <NUM> may comprise a core dispense module (CDM) <NUM>, a human machine interface (HMI) module <NUM>, a user interface (UI) <NUM>, and a machine bus (MBUS) <NUM>. HMI <NUM> may connect to or otherwise interface and communicate with at least one external device (e.g., mobile computing device <NUM>) being external to dispensing device <NUM>. HMI <NUM> may also control and update display screens on UI <NUM>. CDM <NUM> may control flows from a plurality of pumps and/or valves <NUM> in dispensing device <NUM> according to a recipe to mix and dispense a product (e.g., a beverage) from dispensing device <NUM>.

Beverage components (i.e., beverage bases or beverage base components and flavors) may be combined, along with other ingredients, to dispense various products that may include beverages or blended beverages (i.e., finished beverage products) from dispensing device <NUM>. However, dispensing device <NUM> may also be configured to dispense beverage components individually. Dispensing device <NUM> may be configured to dispense beverage base components to form a beverage base or finished beverage. The other beverage ingredients may include diluents such as still or carbonated water, functional additives, or medicaments, for example.

An example of control architecture <NUM> for dispensing device <NUM> may be described in <CIT>, the entirety of which is hereby incorporated by reference. MBUS <NUM> may facilitate communication between HMI module <NUM> and CDM <NUM>. HMI module <NUM>, MBUS <NUM>, and CDM <NUM> may collectively comprise common core components, implemented as hardware or as combination of hardware and software, which may be adapted to provide customized functionality in dispensing device <NUM>. Dispensing device <NUM> may further include memory storage and a processor. Examples of UI <NUM> may be described in <CIT>, the entirety of which is hereby incorporated by reference.

UI <NUM> may detect what area of a touch screen has been touched by a user (e.g., user <NUM>). In response, UI <NUM> may send HMI module <NUM> data regarding where the touch screen was touched. In response, HMI module <NUM> may interpret this received data to determine whether to have UI <NUM> display a different UI screen or to issue a command to CDM <NUM>. For example, HMI module <NUM> may determine that the user touched a portion of the touch screen corresponding to a beverage brand. In response, HMI module <NUM> may issue a command to CDM <NUM> to pour the corresponding beverage brand. Or HMI module <NUM> may determine that the user touched a portion of the touch screen corresponding to a request for another screen. In response, HMI module <NUM> may cause UI <NUM> to display the requested screen.

In some embodiments, UI <NUM> in dispensing device <NUM> may be utilized to select and individually dispense one or more beverages. The beverages may be dispensed as beverage components in a continuous pour operation whereby one or more selected beverage components continue to be dispensed while a pour input is actuated by a user or in a batch pour operation where a predetermined volume of one or more selected beverage components are dispensed (e.g., one ounce at a time). UI <NUM> may be addressed via a number of methods to select and dispense beverages. For example, a user may interact with UI <NUM> via touch input to navigate one or more menus from which to select and dispense a beverage. As another example, a user may type in a code using an onscreen or physical keyboard (not shown) on dispensing device <NUM> to navigate one or more menus from which to select and dispense a beverage.

UI <NUM>, which may include a touch screen and a touch screen controller, may be configured to receive various commands from a user (i.e., consumer input) in the form of touch input, generate a graphics output and/or execute one or more operations with dispensing device <NUM> (e.g., via HMI module <NUM> and/or CDM <NUM>), in response to receiving the aforementioned commands. A touch screen driver in HMI module <NUM> may be configured to receive the consumer or customer inputs and generate events (e.g., touch screen events) that may then be communicated through a controller to an operating system of HMI module <NUM>.

Dispensing device <NUM> may be in communication with one or more external device (e.g., mobile computing device <NUM>). In some embodiments, the communication between dispensing device <NUM> and the external device may be accomplished utilizing any number of communication techniques including, but not limited to, near-field wireless technology such as BLUETOOTH, Wi-Fi and other wireless or wireline communication standards or technologies, via a communication interface.

<FIG> shows a mobile computing environment <NUM> that mobile computing device <NUM> may operate within. For example, mobile computing environment <NUM> may comprise, but is not limited to, a smartphone, a tablet personal computer, or a laptop computer. Mobile computing environment <NUM> may comprise a handheld computer having both input elements and output elements. Input elements may include touch screen display <NUM> that may allow the user to enter information into mobile computing environment <NUM>, a microphone <NUM>, and a camera <NUM>. Mobile computing environment <NUM> may incorporate additional input elements such as a physical keypad (not shown). A soft keypad (not shown) may also be generated on touch screen display <NUM>.

Touch screen display <NUM> on mobile computing device <NUM> may also comprise an output element that can display a graphical user interface (GUI). Other output elements include a speaker <NUM>. Additionally, mobile computing environment <NUM> may incorporate a vibration module (not shown), which may cause mobile computing environment <NUM> to vibrate to notify the user of an event. Mobile computing environment <NUM> may incorporate a headphone jack (not shown) for providing output signals.

Mobile computing environment <NUM> may comprise a number of other components. The components may include a processor <NUM>, a memory <NUM>, radio functions <NUM>, an accelerometer <NUM>, and a GPS receiver <NUM>. Memory <NUM> may be utilized for storing an operating system <NUM> and may include a data storage <NUM>. Memory <NUM> may also include a number of applications <NUM> including, but not limited to, a mobile phone application, a data processing application, a calculator, games, an Internet browser, navigation a camera/video application and other applications such as application <NUM> that may be utilized for facilitating an individualized interaction with dispensing device <NUM> as discussed above. Radio functions <NUM> may support short range wireless communications via NFC, BLUETOOTH wireless technology, BLUETOOH LOW ENERGY (BLE) wireless technology, Wi-Fi, or other wireless technologies. Radio functions <NUM> may also be utilized to connect to the Internet (or other types of networks) as well as to remote computing systems.

<FIG> shows electronic device <NUM> that may provide an operating environment for dispensing device <NUM> or server <NUM> for example. Electronic device <NUM> may comprise a computing device that may include at least one processing unit <NUM> and a system memory <NUM>. Depending on the configuration and type of computing device, system memory <NUM> may comprise, but is not limited to, volatile (e.g., random access memory (RAM)), non-volatile (e.g., read-only memory (ROM)), flash memory, or any combination. System memory <NUM> may include an operating system <NUM> and other applications <NUM>. Operating system <NUM> may be suitable for controlling electronic device <NUM>'s operation.

Electronic device <NUM> may have additional features or functionality. For example, electronic device <NUM> may also include additional data storage devices (not shown) that may be removable and/or non-removable such as, for example, magnetic disks, optical disks, solid state storage devices (SSD), flash memory or tape. Electronic device <NUM> may also have input device(s) <NUM> such as a keyboard, a mouse, a pen, a sound input device (e.g., a microphone), a touch input device, etc. Output device(s) <NUM> such as a display, speakers, a printer, etc. may also be included. The aforementioned devices are examples and others may be used. Communication connection(s) <NUM> may also be included and utilized to connect to the Internet (or other types of networks) as well as to remote computing systems.

Embodiments, for example, may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process.

Computer readable media may include computer storage media. Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information (such as computer readable instructions, data structures, program modules, or other data) in hardware. System memory <NUM> (as well as memory <NUM>) may be an example of computer storage media (e.g., memory storage). Computer storage media may include, but is not limited to, RAM, ROM, electrically erasable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store information.

Computer readable media may also include communication media. Modulated data signal may describe a signal that may have one or more characteristics set or changed in such a manner as to encode information in the signal. Communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media.

A beverage may include, but is not limited to, pulp and pulp-free citrus and non-citrus fruit juices, fruit drink, vegetable juice, vegetable drink, milk, soy milk, protein drink, soy-enhanced drink, tea, water, isotonic drink, vitamin-enhanced water, soft drink, flavored water, energy drink, coffee, smoothies, yogurt drinks, hot chocolate and combinations thereof. The beverage may also be carbonated or non-carbonated. The beverage may comprise beverage components (e.g., beverage bases, colorants, flavorants, and additives).

A beverage base may comprise parts of the beverage or the beverage itself prior to additional colorants, additional flavorants, and/or additional additives. Beverage bases may include, but are not limited to syrups, concentrates, and the like that may be mixed with a diluent such as still or carbonated water or other diluent to form a beverage. The beverage bases may have reconstitution ratios of about <NUM>:<NUM> to about <NUM>:<NUM> or higher. Beverage bases may comprise a mixture of beverage base components.

A beverage base component may be included in beverage bases. The beverage base component may comprise parts of beverages that may be considered food items by themselves. The beverage base components may be micro-ingredients such as an acid portion of a beverage base, an acid-degradable and/or non-acid portion of a beverage base, natural and artificial flavors, flavor additives, natural and artificial colors, nutritive or non-nutritive natural or artificial sweeteners, additives for controlling tartness (e.g., citric acid or potassium citrate), functional additives such as vitamins, minerals, or herbal extracts, nutraceuticals, or medicaments. The micro-ingredients may have reconstitution ratios from about <NUM>: <NUM>, <NUM>: <NUM>, <NUM>: <NUM>, or higher with many having reconstitution ratios of <NUM>:<NUM> to <NUM>:<NUM>. The viscosities of the micro-ingredients may range from about <NUM> to about <NUM> centipoise.

Thus, for the purposes of requesting, selecting, or dispensing a beverage base, a beverage base formed from separately stored beverage base components may be equivalent to a separately stored beverage base. For the purposes of requesting, selecting or dispensing a beverage, a beverage formed from separately stored beverage components may be equivalent to a separately stored beverage.

Separately stored may comprise that the components may be kept separate until combined. For instance, the components may be separately stored individually in a container or package or instead may be all stored in one container or package wherein each component is individually packaged (e.g., plastic bags) so that they do not blend while in the container or package. The container or package, itself, may be individual, adjacent to, or attached to another container or package. A blended beverage may include final products wherein two or more beverages have been blended or mixed or otherwise combined to form a final product.

The product ingredients may include beverage bases or beverage base components (e.g., concentrated syrups) as well as flavors (i.e., flavoring agents, flavor concentrates, or flavor syrups), which may be separately stored or otherwise contained in individual removable containers. Each of the beverage bases or beverage base components and each of the flavors may be separately stored or otherwise contained in individual removable containers, cartridges, packages or the like that may generally be referred to simply as a package or ingredients package.

Claim 1:
A method comprising:
transmitting, by a dispensing device, a wireless signal from the dispensing device in close proximity to the dispensing device, the wireless signal including a device identification of the dispensing device;
receiving, at the dispensing device, an event notification, the event notification associated with a mobile device that received the wireless signal in close proximity to the dispensing device;
displaying, in response to the event notification, a customized user interface, the customized user interface based on preference data or profile data included in the event notification, the preference data or profile data associated with a user of the mobile device;
directly connecting, by the dispensing device, via a first wireless connection with the mobile device, the first wireless connection configured to exchange data between the dispensing device and the mobile device;
wherein the dispensing device comprises a first access point for establishing the first wireless connection; and
sending, by the dispensing device, second connection data to the mobile device, the second connection data comprising credentials for establishing a second wireless connection with a second access point, wherein the second access point is external to the dispensing device, wherein the credentials comprise a service set identifier of the second access point and a password for the second access point, and wherein the second wireless connection has a greater bandwidth than the first wireless connection.