Remote beverage selection using a beverage dispenser

Abstract

The beverage order execution system enables beverage execution from a mobile device without requiring a custom software application on the mobile device, instead controlling beverage dispenser operation using a web connection. The mobile device incorporates web browser software, the web browser software configured to initiate a communication session with at least one server. Data entry options are displayed in an interactive GUI for a first computer for communicating beverage selection commands to beverage dispensing software via the at least one server during each instance of beverage execution. The at least one server incorporates a WebSocket application program interface (API) stored on the at least one server and configured to connect a communication link between the beverage dispenser and the web browser software on the first computer.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 032,610, entitled "Remote Beverage Selection with a Beverage Dispenser," filed May 30, 2020, and U.S. Patent Application No. 17 / 007,608, entitled "Remote Beverage Selection with a Beverage Dispenser," filed August 31, 2020, the entire contents of which are incorporated by reference. [Background technology]

[0002] background Conventional post-mix beverage dispensing systems typically mix a stream of water or other type of diluent with a stream of syrup, concentrates, sweeteners, flavorings, other types of flavorings, and / or other ingredients by directing a stream of syrup down the center of a nozzle with a stream of water flowing around the outside. The stream of syrup is directed downward with the stream of water so that the streams of syrup and water mix as they fall into the consumer's cup. Overall, there is a desire for beverage dispensing systems to provide as many different types and flavors of beverages as possible in as small a footprint as possible. Recent improvements in beverage dispensing technology have focused on the use of minor ingredients. Minor ingredients may be used to separate conventional beverage bases into beverage components at very high dilution or reconstitution ratios.

[0003] The technology is enabled by cartridges containing highly concentrated trace ingredients. The trace ingredients are mixed with sweeteners and still or soda water using precise metering and dosing technology and dispensed through a nozzle that promotes air mixing to prevent leftovers. The technology includes user input for the user to select the desired beverage, customize the beverage as needed, and dispense the beverage with the dispenser. These beverages are produced from precise recipes that ensure a good tasting beverage despite the customization.

[0004] A post-mixed beverage dispensing system using micro-ingredients greatly increases the number of beverage options available at a given dispenser. For example, personalized interaction with the beverage dispenser may be provided as described in U.S. Patent Application Publication No. 2015 / 0082243, filed Sep. 15, 2014, entitled "Product Categorization User Interface for a Dispensing Device," the entire contents of which are incorporated herein by reference.

[0005] Queuing problems may occur because many users may establish a line or queue of users waiting their turn (i.e., a queue) to interact with the beverage dispenser, making it difficult to determine which consumer is handling the beverage dispenser at a given time and wants to establish an interaction with the beverage dispenser. The queuing problem is particularly pronounced when the handshaking between the dispenser and the consumer mobile computing device is performed via wireless communication technology, whose range may include multiple consumer mobile computing devices. The presence of multiple beverage dispensers within wireless communication distance may further exacerbate the queuing problem.

[0006] Previous solutions to the queuing problem have focused on deterministic methods of ascertaining which consumer is handling a particular beverage dispenser at a given time. For example, as described in U.S. Patent Application Publication No. 2015 / 0039776, filed Feb. 5, 2015, entitled "Facilitating Individualized User Interaction with an Electronic Device," the entire contents of which are incorporated herein by reference, a consumer may use the consumer's mobile computing device to scan an identifier on the beverage dispenser when handling the beverage dispenser. Similarly, in the case of a wireless handshake between a beverage dispenser and a consumer's mobile computing device, as described in U.S. Patent Application Publication No. 2018 / 0288594, filed Sep. 27, 2016, entitled "Dispenser Connectivity," the entire contents of which are incorporated herein by reference, the range of a wireless beacon transmitting an identifier to the beverage dispenser is limited (e.g., within 1-12 inches of the beverage dispenser), limiting the possibility of multiple mobile computing devices in the queue or adjacent queues from receiving the signal.

[0007] Another development in beverage execution is allowing consumers to interact with beverage dispensers using personal computing device applications (i.e., "mobile applications"). One example of an implementation of a beverage dispenser controlled by a mobile application is detailed in commonly owned International Patent Application PCT / US2019 / 067875, filed December 20, 2019, the contents of which are incorporated herein by reference. As described herein, upon a mobile application installed on a consumer mobile device reporting to a server that a first dispenser identifier (e.g., a scanned QR code) has been received from a region, the server may provide data regarding available beverages. For example, the server may provide a consumer profile for all beverage dispensers in a particular outlet, or all beverage dispensers within a predefined distance of the consumer mobile device. In this non-limiting optional embodiment, each beverage dispenser maintains an area profile, a database of profiles of consumers within a given area (e.g., an outlet or a predefined distance). Similarly, on a mobile application that no longer receives the first dispenser identifier within a threshold time or otherwise exits the region, the consumer profile is removed from the database of region profiles.

[0008] Even with so much development in beverage execution using mobile devices, consumers remain hindered by technical obstacles that require modification of current beverage systems. The current customer base for beverages frequently utilizes self-service beverage dispensers "on the fly" in multiple establishments, at various locations, and with impulse buying decisions occurring in real time. Thus, some customers may not be inclined to download the necessary software and mobile applications, especially if each point of sale requires specific software. Thus, there remains a need in the field of beverage execution for an easier system to use self-service beverage dispensers with maximum flexibility for consumers. Summary of the Invention [Means for solving the problem]

[0009] overview In one embodiment, a computerized system for beverage order fulfillment may be described as a system in which a first computer is connected in bidirectional electronic communication with at least one web server over a network. A beverage dispenser having a processor and a computerized memory storing beverage dispensing software on the beverage dispenser is in electronic communication with the at least one server over the network. The first computer incorporates web browser software stored on the first computer, the web browser software configured to initiate a communication session with the at least one server. An interactive graphical user interface (GUI) may be displayed on the first computer via the web browser, the interactive GUI being configured and updated by communication from the at least one server. Data entry options are displayed on the interactive GUI for the first computer for communicating beverage selection commands to the beverage dispensing software via the at least one server at each instance of beverage execution. The at least one server incorporates a web socket application program interface (API) stored on the at least one server and configured to connect a communication link to the beverage dispenser and the web browser software on the first computer. These and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.

[0010] In another embodiment, a computer-implemented method of beverage execution includes establishing an instance of beverage execution in electronic communication between a mobile device and a beverage dispenser via a web server by using each computer. The first computer may be a mobile device that scans a QR code displayed on the beverage dispenser and initiates electronic communication between the mobile device, the web server, and the beverage dispenser. The first computer or mobile device connects to a web address at the web server and embeds the web address within the QR code. The method continues by receiving an interactive graphical user interface (GUI) at the mobile device from the web server corresponding to beverage options available at the beverage dispenser and sending beverage commands to the web address using the interactive graphical user interface. The web server that implements the beverage commands in beverage dispensing software stored in the beverage dispenser.

[0011] In another embodiment, a beverage dispenser may include a beverage dispenser display coupled to a computer processor and a computerized memory storing beverage dispensing software. The beverage dispenser includes a nozzle configured to dispense a selected beverage, and a plurality of pumps and / or metering devices each configured to deliver beverage ingredients for the selected beverage from an ingredient source to the nozzle according to commands executed in the beverage dispensing software. A communications device configured to connect the beverage dispenser to a web server on a network and to receive beverage selection commands from the web server.

[0012] For a more complete understanding of the present disclosure, reference is now made to the following brief description taken in conjunction with the accompanying drawings and detailed description, in which like reference numerals indicate like parts. [Brief description of the drawings]

[0013] BRIEF DESCRIPTION OF THE DRAWINGS [Figure 1]FIG. 1 illustrates an exemplary system block diagram for preloading beverage selections into a beverage dispenser according to various embodiments of the present disclosure. [Figure 2A] 1 illustrates a schematic diagram of a communication system in which a mobile device can control a beverage dispenser according to the present disclosure. [Figure 2B] 1 illustrates a schematic diagram of a communication system in which a mobile device can control a beverage dispenser according to the present disclosure. [Figure 2C] 1 illustrates a schematic diagram of a communication system in which a mobile device can control a beverage dispenser according to the present disclosure. [Diagram 3] 1 illustrates a data sequence for a mobile device to control a beverage dispenser via a web server according to an embodiment of the present disclosure. [Figure 4] 1 illustrates an exemplary outlet having multiple beverage dispensers installed therein in accordance with various embodiments of the present disclosure. [Diagram 5] 1 illustrates a number of consumers at different distances from a group of beverage dispensers according to various embodiments of the present disclosure. [Figure 6] 14 illustrates example graphical user interface screens on a mobile device for controlling a corresponding beverage dispenser and navigating options on the beverage dispenser, according to various embodiments of the present disclosure. [Figure 7] 14 illustrates an example graphical user interface screen on a beverage dispenser for navigating to a selected beverage associated with the beverage dispenser according to various embodiments of the present disclosure. [Figure 8] 1 illustrates an exemplary graphical user interface screen on a mobile device according to various embodiments of the present disclosure. [Figure 9] 1 illustrates an exemplary beverage dispenser system suitable for implementing some embodiments of the present disclosure. [Figure 10] 1 illustrates an exemplary fluid circuit having a positive displacement pump suitable for implementing some embodiments of the present disclosure. [Figure 11]1 illustrates an exemplary fluid circuit having a static mechanical flow controller suitable for implementing some embodiments of the present disclosure. [Figure 12] 1 illustrates an exemplary fluid circuit having a dynamic mechanical flow controller and a flow meter suitable for implementing some embodiments of the present disclosure. [Figure 13] 1 illustrates an exemplary fluid circuit having multiple independently controlled paths from a single component source suitable for implementing some embodiments of the present disclosure. [Figure 14] FIG. 1 illustrates an example block diagram of a control architecture for a beverage dispenser suitable for implementing some embodiments of the present disclosure. [Figure 15] 1 illustrates an exemplary computer system suitable for implementing some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Detailed Description Although exemplary implementations of one or more embodiments are described below, it should be understood at the outset that the system and method of the present disclosure can be implemented using any number of techniques, whether currently known or existing. The present disclosure should in no way be limited to the exemplary implementations, figures, and techniques described below, but can be modified within the scope of the appended claims, together with the full scope of equivalents. The use of the term "and / or" means that any one or any combination of the list of options can be used. For example, "A", "B", and / or "C" means "A", or "B", or "C", or "A and B", or "A and C", "B and C", or "A and B and C".

[0015] The beverage dispenser 102 may have one or more wireless communication devices associated with it that provide the beverage dispenser with additional functionality for embodiments of the present disclosure. For example, each wireless communication device may be configured to broadcast one or more dispenser identifiers of the beverage dispenser to remote devices, where such technology is useful for verifying secure communications with customer devices, servers, or other computers at a retail store. For example, the dispenser identifier may be an identifier common to multiple beverage dispensers or to all compatible beverage dispensers. Another dispenser identifier may uniquely identify a particular beverage dispenser.

[0016] In some implementations, specialized configurations are possible when the beverage dispenser is a "smart dispenser" with multiple communication capabilities. For example, the beverage dispenser 102 may include multiple wireless communication devices, each of which broadcasts a dispenser identifier and connects to various remote computers at different communication ranges. For example, a first wireless communication device may be a WiFi modem 112 having a communication range of approximately 100-300 feet. A second wireless communication device may broadcast a second dispenser identifier at a second distance from the beverage dispenser. For example, the second wireless communication device may be a Bluetooth beacon having a communication range of approximately 10-20 feet.

[0017] 1 illustrates an exemplary system 100 for preloading a beverage dispenser 102 with a beverage selection in accordance with various embodiments of the present disclosure. The beverage dispenser 102 includes a user interface 104 (e.g., a display 107) for selecting a desired beverage to be dispensed from a nozzle 106 on the beverage dispenser 102. In some implementations, the beverage dispenser 102 includes an ingredient compartment 108 that stores a number of beverage ingredients (e.g., beverage microingredients). One or more additional beverage ingredients (not shown) may be supplied to the beverage dispenser 102 from a remote location (e.g., a back compartment). The additional beverage ingredients may include sweeteners, flavored syrups, carbon dioxide, water, carbonated water, and / or other beverage ingredients. As described in more detail below, pumps and / or metering devices (e.g., positive displacement pumps, static mechanical flow control valves, dynamic mechanical flow control valves, shut-off valves, etc.) are connected between each beverage component and the nozzle 106 to control the amount, rate, or ratio of the beverage components dispensed to dispense a selected beverage.

[0018] The beverage dispenser 102 may include an architecture 110 having a modem 112 for communicating with external devices. Though shown as a single component, the modem 112 may be multiple modems for communicating with different communication standards. For example, the modem 112 may include an Ethernet card and / or a cellular modem for connecting to a wide area network (WAN) 114 (e.g., the Internet) (e.g., via a local gateway (not shown)). The modem 112 may further include a local wireless communication modem for facilitating communication over a local network 116 using one or more local wireless communication standards (e.g., WiFi, WiFi Direct, ZigBee, Z-Wave, Bluetooth, or Bluetooth Low Energy (BLE) communication). In addition to the modem 112, the beverage dispenser 102 may emit a beacon (not shown), for example, a BLE beacon, that broadcasts a unique identifier associated with the beverage dispenser 102. These modem capabilities enable multiple programming and update techniques with state-of-the-art telecommunications processing.

[0019] The beverage dispenser 102 may be configured to utilize a modem 112 to communicate 118 with a remote server 119 over a wide area network WAN 114. In some embodiments, the beverage dispenser 102 is further configured to receive one or more notifications from the server 118 regarding how to handle communications with a consumer mobile device 122 that is to use the beverage dispenser 102. The mobile device 122 may be a smartphone, smart watch, personal digital assistant, or any other mobile computing device carried by the consumer. The beverage dispenser 102 is further configured to utilize the modem 112 to communicate locally with the consumer mobile device 122 or a local point of sale (POS) device 124.

[0020] In some non-limiting embodiments, the POS device 124 may be located in the same outlet (e.g., restaurant, convenience store, etc.) as the beverage dispenser 102. For example, the POS device 124 may be a self-service order entry system that receives consumer orders at the outlet. The POS device 124 facilitates a consumer to select a desired food order on the POS device 124 when placing an order before utilizing the beverage dispenser 102. The POS device 124 may or may not be in communication with the beverage dispenser 102 via the local network 116 (e.g., wired or wireless communication).

[0021] In some implementations, an individual POS device 124 may be in communication with each beverage dispenser 102 at a given outlet to facilitate beverage fulfillment. In some implementations, a POS device 124 may be associated with more than one beverage dispenser 102.

[0022] In one embodiment of the present disclosure, the mobile device 122 avoids requiring the consumer to download a mobile application and still remains compatible with facilitating personalized interaction with the beverage dispenser 102. With an embodiment of the present disclosure, the mobile device 122 with a regular internet connection (instead of a dedicated mobile application) can be used to order a favorite beverage, browse options for mixed or blended beverages, and maintain access to updated or future beverage selections available on one of the beverage dispensers 102 described above.

[0023] Generally, the mobile device 122 and the beverage dispenser 102 are configured for two-way online communication via a web server, as described below. The communication link 118 is facilitated online via a web server 119 when the mobile device is placed in sufficient proximity to the beverage dispenser 102 to scan, photograph or process an image (e.g., QR code 155) shown on the beverage dispenser display 107. Of course, the present disclosure is broader still for use in other technologies related to beverage dispensers that are not the primary focus of this disclosure (e.g., the mobile device 122 and the beverage dispenser may connect via a web server when the mobile device 122 is within a first distance of the beverage dispenser 102 or within a store that houses the beverage dispenser 102, when scanning a QR code is not the most efficient means of connection).

[0024] 2-5 illustrate example line diagrams for a communication session 200 between a mobile device 122 and a beverage dispenser 102 according to various embodiments of the present disclosure. Without limiting the disclosure, in the illustrated implementation, the beverage dispenser 102 may include communication resources such as, but not limited to, an Internet network, other computers, and / or a first wireless communication device and a second wireless communication device configured to broadcast data for wireless communication with the mobile device 122.

[0025] Consider FIG. 2A. The diagram illustrates how a mobile device 122 can implement a communication link 118 to a beverage dispenser 102 via a web server 119 to complete an entire instance of a beverage execution operation. Without limiting this disclosure, an instance of a beverage execution can include all of the steps, communications, and beverage dispenser operations that a consumer selects and completes to receive a beverage in a cup ready for consumption. The steps of the diagram in FIG. 2A illustrate that, at step 201, the beverage dispenser 102 utilizes a communication device (e.g., modem 112) to connect to a network 113 that provides an Internet connection to the web server 119. In one embodiment, at step 202, a vendor of beverages dispensed via the beverage dispenser 102 may utilize a private network that provides dedicated, reliable connections through a known Internet service provider to connect thousands of beverage dispensers distributed throughout various geographic regions to the servers, computers, and peripherals described below. At step 203, after the communication data from the beverage dispenser connection leaves the private network 113 for communication with the consumer operated mobile device 122 over the public communication network, the beverage dispenser connection may connect to a load balancer 117 and gateway hardware 116 that manages secure communication between the mobile device 122 and the beverage dispenser network. As illustrated at step 204, the network traffic flows through the load balancer 117 to perform web communication and data processing operations (e.g., services provided at least in part by Amazon Web Servers (AWS), but not limited to these). In some embodiments, the traffic leaves AWS and enters a public Internet Service Provider network (e.g., step 205) for communication over a global communication network serving the mobile device operated by the beverage consumer. At the retail store, the consumer uses the mobile device 122 to select a beverage execution command that is transmitted across the aforementioned network to complete an instance of the beverage execution at the beverage dispenser 102.Step 206 illustrates an optional connection to cache transaction data at the network edge (eg, a connection provided by a cloud service provider).

[0026] 2B illustrates another version of completing an instance of beverage execution. First, the beverage dispenser 102 establishes a communication connection 251 with an application program interface ("API") through a gateway ("GW") that initiates an appropriate web socket protocol (e.g., AWS) and, in one embodiment, passes the dispenser 102's serial number to the web server. In step 252, upon connecting to the beverage dispenser 102, the API gateway server distributes a security token to the beverage dispenser 102 and sends another security token every 10 seconds. In step 253, the beverage dispenser 102 displays a barcode 155 containing an encrypted URL on the graphical user interface 104, and in the communication connection 251, the beverage dispenser 102 sends the barcode 155 to the API gateway server 123 along with the previously received security token, which is updated every 10 seconds. At step 254, the consumer scans the two-dimensional barcode (i.e., QR code 155) and authorizes the launch of a web browser on the mobile device 122 to open a mobile version of the website on the mobile device 122. The browser on the mobile device 122 connects to the API gateway web socket at 256 and receives a verification token in two-way communication between the mobile device 122 and the API gateway server 123 at step 258. Over this connection, beverage execution occurs. At step 255, the API gateway server 123 sends a notification to the beverage dispenser 102 that the mobile device 122 has connected. The dispenser updates the two-dimensional barcode to indicate that the consumer has connected. At step 256, in various embodiments, the consumer uses graphical user interface options displayed on the mobile device 122 received from the API gateway server 123 to select a beverage and press a pour icon, ice icon, or stop icon among other selections. In some embodiments, the selection may include mixing the beverage selection in a desired ratio into a single cup. In step 257, the API gateway relays the dispense event from the mobile device to the dispenser.At step 258, the consumer clicks Done on the mobile device user interface there is a timeout or another activity that requires the end of the beverage run.

[0027] FIG. 2C illustrates a schematic diagram of the operations described above. This diagram basically shows the processing in the application layer 215 accessed via the gateway server 123 that can initiate cloud-based operations 217 using electronics configured within the beverage dispenser 219. The API gateway server 123 may implement different application interfaces 215 depending on the type of user communicating with the web server 119 via the API gateway server 123. In this regard, the beverage dispenser 102 may be configured for secure communication via a customer user interface 225A and / or a non-customer user interface 225B, each having different web socket connections and authorizations. In this manner, the web server 119 can provide access to appropriate data and communication resources depending on whether the user is a member of the beverage manufacturer personnel (having dedicated access), a beverage dispenser technician (e.g., having maintenance access), or a user with contactless access for beverage purchases as described herein. Appropriate application services with different web socket connections are provided to each within the cloud operations 217 available in at least one embodiment.

[0028] 3 illustrates an example entity sequence diagram 300 for an indirect communication session between a mobile device 122, a web server 119, and a beverage dispenser 102 in accordance with various embodiments of the present disclosure. The sequence diagram 300 shows the server 119 acting as an intermediary to facilitate a communication link 118 between the mobile device 122 and the beverage dispenser 102. Steps in the sequence include, but are not limited to, the following:

[0029] At 325, the QR code 155 may be displayed on the graphical user interface 104 of the beverage dispenser 102 for reading by the mobile device 122 having a mobile phone enabled display for the contactless experience. Thus, as shown at 325, the consumer can scan the QR code 155 with the consumer's mobile camera and activate the experience via the web server 119 without having to install a mobile application. The mobile phone or mobile device 122 prompts the user to confirm that the user wants to start the contactless experience. In some embodiments, the mobile experience may be started in less than 3 seconds on an LTE smartphone with good signal reception. The QR code 155 has an embedded security token so that only the person in front of the beverage dispenser 102 can activate the experience. Once the consumer starts the mobile experience 147, it connects the consumer to the beverage dispenser 102 via a cloud based web socket 137. This has all of the qualities of a direct connection from the consumer's perspective with security controlled by the web server 119 therein.

[0030] As shown in Figure 3, the beverage dispenser 102 is continuously updating its connection with the cloud infrastructure and associated web socket 137. The cloud-based web server 119 receives the updated QR code and associated token via periodic secure updates between the web server 119 and the beverage dispenser 102. The updated QR code is shown on a display 107 associated with a graphical user interface 104 on the beverage dispenser. At steps 345, 355, the mobile device 102 receives updates to its mobile website connection with the web server 119 for proper display of beverage availability and other updates related to use of the beverage dispenser. These communications with the web server 119 are secured by a pre-received communication token as described in step 325 and described in more detail below.

[0031] In FIG. 3, once the consumer connects to the beverage dispenser 102 at 365, the QR code 155 shown on the beverage dispenser's customer user interface ("CUI") 225A changes to reflect the fact that a connection has been made. In one non-limiting embodiment, the QR code 155 may be shown with a mobile phone icon above the QR code 155 to signify that an in-use operation is in progress. This more effectively prevents another consumer from scanning the code. From the mobile device 122, the consumer should be able to select a beverage. This selection should also reflect sold out options since the beverage dispenser can send inventory data to the web server 119. The customer user interface 225A should reflect the selection being made by the consumer. This is a good feedback mechanism and furthermore, the consumer can use contact to resume the consumer's experience if they accidentally disconnect the consumer. With technician and personnel settings established through each non-customer user interface 225B, the consumer can complete a volumetric dispense based on prior input and settings from the non-customer user interface 225B or retail store personnel settings. The consumer should be able to cancel the pour. In some embodiments, the consumer can perform pour lock actions. These actions are summarized in FIG.

[0032] In a dispense contact embodiment, if the consumer loses connectivity with the beverage dispenser 102, the instance of beverage execution should cancel the dispense after a selected number of milliseconds. This time may be variable based on the test latency of the web connection between the mobile device, the web server, and the beverage dispenser.

[0033] Once the consumer has completed their pour, they should be able to perform a "fill up" from a screen selection on the consumer's mobile device.

[0034] Once the consumer is completely finished with their experience, they should be able to click "Done," which will return the dispenser and 2D barcode to their original state.

[0035] If the mobile experience is running and someone touches the dispenser CUI, the mobile experience will be terminated.

[0036] If the mobile phone loses connectivity for X seconds or if the user does not continue the experience for Y seconds, the CUI reverts to its original state.

[0037] In one embodiment, the computerized beverage order fulfillment system 200 may be described as a system in which a first computer 122 is connected in two-way electronic communication with at least one web server 119 over a network via a gateway server 123. A beverage dispenser 102 having a processor and a computerized memory storing beverage dispensing software on the beverage dispenser is in electronic communication with the at least one server over the network. The first computer incorporates web browser software stored on the first computer, the web browser software configured to initiate a communication session with the at least one server 119. An interactive graphical user interface (GUI) 600 may be displayed on the first computer 122 via the web browser, the interactive GUI 600 being configured and updated by communication from the at least one server 119. Data entry options are displayed in the interactive GUI for the first computer for communicating beverage selection commands to the beverage dispensing software via the at least one server at each instance of beverage execution. The at least one server incorporates a WebSocket application program interface (API) stored on the at least one server and configured to connect a communication link 113 to the beverage dispenser 102 and to web browser software on the first computer.

[0038] an encryption program stored in the computerized memory of the beverage dispenser, the encryption program configured to generate a verification token for each instance of a beverage execution 215-217, as shown in FIG. 2C, the verification token verifying authenticity of electronic communications between the first computer and the at least one server and the beverage dispenser; the encryption program further configured to incorporate the verification token into a QR code displayed on the beverage dispenser via the beverage dispenser display, the beverage dispenser communicating the token encoded by the QR code to the at least one server for each instance of a beverage execution; and displaying an in-use icon on the beverage dispenser display during each instance of a beverage execution if the instance of a beverage execution is active.

[0039] The beverage dispenser further includes a customer user interface and a non-customer user interface that connect the beverage dispenser display to the beverage dispenser's processor and computerized memory. The non-customer user interface may include a dedicated screen that allows an employee at the retail establishment to program features or feature limitations into the beverage dispenser. The first computer may be a mobile device that further includes a camera and is configured to launch web browser software and provide a beverage selection experience on the camera that processes a QR coded image displayed on the beverage dispenser. The image is a QR code that may incorporate a verification token and a web address that launches a website on the mobile device that corresponds to the beverage execution software on the beverage dispenser.

[0040] As mentioned above, FIG. 3 illustrates that an embodiment of the present disclosure may also be described as a computer-implemented method of beverage execution, the method including establishing an instance of beverage execution 300 in electronic communication between a mobile device 122 and a beverage dispenser 102 via a web server 119 by using each computer to execute optional steps 325-385 of the beverage execution. For example, at 325, using the mobile device 122, a consumer may initiate a beverage execution at the beverage dispenser by scanning a QR code 155 displayed on the beverage dispenser 102 and initiating electronic communication between the mobile device 122, the web server 119, and the beverage dispenser 102. An electronic communication network 113, 123 accessible by the mobile device may connect the mobile device to a web address at the web server 119, embedding the web address within the QR code. With the web server as an intermediary between the mobile device and the beverage dispenser, the mobile device may receive an interactive graphical user interface (GUI) 600 from the web server corresponding to beverage options available at the beverage dispenser. At 345-375, the method of this embodiment uses an interactive graphical user interface 600 to send beverage commands to a web address. Using the web server to implement an instance of a beverage execution, the beverage commands control equipment described below with beverage dispensing software stored in the beverage dispenser.

[0041] At the beverage dispenser, the method includes using beverage dispensing software to generate a QR code and a unique verification token that attests to the authenticity of information used during an instance of beverage execution. The beverage dispensing software at the beverage dispenser embeds the unique verification token and a website address into the QR code, and further transmits and stores the QR code with the unique verification token and website address embedded in the QR code at the web server. Concurrently, the beverage dispenser displays the QR code at the beverage dispenser with the unique verification token and website address embedded in the QR code.

[0042] From the consumer's perspective, using the camera on a mobile device, the consumer processes an image of the QR code displayed on the beverage dispenser and initiates an instance of beverage execution with the QR code by connecting the mobile device to a website address embedded within the QR code. Importantly, this connection does not require a mobile application on the mobile device, as the beverage execution of the present disclosure can be completed by a simple website connection on the internet.

[0043] The consumer uses a mobile device to extract the unique verification token embedded within the QR code and transmits the extracted verification token from the mobile device to a web server. The web server then compares the extracted verification token to the unique verification token and verifies the electronic communication between the mobile device and the beverage dispenser. The web server uses a shared secret to verify the authenticity of the token, for example, by digitally signing it via an HMAC hash-based message authentication code.

[0044] A graphical user interface on the mobile device transmits beverage commands which, in non-limiting embodiments, may include selecting a beverage available at the beverage dispenser, dispensing a beverage from the beverage dispenser, and stopping the dispensing of a beverage.

[0045] As used herein, by way of example only, a beverage dispenser used in an embodiment of the present disclosure includes a beverage dispenser display connected to a computer processor and a computerized memory storing beverage dispensing software, a nozzle configured to dispense a selected beverage, a plurality of pumps and / or metering devices each configured to deliver beverage ingredients for the selected beverage from an ingredient source to the nozzle according to commands executed in the beverage dispensing software, and a communication device configured to connect the beverage dispenser to a web server on a network and to receive beverage selection commands from the web server. The beverage dispenser as described above includes an encryption program stored in the computerized memory of the beverage dispenser. The encryption program is configured to generate a verification token for each instance of beverage execution, the verification token verifying authenticity of the electronic communication and beverage selection command from the web server. The encryption program is further configured to incorporate the verification token into a QR code displayed on the beverage dispenser via the beverage dispenser display, the beverage dispenser communicating the token and the QR code for each instance of beverage execution to at least one server.

[0046] As shown in Figures 2 and 3, a computerized system for beverage order fulfillment may include a first computer (such as, but not limited to, a mobile device 122) connected in bidirectional electronic communication with at least one web server 119 over a network 118. The beverage dispenser 102 is a smart device connected to the network and utilizes hardware (e.g., a processor and a computerized memory that stores beverage dispensing software in the computerized memory). Additionally, the beverage dispenser 102 is in electronic communication with the at least one server 119 over the network 118. The first computer, which is often a mobile device 122 or a smartphone, stores web browser software, and the web browser software on the mobile device 122 is configured to initiate a communication session with the at least one server 119. The first computer (e.g., the mobile device 122) includes an interactive graphical user interface (GUI) including a display on the first computer that interacts with the web browser. The interactive GUI is configured and updated by communication from at least one server, and data entry options are displayed on the interactive GUI for the first computer / mobile device 122 for communicating beverage selection commands to the beverage dispensing software on the beverage dispenser 102 via the at least one server 119 at each instance of beverage execution.

[0047] As shown in FIG. 3, the computerized system further includes a web socket application program interface (API) stored in the at least one server 119, accessible via the gateway server 123, and configured to connect to the beverage dispenser 102 and a web browser software on the first computer / mobile device 122. These communications are secured via an encryption program stored in the computerized memory of the beverage dispenser. The encryption program is configured to generate a verification token for each instance of beverage execution, the verification token verifying the authenticity of electronic communications between the first computer / mobile device 102 and the at least one server 119 and the beverage dispenser 102. The encryption program is further configured to embed the verification token in a QR code 155 displayed on the beverage dispenser 102 via the beverage dispenser display 104, 107, and the beverage dispenser communicates the token, encoded by the QR code 155, to the at least one server 119 for each instance of beverage execution. In one embodiment, the beverage dispenser 102 is equipped to display various images including beverage selections and QR codes. The QR code may include an encrypted verification token and a web address that launches a website on the mobile device that corresponds to the beverage execution software on the beverage dispenser 102. Thus, the first computer may be characterized as a mobile device that further includes a camera and is configured to launch web browser software and provide a beverage selection experience on the camera that processes the QR coded image displayed on the beverage dispenser. A graphical user interface on the mobile device may be configured to allow a user to send a beverage selection command over a network to the beverage dispenser 102 without touching the beverage dispenser 102. In some embodiments, the beverage execution may automatically place a cup under the nozzle with no touching or contact at all.The contactless beverage execution system allows the mobile device 102 to transmit beverage selection data including, but not limited to, selecting individual beverages from those available at the beverage dispenser, dispensing the beverage from the beverage dispenser, and stopping the dispensing of the beverage. In some embodiments, the graphical user interface may include commands to mix different beverages into a single cup during the same instance of beverage execution.

[0048] A web server, which complements the mobile device and beverage dispenser to complete an instance of a beverage execution, may include at least one processor connected to a computerized memory that stores web content and a web server application accessible over a network. In some non-limiting embodiments, the web server connects to components of the system with an application program interface (API) for a web socket communication connection with the web server by the beverage dispenser, and the web server application receives beverage data from the beverage dispenser for an instance of a beverage execution. The beverage data may include inventory data of beverages available at the dispenser, or other information useful to the consumer (e.g., consumer profiles for repeat customers). The beverage data includes a QR code generated by the beverage dispenser having beverage dispensing software stored in the beverage dispenser. The QR code includes a unique validation token to be stored in the web server for each instance of a beverage execution. At least one of the web server applications uses the beverage data from the beverage dispenser to update a graphical user interface that is distributed to the remote mobile device. In other embodiments, at least one of the web server applications receives beverage commands from the remote mobile device and transmits the beverage commands to the beverage dispenser. Beverage commands may include, but are not limited to, selecting a beverage available at the beverage dispenser, dispensing a beverage from the beverage dispenser, stopping the dispensing of a beverage, and filling a container with a beverage.

[0049] An embodiment of the present disclosure further includes a web server 119 that completes an instance of a beverage execution. The web server incorporates at least one web server processor connected to a web-based computerized memory that stores web content and web server applications accessible over a network, such as, but not limited to, a cloud-based network. An application program interface (API) for web socket communication connects the web server to the beverage dispensers, and the web server application receives beverage data from the beverage dispensers for an instance of a beverage execution.

[0050] 4 illustrates an example outlet 400 having multiple beverage dispensers installed therein in accordance with various embodiments of the present disclosure. As shown, the outlet 400 includes a first group 402 of beverage dispensers, a second group 404 of beverage dispensers, and a third group 406 of beverage dispensers. Each group 402, 404, 406 of beverage dispensers includes one or more beverage dispensers. For example, the group 402 includes beverage dispenser 402a and beverage dispenser 402b. Similarly, the second group 404 includes beverage dispenser 404a, beverage dispenser 404b, beverage dispenser 404c, and beverage dispenser 404d. Additionally, the third group 406 includes beverage dispenser 406a and beverage dispenser 406b.

[0051] The consumer 408 may be one of many customers entering the outlet 400 through the entrance 412. As described above in other commonly owned patent applications, the beverage dispenser may pre-arrange secure communications with the customer's mobile device when the mobile device enters the outlet 400 or within a predetermined distance of the outlet 400, and may determine that the mobile device 122 carried by the consumer 408 is within a first distance of one or more beverage dispensers in the outlet 400. As a further example, the mobile device 122 may be determined to be within a first distance of one or more beverage dispensers in the outlet 400 upon entering a geographic fence location around the perimeter or within a predetermined distance of the outlet 400.

[0052] FIG. 5 illustrates that the technology surrounding the communication between the beverage dispenser and the mobile device can incorporate all of the protections of a "smart system" for verification communication. In the example of FIG. 5, multiple consumers at different locations are around the beverage dispensers 404a-404d of the second group 404 according to various embodiments of the present disclosure. As shown, the consumers may be located at different distances from the beverage dispensers of the second group 404, including a first distance 502, a second distance 504, a third distance 506, and a fourth distance 508. The first distance 502 may be located farthest from the second group 404, and the fourth distance 508 may be located closest to the second group 404. A first consumer 510 (consumer A) and a second consumer 512 (consumer B) may be located between the third distance 506 and the fourth distance 508. A fourth consumer 516 (consumer D) may be located between the second distance 504 and the third distance 506. A third consumer 514 (consumer C) and a fifth consumer 518 (consumer E) may be located between the first distance 502 and the second distance 504.

[0053] Although shown as different distances from the second group 404 for simplicity, each dispenser in the second group 404 may have one or more wireless communication devices that establish different communication ranges with each dispenser. For example, beverage dispenser 404a may have a wireless communication device with a corresponding range within a fourth distance 508 that includes adjacent beverage dispenser 404b but does not include the remaining beverage dispensers 404c, 404d in the second group 404. Similarly, beverage dispenser 404b may have a wireless communication device with a corresponding range within a fourth distance 508 that includes adjacent beverage dispensers 404a and 404c but does not include the remaining beverage dispensers 404d, etc.

[0054] As consumers move through the store, they may travel one or more of distances 502-508. For example, a first consumer 510 may move to service beverage dispenser 404a, and a second consumer 512 may move to service beverage dispenser 404c. At the same time, a third, fourth, and fifth consumers 514, 516, 518 may move to other portions of the store 400 and not service any of the beverage dispensers in the second group 404.

[0055] 6 illustrates an example graphical user interface 605 and associated screens that may be implemented on a mobile device 122 to communicate beverage execution commands to and navigate beverage dispenser operations 102, according to various embodiments of the present disclosure. Following the example in FIG. 5 above, the graphical user interface screens shown in FIG. 6 may correspond to the user interface 104 of the beverage dispenser 102.

[0056] As shown, the main screen 602 may present a graphical user interface 605 having a number of buttons 603 for making beverage selections. For example, one or more of the buttons 603 on the main screen 602 may be for navigating to sub-screens having different categories of beverages. These buttons may correspond to buttons found on the beverage dispenser 102, for example, as described in commonly owned U.S. patent application Ser. No. 14 / 485,826, entitled "Product Categorization User Interface for a Dispensing Device," the entire contents of which are incorporated herein by reference. The main screen 602 further includes a pour button 620 that controls the length of a pour action for a selected beverage on the beverage dispenser 102. A separate ice button 630 may be utilized to manually operate an ice dispenser function on the beverage dispenser 102.

[0057] 7 illustrates an exemplary graphical user interface screen on a beverage dispenser for navigating to pre-selected beverages associated with multiple pre-loaded consumer profiles according to various embodiments of the present disclosure. Following the example in FIG. 6 above, the graphical user interface screen shown in FIG. 7 may be displayed on the user interface 104 of the beverage dispenser 102 and on the graphical user interface 600 on the mobile device 122 that controls the beverage dispenser.

[0058] The details of the user interface 104 on the beverage dispenser 102 may be configured for operation on the dispenser and may be further configured to be replicated in the graphical user interface 600 on the mobile device 122. As shown on the beverage dispenser 102, a main screen 702 may present a graphical user interface having a number of buttons for making beverage selections. For example, one or more of the buttons 704 on the main screen 702 may be for navigating to sub-screens having different categories of beverages, as described, for example, in U.S. Patent Application No. 14 / 485,826, entitled "Product Categorization User Interface for a Dispensing Device," mentioned above. The main screen 702 may further include one or more buttons for categories of pre-selected beverages held in the user profile. For example, the main screen 702 may include a selectable favorite beverage icon 706, a selectable mix icon 708, and a selectable order icon 710.

[0059] Upon selection of the blend icon 708, a blend screen 718 may be displayed in the user interface 104. The blend screen 718 lists the top three blends from each of a plurality of profiles (e.g., each of the profiles in a profile queue, or a predetermined number of profiles from an array of profiles in a database of area profiles). Other numbers of blends from each profile are shown in various implementations.

[0060] FIG. 8 illustrates an exemplary graphical user interface 600 and associated screens on a mobile device 122 for selecting and associating a beverage order with a beverage dispenser 102. Each of the graphical user interface screens shown in FIG. 8 may be displayed via a user interface on the mobile device 122 (e.g., a touch screen display). A profile mobile application on the mobile device 122 facilitates customization of a consumer profile that may be saved to a network server or the beverage dispenser's hard drive. From the order screen 910, multiple beverage options may be presented. For example, one or more of the buttons 916 on the order screen 910 can be for navigating to corresponding buttons on the associated beverage dispenser 102.

[0061] In response to the selection of the beverage icon, an order confirmation screen 926 may be displayed on the user interface of the mobile device 122. For example, the order confirmation screen 926 may display the selected beverage icon 924 and may include a selectable confirmation icon 928 ("I choose you") to confirm the selection of the selected beverage icon 924 for the next order. Other variations and modifications of the order selection screen shown in FIG. 8 are contemplated by this disclosure. For example, one or more of the screens or icons may be omitted or other options (not shown) may be included.

[0062] 9 illustrates an exemplary beverage dispenser system 1000 suitable for implementing some embodiments of the present disclosure. As shown, the beverage dispenser system 1000 is configured as an ice-cooled beverage dispenser. Other configurations of the beverage dispenser (e.g., a plug-in ice-cooled beverage dispenser, a countertop electric beverage dispenser, a remote recirculating beverage dispenser, or any other beverage dispenser configuration) are contemplated by the present disclosure.

[0063] The beverage dispenser system 1000 includes a front chamber system 1002 having a beverage dispenser 1004, and a back chamber system 1006. The beverage dispenser 1004 includes a user interface 1008 (e.g., a touch screen display) that facilitates selection of a beverage to be dispensed. The user interface 1008 may use various screens to facilitate user interaction with the beverage dispenser 1004 and / or receive a user profile through interaction with the user's mobile device 1052, for example, as described in commonly owned U.S. patent application Ser. No. 14 / 485,826, entitled "Product Categorization User Interface for a Dispensing Device," the entire contents of which are incorporated herein by reference.

[0064] Upon receiving a beverage selection via the user interface 1008, the dispense button 1010 may be actuated to dispense the selected beverage from the beverage dispenser 1004 via the nozzle 1014. For example, the dispense button 1010 may be an electromechanical button, a capacitive touch button, or other button selectable by a user to actuate the beverage dispenser 1004 to dispense a beverage. Although shown as a button, the dispense button 1010 may instead be implemented as a lever or other mechanism that actuates the beverage dispenser 1004 to dispense a beverage. As shown in FIG. 10, the dispense button 1010 is separate from the user interface 1008. In some implementations, the dispense button 1010 may be implemented as a selectable icon in the user interface 1008.

[0065] In some implementations, the beverage dispenser may further include an ice lever 1014. When activated, the ice lever 1014 may cause the beverage dispenser 1004 to dispense ice via an ice chute (not shown). For beverage dispensers that do not have an ice bin (e.g., countertop electric or remote recirculating beverage dispensers), the ice lever 1014 may be omitted.

[0066] The beverage dispenser 1004 may be secured via a main door 1016 and an ingredient door 1018. The main door 1016 and the ingredient door 1018 may be secured via one or more locks. In some implementations, the lock is a lock and key. In some implementations, the lock on the ingredient door 1018 may be opened via an RFID reader (not shown) that reads an approved ingredient package 1028. The main door 1016 may protect the electronic components of the beverage dispenser 1004, including one or more controllers 1020. The ingredient door 1018 may protect an ingredient compartment that houses an ingredient array 1024.

[0067] The ingredient array 1024 includes a number of slots 1026 that receive ingredient packages 1028. In various implementations, the ingredient packages 1028 may be microingredient cartridges. The microingredient cartridges may be single or dual cartridges, for example, as described in commonly owned U.S. patent application Ser. No. 14 / 209,684 entitled "Beverage Dispenser Container and Carton" and U.S. patent application Ser. No. 12 / 494,427 entitled "Container Filling Systems and Methods," both of which are incorporated herein by reference in their entirety. As shown in FIG. 9, there are three drawers of ingredients in the ingredient array 1024. One or more of the drawers may slide back and forth along rails to periodically agitate the ingredients contained therein. Other configurations of the ingredient array 1024 are possible, for example, via one or more stationary and / or agitated ingredient towers.

[0068] Each ingredient package 1028 may include an RFID tag, a fixture 1030, and a fixture seal 1032. The fixture seal 1032 may be removed prior to installation in the beverage dispenser 1004. Upon installation, the fixture 1030 may engage and provide fluid communication between a probe (not shown) in the slot 1026 and the ingredients contained in the ingredient package 1028. The ingredient array 1024 may further include one or more bulk microingredient packages 1034, for example, one or more microingredient sweetener sources.

[0069] The beverage dispenser 1004 may further include a carbonator (not shown) that contains water and carbon dioxide to produce carbonated water. The beverage dispenser 1004 may further include one or more heat exchangers (not shown), e.g., cold plates, that cool one or more of the beverage components contained in or by the beverage dispenser 1004. In some implementations, one or more of the minor ingredients dispensed through the nozzle 1012 are not cooled via a heat exchanger or are otherwise held at ambient temperature. Macro-ingredients dispensed through the nozzle 1012 are typically cooled via a heat exchanger before being dispensed.

[0070] The back room system 1006 is typically installed in a back room (e.g., a storage area at a commercial location) separate from the front room system 1002. The back room system 1006 includes a water source 1036 (e.g., a municipal water supply providing a pressurized source of fresh water). Water received via the water source 1036 may be filtered or otherwise treated by a water treatment system 1038. Optionally, the treated water may be pressurized to a desired pressure in a water booster 1040 and provided to the beverage dispenser. A carbon dioxide source 1042 may provide carbon dioxide to the beverage dispenser 1004.

[0071] One or more macro-ingredient sources 1044 may be located in the back chamber. A macro-ingredient from each macro-ingredient source 1044 may be supplied to the beverage dispenser 1004 via a pump 1046. The pump 1046 may be a controlled gear pump, a diaphragm pump, a BIB pump, or any other suitable pump that supplies macro-ingredients to the beverage dispenser 1004. The back chamber system 1006 may further include a rack having one or more storage locations 1048 for reserve micro-ingredients and one or more storage locations 1050 for reserve macro-ingredients.

[0072] The beverage dispenser 1004 may include one or more network interfaces to communicate directly with devices in the front or back room, over a local area network (LAN) with devices in the front or back room, or over a wide area network (WAN) connection with devices remote from the location having the beverage dispenser system 1000. For example, the beverage dispenser 1004 may include a network device (e.g., a near field communication (NFC) module, a Bluetooth module, a WiFi module, a cellular modem, an Ethernet module, etc.). The beverage dispenser 1004 may communicate directly or over a local area network (LAN) with a user's mobile device 1052 or a point of sale (POS) device 1054 to receive the user's beverage selection or user profile that configures the beverage dispenser 1004, and dispense one or more beverages based on the beverage selection or user profile. The user profile may include stored favorite beverages for the user, mixed or blended beverages created or stored by the user in the user's profile, and / or one or more beverage preferences (e.g., preferred nutritional levels). Additionally, the beverage dispenser 1004 may communicate over a wide area network (WAN) 1056, which communicates with one or more remote servers 1058, to receive software updates, content updates, user profiles, or beverage selections made via the remote servers 1058.

[0073] Figures 10-12 illustrate exemplary fluid circuits 1100-1300 having pumps or metering devices from ingredient sources 1102, 1202, 1302 to a nozzle 1012 of a beverage dispenser 1004. The beverage dispenser 1004 may include zero, one, or more of the fluid circuits shown in Figures 10-12. For each ingredient source, the beverage dispenser 1004 may include one of the fluid circuits shown in Figures 10-12.

[0074] 10 illustrates an exemplary fluid circuit 1100 having a positive displacement pump 1110 suitable for implementing some embodiments of the present disclosure. The fluid circuit 1100 provides a fluid path from an ingredient source 1102 to a nozzle 1012. The ingredient source 1102 may be a micro-ingredient source or a macro-ingredient source housed in the ingredient array 1024 of the beverage dispenser 1004, located remotely from the beverage dispenser 1004 in a front chamber (e.g., adjacent to the beverage dispenser 1004 or under a stand on which the beverage dispenser 1004 is placed) or in a rear chamber. The positive displacement pump 1110 may meter a predetermined volume or flow rate of an ingredient from the ingredient source 1102 to the nozzle 1012. The positive displacement pump 1110 may be a piston pump, a controlled gear pump, a peristaltic pump, a nutation pump, a diaphragm pump, or other such positive displacement pump that meters a fixed volume of fluid flow with each pump cycle.

[0075] Optionally, the fluid circuit 1100 may include a sold out sensor 1104 that detects when the ingredient source 1102 is empty. If the ingredient source 1102 is located remotely from the beverage dispenser 1004, the fluid circuit 1100 may further optionally include a backing pump 1106 that provides a pressurized supply of the beverage ingredient to the beverage dispenser 1004. Within or directly adjacent to the beverage dispenser 1004, the fluid circuit 1100 may include a pressure regulator 1108 such that an inlet of the positive displacement pump 1110 receives a lower or zero pressure supply of the beverage ingredient. Further optionally, the fluid circuit 1100 may include a shutoff valve 1112 configured to remain closed when the ingredient is not being dispensed to prevent the beverage ingredient from dripping out of the nozzle 1012.

[0076] 11 illustrates an exemplary fluid circuit 1200 having a static mechanical flow controller 1208 suitable for implementing some embodiments of the present disclosure. The static mechanical flow controller 1208 receives pressurized beverage ingredients from an ingredient source 1202 and provides a fixed flow rate of the beverage ingredient to the nozzle 1012. The static mechanical flow controller 1208 may be calibrated with a set screw that sets the flow rate of the static mechanical flow controller 1208. A shutoff valve 1210 downstream of the static mechanical flow controller 1208 may be actuated to open or close to dispense or prevent dispensing of the beverage ingredient from the nozzle 1012.

[0077] The ingredient source 1202 may be a micro-ingredient source or a macro-ingredient source housed in the ingredient array 1024 of the beverage dispenser 1004, located remotely from the beverage dispenser 1004 in a front room (e.g., adjacent to the beverage dispenser 1004 or under a stand on which the beverage dispenser 1004 is placed), or in a back room. The ingredient source 1202 may be a municipal water supply 1036 or other pressurized ingredient source. If the ingredient source 1202 is not pressurized, the fluid circuit 1200 may include a pump 1206 to pressurize the beverage ingredient from the ingredient source 1202. The pump 1206 may be any pump (e.g., a BIB pump, a carbon dioxide driven pump, a controlled gear pump, or a positive displacement pump) suitable for pressurizing the beverage ingredient from the ingredient source 1202. Further optionally, the fluid circuit 1200 may include a sold out sensor 1204 to detect when the ingredient source 1202 is empty.

[0078] 12 illustrates an exemplary fluid circuit 1300 having a dynamic mechanical flow controller 1308, a flow meter 1310, and a shutoff valve 1312 suitable for implementing some embodiments of the present disclosure. The dynamic mechanical flow controller 1308 receives pressurized beverage components from an ingredient source 1302 and provides an adjustable flow rate of the beverage components to the nozzle 1012. The dynamic mechanical flow controller 1308 may include a variable size orifice that adjusts to dynamically change the flow rate of the beverage components delivered to the nozzle 1012 based on control signals provided by one or more controllers 1020. A flow meter 1310 downstream of the dynamic mechanical flow controller 1308 measures the flow rate of the beverage components being delivered by the dynamic mechanical flow controller 1308 and provides a feedback loop to the dynamic mechanical flow controller 1308 that controls the variable size orifice. A shutoff valve 1312 downstream of the dynamic mechanical flow controller 1308 may be actuated to open or close to dispense or prevent dispensing of the beverage components from the nozzle 1012.

[0079] The ingredient source 1302 may be a micro-ingredient source or macro-ingredient source housed in the ingredient array 1024 of the beverage dispenser 1004, located remotely from the beverage dispenser 1004 in a front room (e.g., adjacent to the beverage dispenser 1004 or under a stand on which the beverage dispenser 1004 is placed), or in a back room. The ingredient source 1302 may be a municipal water supply 1036 or other pressurized ingredient source. If the ingredient source 1302 is not pressurized, the fluid circuit 1300 may include a pump 1306 to pressurize the beverage ingredient from the ingredient source 1302. The pump 1306 may be any pump (e.g., a BIB pump, a carbon dioxide driven pump, a controlled gear pump, or a positive displacement pump) suitable for pressurizing the beverage ingredient from the ingredient source 1302. Further optionally, the fluid circuit 1300 may include a sold out sensor 1304 to detect when the ingredient source 1302 is empty.

[0080] Although the components of the fluid circuits 1100-1300 are shown in a particular order in Figures 10-12, any order of the components described above may be used. For example, the shutoff valve 1312 may be upstream of the flow meter 1310. Other variations will be readily recognized by those of ordinary skill in the art. Additionally, one or more heat exchangers (not shown) may be used in any location in the fluid circuits of Figures 10-12. The heat exchanger may include an ice bin, a water tank, a cold plate, or a remote recirculation system.

[0081] 13 illustrates an exemplary fluid circuit 1400 having multiple independently controlled paths from a single ingredient source 1402 to a nozzle 1012 suitable for implementing some embodiments of the present disclosure. The fluid circuit 1400 includes a manifold 1404 that supplies beverage ingredients to each independently controlled path. Each path includes a pump or metering device 1406, 1408, 1410 that supplies beverage ingredients from the ingredient source 1402 to the nozzle 1012. The pump or metering device 1406, 1408, 1410 may be configured as any of the fluid circuits 1100-1300 shown in FIGS. 11-13. By having multiple independently controlled paths from the ingredient source 1402 to the nozzle 1012, a wider range of flow rates is possible than using any one of the pumps or metering devices 1406, 1408, 1410. For example, only one of the pumps or metering devices 1406, 1408, 1410 may be activated for a first flow rate of the beverage component from the ingredient source. Multiple pumps or metering devices 1406, 1408, 1410 may be activated for a second flow rate of the beverage component from the ingredient source.

[0082] FIG. 14 illustrates an example block diagram of a control architecture 1500 that can be used to control a beverage dispenser 1504 suitable for implementing some embodiments of the present disclosure. As shown in FIG. 14, the control architecture 1500 may include a core dispensing module (CDM) 1006, a human machine interface (HMI) module 1504, a user interface (UI) 1502, and a machine bus (MBUS) 1005. The HMI 1504 may connect to or otherwise interface and communicate with at least one external device (e.g., a mobile device 1052 or a POS 1054) that is external to the beverage dispenser 1504. Additionally, the HMI 1504 may control and update display screens on the UI 1502. The CDM 1506 may control flows from multiple pumps and / or valves 1510 in the beverage dispenser 1504 according to a recipe for mixing and dispensing a product (e.g., a beverage) from the beverage dispenser 1504.

[0083] Beverage ingredients (e.g., minor ingredients, macro ingredients, and / or diluents) may be combined to dispense a variety of products, which may include a beverage or blended beverage (i.e., a final beverage product) from the beverage dispenser 1504. However, the beverage dispenser 1504 may also be configured to dispense beverage ingredients individually.

[0084] An example of a control architecture 1500 for a beverage dispenser 1504 may be described in U.S. Patent Application No. 61 / 987,020, entitled "Dispenser Control Architecture," filed May 1, 2014, the entire contents of which are incorporated herein by reference. The MBUS 1005 may facilitate communication between the HMI 1504 and the CDM 1506 via one or more API calls. The HMI 1504, MBUS 1005, and CDM 1506 may collectively include common core components implemented as hardware or a combination of hardware and software that are adaptable to provide customization capabilities in the beverage dispenser 1504. The beverage dispenser 1504 may further include a memory storage device and a processor. An example of UI 1502 can be described in U.S. patent application Ser. No. 61 / 877,549, entitled "Product Categorization User Interface for a Dispensing Device," filed Sep. 13, 2013, the entire contents of which are incorporated herein by reference.

[0085] The UI 1502 may detect which area of ​​the touch screen is touched by a user (e.g., user 108). In response, the UI 1502 may transmit data to the HMI 1504 regarding where the touch screen was touched. In response, the HMI 1504 may interpret this received data and determine whether to cause the UI 1502 to display a different UI screen or to issue a command to the CDM 1506. For example, the HMI 1504 may determine that the user touched a portion of the touch screen that corresponds to a beverage brand. In response, the HMI 1504 may issue a command to the CDM 1506 to dispense the corresponding beverage brand. In response to receiving the command to dispense the corresponding beverage brand, the CDM 1506 then issues a command over one or more control buses 1508 to a pump or metering device 1510 for the beverage ingredient needed to dispense the beverage brand. Alternatively, the HMI 1504 may determine that the user touched a portion of the touch screen that corresponds to a request for another screen. In response, the HMI 1504 may cause the UI 1502 to display the request screen.

[0086] In some embodiments, the UI 1502 on the beverage dispenser 1504 may be utilized to select and dispense one or more beverages individually. The beverages may be dispensed as beverage components in a continuous dispense operation that continues to dispense one or more selected beverage components while a dispense input is actuated by the user, or in a batch dispense operation that dispenses a predetermined volume of one or more selected beverage components (e.g., one ounce at a time). The UI 1502 may be manipulated through a number of methods to select and dispense beverages. For example, a user may interact with the UI 1502 through 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 on-screen or physical keyboard (not shown) on the beverage dispenser 1504 to select and navigate one or more menus from which to select and dispense a beverage. As a further example, a user may interact with the HMI 1504 through a user interface of an application on the mobile device 1052.

[0087] The UI 1502, which may include a touch screen and touch screen controllers, may be configured to receive various commands from a user (i.e., consumer input) in the form of touch input and, in response to receiving such commands, generate graphical output and / or perform one or more actions on the beverage dispenser 1504 (e.g., via the HMI 1504 and / or CDM 1506). A touch screen driver in the HMI 1504 may be configured to receive consumer or customer input and then generate events (e.g., touch screen events) that can be communicated via the controller to an operating system of the HMI 1504.

[0088] The beverage dispenser 1504 may be in communication with one or more external devices, such as a mobile device 1052 or a POS 1054. In some embodiments, communication between the beverage dispenser 1504 and the external devices may be accomplished using any number of communication techniques, including, but not limited to, short-range wireless technologies such as Bluetooth, Wi-Fi, and other wireless or wired communication standards or technologies via a communication interface.

[0089] 15 illustrates an example computer system 1600 suitable for implementing some embodiments of the disclosure. For example, one or more components or controller components of the beverage dispenser 1504 may be implemented as the computer system 1600. In some implementations, one or both of the HMI 1504 and the CDM 1506 may be implemented as the computer system 1600.

[0090] It should be understood that the logical operations described herein for the various figures can be implemented as (1) a sequence of computer-implemented operations or program modules (i.e., software) running on a computing device (e.g., the computing device described in FIG. 16), (2) logic circuits or circuit modules (i.e., hardware) within a computing device, and / or (3) a combination of software and hardware on a computing device. Thus, the logical operations described herein are not limited to any particular combination of hardware and software. The implementation is a matter of choice depending on the performance and other requirements of the computing device. Thus, the logical operations described herein are variously referred to as operations, structural devices, operations, or modules. These operations, structural devices, operations, and modules can be implemented in software, firmware, special purpose digital logic, and any combination thereof. It should also be understood that more or fewer operations can be performed than those shown and described herein. These operations can also be performed in orders different than those described herein.

[0091] Reference is now made to FIG. 15, which illustrates an example of a computing device 1600 on which embodiments of the present invention may be implemented. For example, each of the beverage dispenser 102, server 118, mobile device 122, POS device 124, beverage dispenser 1004, mobile device 1052, POS 1054, and remote server 1058 described herein may be implemented as a computing device (e.g., computing device 1600). The example computing device 1600 is intended to be only one example of a suitable computing environment on which embodiments of the present invention may be implemented. Optionally, computing device 1600 may be any well-known computing system, including, but not limited to, a personal computer, a server, a handheld or laptop device, a multiprocessor system, a microprocessor-based system, a networked personal computer (PC), a minicomputer, a mainframe computer, an embedded system, and / or a distributed computing environment including a plurality of the above-mentioned systems or devices. A distributed computing environment enables remote computing devices connected to a communications network or other data transmission medium to perform a variety of tasks. In a distributed computing environment, program modules, applications and other data may be stored in local and / or remote computer storage media.

[0092] In some embodiments, computing device 1600 may include two or more computers in communication with each other that cooperate to perform a task. For example, and not by way of limitation, an application may be divided in a manner that allows for simultaneous and / or parallel processing of the application's instructions. Alternatively, data processed by an application may be divided in a manner that allows for simultaneous and / or parallel processing of different portions of the data set by two or more computers. In some embodiments, virtualization software may be used by computing device 1600 to provide the functionality of many servers that are not directly bound to the number of computers in computing device 1600. For example, virtualization software may provide 20 virtual servers on four physical computers. In some embodiments, the above functionality may be provided by running an application and / or multiple applications in a cloud computing environment. Cloud computing may include providing computing services over a network connection using dynamically scalable computing resources. Cloud computing may be at least partially supported by virtualization software. Cloud computing environments may be established by businesses and / or rented as needed from third party providers. Some cloud computing environments may include cloud computing resources that are owned and operated by an enterprise, as well as cloud computing resources that are rented and / or leased from third party providers.

[0093] In its most basic configuration, a computing device 1600 typically includes at least one processing unit 1620 and a system memory 1630. Depending on the exact configuration and computing device, the system memory 1630 may be volatile (e.g., random access memory (RAM)), non-volatile (e.g., read only memory (ROM), flash memory, etc.), or a combination of the two. This most basic configuration is illustrated in FIG. 16 by dashed line 1610. The processing unit 1620 may be a standard programmable processor that performs arithmetic and logical operations necessary for the operation of the computing device 1600. Although only one processing unit 1620 is shown, multiple processors may be present. Thus, although instructions are described as being executed by one processor, the instructions may be executed by one or multiple processors simultaneously, serially, or otherwise. The computing device 1600 may further include a bus or other communication mechanism for communicating information between various components of the computing device 1600.

[0094] Computing device 1600 may have additional features / functionality. For example, computing device 1600 may include additional storage (e.g., removable storage 1640 and non-removable storage 1650), including, but not limited to, magnetic or optical disks or tape. Computing device 1600 may further include a network connection 1680 that allows the device to communicate with other devices, for example, over communications paths as described herein. Network connection 1680 may take the form of a modem, a collection of modems, an Ethernet card, a Universal Serial Bus (USB) interface card, a serial interface, a token ring card, a Fiber Optic Distributed Data Interface (FDDI) card, a Wireless Local Area Network (WLAN) card, a radio transceiver card (e.g., Code Division Multiple Access (CDMA)), a Global System for Mobile Communications (GSM), Long Term Evolution (LTE), WiMAX, and / or other air interface protocol radio transceiver cards, and other well-known network devices. Computing device 1600 may further include input devices 1670 (e.g., a keyboard, keypad, switches, dials, a mouse, a trackball, a touch screen, a voice recognition device, a card reader, a paper tape reader, or other known input devices). It may further include output devices 1660 (e.g., a printer, a video monitor, a liquid crystal display (LCD), a touch screen display, speakers, etc.). Additional devices may be connected to the bus to facilitate communication of data between components of computing device 1600. All these devices are well known in the art and need not be described at length here.

[0095] The processing unit 1620 may be configured to execute program code encoded on a tangible computer-readable medium. Tangible computer-readable medium refers to any medium that can provide data that causes the computing device 1600 (i.e., machine) to operate in a specific manner. A variety of computer-readable media may be utilized to provide instructions to the processing unit 1620 for execution. Examples of tangible computer-readable media may include, but are not limited to, volatile, non-volatile, removable, and non-removable media implemented in any method or technology for storage of information (e.g., computer-readable instructions, data structures, program modules, or other data). The system memory 1630, the removable storage 1640, and the non-removable storage 1650 are all examples of tangible computer-readable media. Examples of specific computer readable recording media include, but are not limited to, an integrated circuit (e.g., a field programmable gate array or an application specific integrated circuit), a hard disk, an optical disk, a magneto-optical disk, a floppy disk, a magnetic tape, a holographic storage medium, a solid state device, a RAM, a ROM, an electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, a CD-ROM, a digital versatile disk (DVD) or other optical storage device, a magnetic cassette, a magnetic tape, a magnetic disk storage device or other magnetic storage device.

[0096] It is essential to electrical and software engineering techniques to be able to convert functions executable by loading executable software into a computer into a hardware implementation by well-known design rules. The decision between implementing a concept in software versus hardware is typically driven by considerations of design stability and the number of units to be manufactured, rather than any issues with converting from the software domain to the hardware domain. Generally, for designs that are subject to frequent changes, implementation in software is preferred, since redesigning a hardware implementation is more expensive than redesigning a software design. Generally, for stable designs that are mass-produced, implementation in hardware (e.g., application specific integrated circuits (ASICs)) is preferred, since a hardware implementation may be less expensive than a software implementation for a mass production process. Often, designs are developed and tested in software form, and may later be converted by well-known design rules into an equivalent hardware implementation in an application specific integrated circuit that hardwires the software's instructions. In the same way that a machine controlled by a new ASIC is a specific machine or device, a computer that has been programmed and / or loaded with executable instructions may similarly be considered a specific machine or device.

[0097] In an example implementation, processing unit 1620 may execute program code stored in system memory 1630. For example, a bus may carry data to system memory 1630, where processing unit 1620 receives and executes instructions. Optionally, data received by system memory 1630 may be stored on removable storage 1640 or non-removable storage 1650 before or after execution by processing unit 1620.

[0098] It is understood that the various techniques described herein can be implemented in hardware or software, or in conjunction with hardware and software, as appropriate. Thus, the methods and apparatus of the presently disclosed subject matter, or certain aspects or portions of the subject matter, may take the form of program code (i.e., instructions) embodied in a tangible medium (e.g., a floppy diskette, a CD-ROM, a hard drive, or any other machine-readable storage medium), and when the program code is loaded into and executed by a machine (e.g., a computing device), the machine becomes an apparatus that implements the presently disclosed subject matter. In the case of program code execution on a programmable computer, the computing device typically includes a processor, a processor-readable storage medium (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device. One or more programs may, for example, use application programming interfaces (APIs), reusable controls, and the like to implement or utilize the processes described in conjunction with the presently disclosed subject matter. To communicate with a computer system, such programs may be implemented in a high-level procedural or object-oriented programming language. However, the programs may be implemented in assembly language or machine language, as appropriate. In any event, the language may be a compiled or interpreted language, and the language may be combined with hardware implementations.

[0099] Embodiments of methods and systems may be described herein with reference to block diagrams and flowchart illustrations of methods, systems, apparatus, and computer program products. Each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, may be implemented by computer program instructions. These computer program instructions may be loaded into a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, executing on the computer or other programmable data processing apparatus, create means for performing the function specified in the flowchart block or block.

[0100] These computer program instructions may further be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture that includes computer readable instructions that implement the functions specified in the flowchart block or blocks. Furthermore, the computer program instructions may be loaded into a computer or other programmable data processing apparatus such that a sequence of operational steps to be performed on the computer or other programmable apparatus creates a computer implemented process, such that the instructions executing on the computer or other programmable apparatus provide the steps to implement the functions specified in the flowchart block or blocks.

[0101] Thus, the blocks in the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. Further, it is understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by the specified functions or steps, or by dedicated hardware and dedicated hardware-based computer systems that execute computer instructions.

[0102] Although several embodiments are provided in this disclosure, it is understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of the disclosure. The examples should be considered illustrative and not limiting, and the intention should not be limited to the details set forth herein. For example, various elements or components may be combined or integrated into another system or certain features may be omitted or not implemented.

[0103] Additionally, the techniques, systems, subsystems, and methods described and illustrated in various embodiments, either discretely or separately, may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items illustrated or described as being directly coupled or in communication with one another may be indirectly coupled or in communication through some interface, device, or intermediate component, whether electrical, mechanical, or otherwise. Other examples of changes, substitutions, and alterations will be ascertainable by one of ordinary skill in the art and may be made herein without departing from the spirit and scope of the present disclosure.

Claims

1. 1. A computerized system for beverage order fulfillment, comprising: a first computer connected in two-way electronic communication with at least one server over a network; a beverage dispenser including a processor and a computerized memory storing beverage dispensing software in the beverage dispenser, the beverage dispenser being in electronic communication with the at least one server over the network and configured to communicate for each instance of beverage execution a verification token that confirms authenticity of electronic communications between the first computer, the at least one server, and the beverage dispenser; web browser software stored on the first computer, the web browser software configured to initiate a communications session with the at least one server; an interactive graphical user interface (GUI) displayed on the first computer via a web browser, the interactive GUI being configured and updated by communication from the at least one server; data entry options displayed on the interactive GUI for the first computer for communicating beverage selection commands to the beverage dispensing software via the at least one server at each instance of the beverage execution; A computerized system comprising:

2. 2. The computerized system of claim 1, further comprising a WebSocket Application Program Interface (API) stored on the at least one server and configured to connect to the beverage dispenser and the Web browser software on the first computer.

3. 10. The computerized system of claim 1, further comprising an encryption program stored in the computerized memory of the beverage dispenser.

4. The computerized system of claim 3 , wherein the encryption program is configured to generate the verification token for each of the instances of beverage execution.

5. 5. The computerized system of claim 4, wherein the encryption program is further configured to incorporate the verification token into a QR code displayed on the beverage dispenser via a beverage dispenser display, and the beverage dispenser communicates each of the verification tokens encoded by the QR code to the at least one server for each instance of beverage execution.

6. 6. The computerized system of claim 5, further comprising an in-use icon displayed on the beverage instance display during each said instance of a beverage run.

7. 10. The computerized system of claim 1, wherein the beverage dispenser further comprises a customer user interface and a non-customer user interface connecting a beverage dispenser display to the processor and the computerized memory of the beverage dispenser.

8. 2. The computerized system of claim 1, wherein the first computer is a mobile device further comprising a camera and configured to initiate the web browser software and provide a beverage selection experience on the camera that processes a QR coded image displayed on the beverage dispenser.

9. 10. The computerized system of claim 8, wherein the image is a QR code that includes a verification token and a web address that launches a website on the mobile device that corresponds to beverage execution software on the beverage dispenser.

10. The beverage dispenser comprises: a beverage dispenser display connected to said processor and to said computerized memory; a nozzle configured to dispense a selected beverage; a plurality of pumps and / or metering devices each configured to deliver beverage ingredients for the selected beverage from an ingredient source to the nozzle according to commands executed by the beverage dispensing software; a communication device configured to connect the beverage dispenser to the at least one server and to receive beverage selection commands from the at least one server; The computerized system of claim 1 , comprising:

11. 11. The computerized system of claim 10, further comprising an encryption program stored in the computerized memory of the beverage dispenser.

12. The computerized system of claim 11 , wherein the encryption program is configured to generate a verification token for each instance of a beverage execution.

13. 13. The computerized system of claim 12, wherein the encryption program is further configured to incorporate the verification token into a QR code displayed on the beverage dispenser via a beverage dispenser display, and the beverage dispenser communicates each of the verification tokens and the QR code to the at least one server for each instance of beverage execution.

14. 14. The computerized system of claim 13, further comprising an in-use icon displayed on the beverage dispenser display during each said instance of a beverage run.

15. 11. The computerized system of claim 10, further comprising a customer user interface and a non-customer user interface connecting the beverage dispenser display to the processor and the computerized memory of the beverage dispenser.

Images