HK1149104A - Method for consumer-dispenser interactions - Google Patents

Description

Method for consumer interaction with a dispenser

Trade mark

COCA-Is a registered trademark of Coca-Cola corporation, Atlanta, Georgia, USA. Other names, symbols, designs or logos used herein may be registered trademarks, trademarks or product names of Coca-Cola corporation or other companies.

Technical Field

The present invention relates to product dispensers, and in particular, to systems and methods for consumer-dependent interaction with dispensers.

Background

Conventional beverage dispensers may fill a beverage by combining syrup, sweetener, and/or water. To create a limited variety of beverage options, different types of syrups may be provided. Typically, this results in the ability to offer a limited number of branded and non-branded beverage options. For example, a single prior art dispenser using several different types of syrups may be able to provide COCA-COLA^TM、DIETCOCA-COLA^TM、SPRITE^TMAnd several other branded or non-branded beverage choices.

One problem with these types of conventional beverage dispensers is that only a limited number of beverages can be provided. As such, conventional beverage dispensers are limited in their ability to provide consumers with the beverage they desire. In this regard, consumers desire a richer menu of beverage choices and the ability to customize their beverages. Studies have shown that they require more beverage variation, even for traditional brands of beverages. For example, COCA-COLA is provided^TMCOCA-COLA containing lime^TM、CHERRY COCA-COLA^TM、VANILLA COCA-COLA^TMAnd many other types of COCA-COLA^TMThe beverage changes. In part due to the limited capacity and selection function of conventional beverage dispensers, such as the COCA-COLA in conventional beverage dispensers^TMIs impractical to provide all possible variations. It does not provide the consumer with a complete selection of brands and non-brands of beverages that the consumer wants, i.e., all types.

Summary of The Invention

Some or all of the above needs and/or problems may be addressed by embodiments of the present invention. Certain embodiments of the invention may include systems and methods for facilitating consumer interaction with a dispenser. In one embodiment, a product dispenser is provided. The product dispenser may include a user interface operable to interact with a consumer and receive at least one input from the consumer. The product dispenser may also include a controller including a set of instructions operable to receive a request from a consumer to dispense a customized product. Additionally, the controller may further comprise a set of instructions to present, via the user interface, a list of selectable product ingredients or at least one of adjustable product formulation parameters. Additionally, the controller can further include a set of instructions to dispense the product based at least in part on one or more of the selectable ingredients or selected formulation parameters.

In another embodiment, a method for operating a product dispenser is provided. The method may include receiving a request from a consumer to dispense a customized product. Additionally, the method may include presenting at least one of a list of selectable product ingredients or adjustable product formulation parameters based at least in part on information associated with the consumer. Additionally, the method may include receiving input regarding at least one of selectable product ingredients or product formulation parameters. Additionally, the method may include dispensing the product based at least in part on one or more of the selectable product ingredients or product formulation parameters.

In yet another embodiment, a method for operating a product dispenser may be provided. The method may include receiving information associated with a consumer. Additionally, the method may include presenting, via a user interface associated with the product dispenser, at least one product recipe comprising at least one selectable product ingredient or adjustable product formulation parameter based at least in part on the information associated with the consumer. Additionally, the method may include receiving consumer input regarding at least one of the selectable product ingredients or product formulation parameters. The method may further comprise dispensing the product based at least in part on one or more of the selected product ingredients or product formulation parameters.

In another embodiment, the product dispenser may include a user interface operable to interact with a consumer and receive at least one input from the consumer. Additionally, the product dispenser may include a controller including a set of instructions operable to receive information associated with a consumer. Additionally, the controller may further include a set of instructions operable to present, via a user interface associated with the product dispenser, at least one product recipe comprising at least one selectable product ingredient or adjustable product formulation parameter based at least in part on information associated with the consumer. Additionally, the controller may further comprise a set of instructions operable to receive consumer input regarding at least one of selectable product ingredients or product formulation parameters. Additionally, the controller may further comprise a set of instructions operable to dispense a product based at least in part on one or more of selected product ingredients or product formulation parameters.

In yet another embodiment, a system may be provided. The system may include a communication network, a plurality of product dispensers in communication with the network. Each product dispenser may include a user interface operable to interact with a consumer and receive at least one input from the consumer. Additionally, each product dispenser may include a controller including a set of instructions operable to receive information associated with a consumer over a network. Additionally, the controller may further include a set of instructions operable to present, via a user interface associated with the product dispenser, at least one product recipe comprising at least one selectable product ingredient or adjustable product formulation parameter based at least in part on information associated with the consumer. Additionally, the controller may further comprise a set of instructions operable to receive consumer input regarding at least one of selectable product ingredients or product formulation parameters. The controller may also include a set of instructions operable to dispense a product based at least in part on one or more of a selected product ingredient or product formulation parameter.

Additional systems, methods, distributors, features and aspects are enabled by the techniques of various embodiments of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention. Other aspects and features may be understood with reference to the description and the drawings.

Brief description of the drawings

The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other objects, features, and aspects of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:

FIG. 1 illustrates an example system including a product dispenser and associated network in accordance with an embodiment of the present invention.

FIG. 2 shows an example of a consumer diet (refreshment) network in accordance with an embodiment of the present invention.

FIG. 3 illustrates an example of an enhanced view graphical user interface in accordance with an embodiment of the present invention.

FIG. 4 shows one example of a classic view graphical user interface according to an embodiment of the invention.

FIG. 5 illustrates an example method of storing a recipe in a recipe list in accordance with an embodiment of the present invention.

FIG. 6 illustrates an example method of customized product formulation in accordance with an embodiment of the present invention.

FIG. 7 illustrates an example method of allowing a consumer to make his or her own recipe in accordance with an embodiment of the present invention.

FIG. 8 illustrates an example method of allowing a consumer to manage a recipe list configuration file (profile) using a website in accordance with an embodiment of the present invention.

FIG. 9 illustrates an example method of allowing a consumer to select between a standard product menu and its recipe list profile in accordance with an embodiment of the present invention.

FIG. 10 illustrates an example method of charging a product based on a volume of product dispensed and paying for the product via a cashless payment implementation in accordance with an embodiment of the present invention.

FIG. 11 illustrates an example method of charging a product based on a volume of product dispensed and paying for the product by pre-payment in accordance with an embodiment of the present invention.

The detailed description explains various embodiments of the invention, together with aspects and features, by way of example with reference to the drawings.

Detailed description of embodiments of the invention

As used herein, the terms "beverage forming dispenser," "product dispenser," "beverage dispenser," "dispenser apparatus," and "dispenser" refer to an apparatus that dispenses a product, such as a beverage, can, bottle, or container.

As used herein, the terms "product" and "beverage" and plural forms thereof are used synonymously, and embodiments of the invention should not be limited in scope by the use of either term.

Turning now to a more detailed illustration, an example system 100 for a product dispenser according to an embodiment of the present invention is shown in FIG. 1. The example system, e.g., 100, may operate in a networked computer environment including at least one network in communication with a product dispenser. For example, in fig. 1, the product dispenser 102A is shown in communication with a communication network 104. In this embodiment, at least one product dispenser, such as 102A, may interface with a consumer, customer, or other user. Other example environments or systems for product dispensers according to embodiments of the present invention may include non-network configurations.

An example product dispenser, such as 102A shown in fig. 1, may be a client-type device. Each of the product dispensers 102A-102N may be a computer or processor based device capable of communicating with the communication network 104 via signals, such as radio frequency signals or direct wired communication signals.

Each product dispenser, e.g., 102A, may include a processor or controller 106, an identification reader/scanner device 106A, an ingredient matrix (ingredient matrix)108, a computer readable medium, e.g., Random Access Memory (RAM)110, coupled to the processor or controller 106, and an input/output device, e.g., a display device 112. The processor or controller, e.g., 106, may execute computer-executable program instructions stored in a memory, e.g., 110. The computer-executable program instructions stored in the memory, e.g., 110, may include any number of modular applications, e.g., consumer interaction engines or modules, e.g., 114. The consumer interaction engine or module, such as 114, may be adapted to implement various methods of consumer-dispenser interaction. Additionally, the consumer interaction engine or module, e.g., 114, may be adapted to receive one or more signals from one or more consumers, remote and/or local servers or data processing resources, as well as client type devices or wireless communication devices. Other examples of functions and aspects of embodiments of the consumer interaction engine or module, e.g., 114, are described below.

The identification reader/scanner device 106A shown in fig. 1 may be in communication with the controller 106 and may receive or otherwise obtain identification information from any number of devices or apparatuses associated with a consumer. For example, the identification reader/scanner devices such as 106A may include machine-readable code technology such as bar codes, or may include any wireless communication technology such as RFID, reflected light frequency, optical, and the like.

As shown in fig. 1, a processor or controller, e.g., 106, may communicate with a component matrix, e.g., 108, to control, monitor and track the addition, flow and removal of some or all of the components to or from the matrix, e.g., 108. The ingredient matrix may be, for example, a series of containers or fixtures capable of receiving or mounting to individual product ingredient packages or other product ingredient supplies. For example, the product component packs, e.g., 116A, may be fabricated as liquid pouches secured in plastic ridged containers to allow insertion into the component matrix, e.g., 108. When inserted into the ingredient matrix, e.g., 108, the bag, e.g., 116A, or pouch, may be pierced by at least one associated fitment, which allows the liquid within the bag, e.g., 116A, or pouch, to be pumped out, or otherwise metered by the controller, e.g., 106, or matrix, e.g., 108, and associated equipment in precise proportions to form a desired product, e.g., a beverage. In one embodiment, one or more product component packages, e.g., 116A-116Q, may be inserted into a component matrix, e.g., 108. In this embodiment, the ingredient matrix, e.g., 108, may secure some or all of the product ingredient packages, e.g., 116A-116Q. In one embodiment, one or more product packages, e.g., 116O, 116P, 116Q, may be supplied directly rather than in package form. For example, a product package such as 116O may be a continuous supply of carbonated water provided by a carbonated water source; product packages such as 116P may be sweeteners provided by sweetener sources, such as non-nutritive sweeteners (NNS) or High Fructose Corn Syrup (HFCS); and product package such as 116Q may be a continuous supply of water from a faucet, purified or distilled water source. In any embodiment, the ingredients, compositions, or product additives may be in the form of pouches, or may be in other configurations suitable for access by a matrix of ingredients, such as 108.

In the embodiment shown in FIG. 1, a product dispenser, e.g., 102A, having a matrix of ingredients, e.g., 108, may include one or more machine code readers, e.g., 118A-118Q, using machine code technology, e.g., bar codes, RFID, reflected light frequencies, optical, etc. In one embodiment, at least one machine readable code reader, e.g., 118A-118Q, may be associated with a location associated with an ingredient matrix, e.g., 108, wherein some or all product ingredient packages, e.g., 116A-116Q, may be scanned, read, or otherwise identified prior to being inserted into or connected to the ingredient matrix, e.g., 108. In this regard, a processor or controller, e.g., 106, may receive or retrieve information related to some or all of the product component packages, e.g., 116A-116Q, and use such information to identify an optimal or other desired location in the component matrix, e.g., 108, for placement of the product component package, e.g., 116A, in the component matrix, e.g., 108. For example, data from a product component package, e.g., 116A, may be read, scanned, or identified from a serial number or identification code associated with the product component package, e.g., 116A. Such data may be used alone or in association with information previously stored in at least one database, such as 128A-128C described below, or in association with data that may be otherwise acquired or stored by a data processing resource or server, such as 126, described below, which may identify one or more ingredients associated with a product ingredient package, such as 116A, for example. In another example, the data from the product component package, e.g., 116A, can be a component code or identifier, and can be used alone or associated with information previously stored in a database, e.g., 128A-128C described below, or with data that can be otherwise acquired or stored by a data processing resource or server, e.g., 126, that can identify one or more components associated with the product component package, e.g., 116A.

In the embodiment shown in FIG. 1, a product dispenser, e.g., 102A, having an ingredient matrix, e.g., 108, may include one or more pumps and/or valves, e.g., 120 and 122, respectively, and a nozzle, e.g., 124. In this example, each of the pumps, e.g., 120, and valves, e.g., 122, may be controlled by the product dispenser, e.g., 102A. For example, a processor or controller such as 106 may be in communication with some or all of the pumps such as 120 and valves such as 122. In this regard, some or all of the pumps, e.g., 120, and/or valves, e.g., 122, may be selectively operated by a processor or controller, e.g., 106, to pump, meter, or otherwise obtain individual products or ingredients from certain product ingredient packages, e.g., 116A-116Q, to dispense a customized product or beverage.

In one embodiment, an ingredient matrix, e.g., 108, may have a plurality of product ingredient packages, e.g., 116A-116Q, inserted therein, wherein each packageMay contain different or unique components. The various ratios of ingredients from some or all of the product ingredient packages, e.g., 116A-116Q, may be selectively combined by way of one or more commands or instructions from a processor or controller, e.g., 106, to one or more pumps, e.g., 120, and/or valves, e.g., 122, associated with the ingredient matrix, e.g., 108, to form various types of products, e.g., beverages. Example ingredients may include, but are not limited to, flavorings, concentrates, syrups, sweeteners, water, carbonated water, lime flavorings, vanilla flavorings, CHERRY flavorings, and branded or non-branded beverages such as CHERRY COCA-COLA^TM、VANILLACOCA-COLA^TM、COCA-COLA^TM、DIET COCA-COLA^TMAnd FANTA^TMAny of the component parts of (a).

In one embodiment, one or more product component packs, e.g., 116A-116Q, can contain components known as "pungency" (which can limit their placement in a matrix of components, e.g., 108). The spicy component may be relatively strong such that once the spicy component is pumped or drawn through a particular portion of the product dispenser, e.g., 102A, any associated pathway through the dispenser, e.g., 102A, such as a tube in the product dispenser, e.g., 102A, may be permanently flavored and any subsequent component or fluid pumped or drawn through the pathway or tube may be tainted with the flavor of the spicy component. Thus, once a spicy type ingredient is used in an ingredient matrix such as 108, an associated processor or controller such as 106 may track or otherwise store information that controls or limits the replacement and/or addition of other spicy ingredients to certain locations in the ingredient matrix such as 108 to avoid mixing spicy type ingredients or staining non-spicy ingredients to maintain the quality of the product or beverage.

In another embodiment, one or more product component packs, e.g., 116A-116Q, may require shaking to keep the relevant components well mixed. In such a case, the location of such components in the component matrix, e.g., 108, may be limited to locations in the component matrix, e.g., 108, that may be needed and/or desired to be panned in a particular implementation.

In another embodiment, ingredients from one or more product ingredient packages, such as 116A-116Q, may be dispensed through an antimicrobial tube or dispenser piece. Such ingredients may include, but are not limited to, milk, dairy products, soy sauce, and/or other types and kinds of product ingredients. In such cases, the location of such components in the component matrix, e.g., 108, may be limited to the location of the appropriate antimicrobial tubes and/or dispenser parts in the component matrix, e.g., 108, as may be needed and/or desired with a particular implementation.

In yet another embodiment, a one-to-one relationship may be established between a particular product component package, e.g., 116A, and at least one pump and/or valve, e.g., 120 and/or 122, respectively. In some cases, the use of more than one pump and/or valve for a single product ingredient package, e.g., 116A, may draw a relatively high volume of the ingredient from the package, e.g., 116A, in a relatively short period of time. For example, a product component package containing a sweetener, such as sweetener e.g., 116P, may use more than one pump and/or valve to draw a relatively high volume of the component from the package 116P in a relatively short period of time.

Returning to FIG. 1, any number of other product dispensers, e.g., 102A-102N, may also be in communication with a network, e.g., 104. In one embodiment, a communication network such as 104 shown in FIG. 1 may be a Local Area Network (LAN). In another embodiment, the communication network may be a wireless communication network capable of transmitting both a sound signal and a data signal including an image data signal or a multimedia signal. Other networks may include, but are not limited to, the internet, a Local Area Network (LAN), a Wide Area Network (WAN), a LON WORKS network, a wired network, a wireless network, or any combination thereof.

The network, e.g., 104 in FIG. 1, is also shown in communication with at least one data processing resource, e.g., server 126, and at least one database, e.g., 128A. In this embodiment, the server, e.g., 126, may be a processor-based device capable of communicating with some or all of the product dispensers, e.g., 102A-102N, via the communication network, e.g., 104, in signals, e.g., radio frequency signals or direct wired communication signals. Additionally, data processing resources or servers such as 126 may be used to assist or facilitate recipes, formulations, methods of making products or beverages, provide operational data processing, perform data processing related to consumer interaction, and/or perform other data processing as may be needed and/or desired in a particular embodiment. Such actionable data processing may include, for example and without limitation, device status, maintenance, service reminders, pre-save (predigestock), and/or other types and kinds of actionable data processing that may be needed and/or desired in a particular implementation. Such consumer interaction support may include, for example, without limitation, consumer preferences, consumer product or beverage preferences, loyalty, countermeasures, prizes, media content, customizations, and/or other types and kinds of consumer interaction and/or data processing support that may be needed and/or desired for a particular implementation.

The server, e.g., 126 in fig. 1, may include a processor, e.g., 130, and a computer-readable medium, e.g., Random Access Memory (RAM)132, coupled to the processor 130. The processor, e.g., 130, may execute computer-executable program instructions stored in the memory, e.g., 132. The computer-executable program instructions stored in the memory, e.g., 132, may include any number of modular applications, e.g., a consumer interaction engine or module similar to 114. A consumer interaction engine or module similar to 114 may be adapted to implement various methods of consumer interaction. Additionally, a consumer interaction engine or module similar to 114 may be adapted to interact with one or more consumers and one or more servers or data processing resources. Other examples of the functionality and aspects of embodiments of the consumer interaction engine or module similar to 114 are described below.

Through a network, such as 104 in fig. 1, some or all of the product dispensers, such as 102A-102N, may retrieve, receive, or otherwise access information stored in some or all of databases, such as databases of recipes, and methods of making products or beverages, such as 128A, operational databases, such as 128B, and consumer databases, such as 128C. In any case, the one or more databases can include product or beverage forming information, such as one or more product or beverage formulation, and method of making the product or beverage. Such product or beverage formulations, methods of making products or beverages can include ingredient lists, ratios of each ingredient, lists of how the product or beverage can be customized by the consumer, and/or other types and kinds of product or beverage formulations, methods of making products or beverages that may be needed and/or desired for a particular implementation.

In one embodiment, a product dispenser such as 102A may be configured to print coupons (coupon) or other documents. In the illustrated embodiment, an associated printer or other output device, such as 134, may be in communication with the product dispenser, such as 102A. In other embodiments, a printer or other output device may communicate with a product dispenser, such as 102A, via a network, such as 104.

An example environment or system, such as 100 shown in FIG. 1, may facilitate customer, consumer, and user interaction with product dispensers and networks. For example, and without limitation, a user, such as a consumer, may make a product or beverage type selection on a product dispenser, such as 102A, via an input/input device, such as display device 112. An associated processor or controller, e.g., 106, may facilitate user selection of a particular recipe to form a selected product or beverage via a display device, e.g., 112. The processor or controller, e.g., 106, may display one or more products or beverages for selection via a display device, e.g., 112. The user may use the display device, e.g., 112, to select at least one product or beverage, e.g., by pressing a button provided by or associated with the display device 112. The processor or controller, e.g., 106, may retrieve information from a local memory, e.g., 110, or may communicate with at least one database, e.g., 104, over a network, e.g., or may communicate with at least one data processing resource, e.g., server 126, to retrieve the respective ingredients and/or proportions of ingredients used to form the selected product or beverage. The processor or controller, e.g., 106, may use the information to operate one or more pumps, e.g., 120, and/or valves, e.g., 122, to form and dispense a product or beverage through a nozzle, e.g., 124, into a cup or other container, e.g., 136.

In another embodiment, a user, such as a customer or package installer, may assist in scanning or reading one or more product component packages, such as 116A-116Q, as the packages 116A-116Q are inserted into the component matrix, such as 108, associated with the product dispenser, such as 102A. A processor or controller, e.g., 106, associated with the product dispenser, e.g., 102A, may identify the best or selected location in the composition matrix, e.g., 108. A user, customer, or package installer may know where a particular product component package, e.g., 116A, may be placed in a component matrix, e.g., 108, by way of an input/output device, e.g., a display device, e.g., 112. Examples of display devices may include, but are not limited to, Light Emitting Diode (LED) display indicators, LCD screens, input/output (I/O) interfaces, audio interfaces, or other types and kinds of displays or indicators as may be needed and/or desired in a particular embodiment.

In one embodiment, insertion of a particular product component package, e.g., 116A, into an ingredient matrix, e.g., 108, may be checked or otherwise verified by scanning the machine-readable code on the corresponding package, e.g., 116A, and scanning the machine-readable code located on the ingredient matrix, e.g., 108, at the insertion point (shown as 118A). In this regard, the associated processor or controller, e.g., 106, may check or verify that the product component package, e.g., 116A, is properly placed in the component matrix, e.g., 108.

In another embodiment, a cup such as 136 or other container may include identifying information such as an RFID or other machine readable tag such as 138 shown in FIG. 1 mounted on the cup. In some embodiments, the identifying information may be associated with the consumer by, for example, an RFID or other machine readable tag similar to 138 contained or otherwise attached to an icon or other object. A reader, such as an RFID or other machine readable code reader, e.g., 140, associated with the product dispenser, e.g., 102A, may receive or otherwise obtain identification information from an RFID or other machine readable tag similar to 138. As shown in fig. 1, a processor or controller, e.g., 106, associated with a product dispenser, e.g., 102A, may be in communication with an RFID or other machine readable reader, e.g., 140, and some or all of the identification information obtained from the RFID or other machine readable tag, e.g., 138, may be stored or otherwise processed by the processor or controller, e.g., 106. In this embodiment, the identification information may be embedded in a machine readable code, bar code, RFID, radio frequency, infrared or other wireless communication method or device, or other types and kinds of encoding and/or storage techniques as may be needed and/or desired in a particular embodiment. The RFID readers or machine-readable code readers such as 140 may be respective devices that read or receive identification information from RFID or other machine-readable tags such as 138, and may include RFID read/write devices, infrared devices, magnetic card readers, bar code readers, or other suitable reader or receiver technology as may be needed and/or desired in a particular implementation.

In yet another embodiment, a server or transaction processing resource, such as 142, may facilitate payment or payment processing when a consumer selects and attempts to pay for a product, such as a beverage, on a product dispenser, such as 102A. The associated processor or controller, e.g., 106, may receive the consumer's payment or related information before, during, or after selection of a particular product or beverage, e.g., by way of a display device, e.g., 112, data transmission, or other input. In any case, the processor or controller, e.g., 106, may transmit payment or related information to a server or transaction processing source, e.g., 142, over a network, e.g., 104. The server or transaction processing source, such as 142, may access at least one database, such as 128A-128C, or may be in communication with at least one data processing resource, such as 126, to authorize or otherwise confirm payment or related information prior to accepting payment from or otherwise dispensing a selected product or beverage for a consumer.

Referring to fig. 2, an example consumer dietary environment or system 200 is shown. In one embodiment, one or more networked product dispensers, such as 210, may be installed in a plurality of respective locations, such as location 202, respectively, and may communicate with a server or data processing resource, such as 206, and one or more data storage devices, such as database 208, via a network 204, such as the internet or a global network. By way of example, the product dispenser 210 may be similar to the beverage dispenser or dispenser device depicted in FIG. 1 as 102A. In one example, a product dispenser, such as 210, may include some or all of the following components with respect to FIG. 1: an ingredient matrix, e.g., 108, having locations operable to receive one or more packages of product ingredients, e.g., 116A-116Q, a controller, e.g., 106, one or more package insertion detection devices or RFID readers/writers, e.g., 118A-118Q, a pump, e.g., 120, a valve, e.g., 122, and a nozzle, e.g., 124. By way of further example, the server or data processing resource 206 may be similar to the server or data processing resource depicted as 126 in FIG. 1.

In one embodiment, one or more consumers, such as 212, may access a network, such as 104, or a consumer's dietary network, such as 204. Through the network 204, the consumer, e.g., 212, can register, set consumer preferences, access corresponding accounts, receive promotions, manage loyalty accounts (loyaltiy accounts), and/or register for other types and kinds of opportunities and services as may be needed and/or desired in a particular embodiment. In another embodiment, a consumer, such as 212, may choose to access the network 104, or a consumer's eating network system, such as 200, and one or more networked product dispensers, such as 210, by any number of client-type devices, including but not limited to Personal Computers (PCs), such as 214A, data processing devices, such as 214B, wireless communication devices, such as 214C, and/or by other types and kinds of data processing, processor-based, or client-type devices. Examples of wireless communication devices may include, but are not limited to, wireless data processing devices, wireless telephones, mobile telephones, IPHONEs^TM、IPOD^TMPersonal data assistant, and/or POCKET PC^TM。

Referring to FIG. 3, an example of an enhanced view graphical user interface 300 is shown. In one illustrated embodiment, a product dispenser, such as 210 in FIG. 2, may include at least one user interface, such as an enhanced view graphical user interface, such as 300, or a consumer interface. The user interface, e.g., 300, can be used, e.g., by a consumer, e.g., 212, to select any number of different product or beverage types, categories, and formulations. In use, a product dispenser, e.g., 210, with an enhanced view graphical user interface, e.g., 300, can provide a consumer with selectable product or beverage options in a series of dynamically generated menus, wherein the consumer can locate and select a specific brand, category, type and/or formulation of a desired corresponding product or beverage. Once a particular product or beverage option is selected, the consumer may cause the corresponding product or beverage to be dispensed and dispensed by the product dispenser.

Referring to FIG. 4, another example of a user interface is shown. In one embodiment, a product dispenser, such as 210 in FIG. 2, may include a classic view graphical user interface, such as 400. The user interface, e.g., 400, may be used by a consumer, e.g., 212, to select from a limited number of different product or beverage types, categories, and/or formulations. In use, a consumer, such as 212, may more easily select a product or beverage from a limited number of product or beverage choices. Once a particular product or beverage option is selected, the consumer may cause the corresponding product or beverage to be dispensed and dispensed by the product dispenser. In some embodiments, a classic type graphical user interface may also be referred to as a traditional view because it generally resembles a traditional sprinkler dispensing valve design. Thus, a classic type of graphical user interface may be referred to as a traditional view graphical user interface.

In one embodiment, the consumer may desire fewer product or beverage selections than are displayed by a product dispenser that allows for selection, for example, of a plurality of different types of products or beverages. In such cases, a classic view graphical user interface may be displayed having relatively fewer, more traditional product or beverage selections, and including one or more traditional types of product or beverage selections, to facilitate and sometimes expedite consumer interaction with the product dispenser.

In another embodiment, the consumer may choose to create consumer preferences that modify the type and/or kind of brand and/or product or beverage party displayed in a user interface, such as a classic view graphical user interface, essentially creating a consumer customized classic view graphical user interface. In this particular embodiment, the consumer may create a consumer customized classic view graphical user interface. For example, when a consumer identifies himself or herself to a product dispenser, such as 210, one or more consumer preferences may be retrieved by the dispenser 210. Based at least in part on one or more consumer preferences, product dispenser 210 may display a default user interface to the consumer, which may be an enhanced view graphical user interface, a classic view graphical user interface, or a classic view graphical user interface customized by the consumer.

Fig. 5-11 are exemplary flow diagrams of various methods according to embodiments of the invention. Some or all of the illustrated methods may be implemented by any combination of the systems, networks, product dispensers, or related components illustrated in fig. 1-4.

Referring to FIG. 5, a method 500 for storing recipes into a recipe list is shown. Method 500 begins at block 502, where input from a consumer is received to select a product formulation. In the illustrated embodiment, a consumer may utilize a client-type device, such as 214A-214C in FIG. 2, to obtain online access to a website, web page, or other online location that allows the consumer to select or determine a product party to dispense from the product dispenser. In another embodiment, the consumer may utilize a mobile phone, wireless communication device, or client device, such as 214A-214C in FIG. 2, or other communication device or method, to determine the party to the product to be dispensed from the product dispenser. In another embodiment, a consumer may utilize a product dispenser, such as 210 in FIG. 2, to access a user interface, website, web page, or other offline or online location that allows the consumer to determine the party to the product to dispense from the product dispenser. In any event, the consumer may select or determine a product formulation to be dispensed from the product dispenser.

In block 504 following block 502, a determination is made as to whether the consumer wants to save the product. If the determination is positive, that is, the consumer wants to save the product formulation, method 500 continues to 506. If the determination is negative, that is, the consumer does not want to save the product formulation, then the method 500 ends. In this embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether the consumer wants to store or otherwise save the product formulation. The consumer may provide input corresponding to a store or save command through a user interface associated with the product dispenser, such as user interface 112 in FIG. 1. In one embodiment, input corresponding to a store or save command may be received via a network from a client device, such as 214A-214C in FIG. 2, a mobile phone, wireless communication device, or other communication device, or a method associated with a consumer. In these cases, a processor, controller, local and/or remote server, or data processing resource, such as 126 in FIG. 1, may receive the store or save command.

Referring to block 506, the consumer is prompted to enter his or her consumer specified code (specficcode). In the illustrated embodiment, the consumer may be prompted to enter a consumer specified code using a user interface associated with the product dispenser, such as user interface 112 in FIG. 1. In response to a prompt from a user interface, e.g., 112, the consumer may enter a consumer specified code via the user interface, e.g., 112. In one embodiment, the consumer may transmit or otherwise enter the consumer specified code via a client type device, such as 214A-214C in fig. 2, a mobile phone, or a wireless communication device, or by way of other communication devices or methods as may be needed and/or desired in a particular embodiment.

In block 508, following block 506, the consumer's product recipe list is retrieved. In this embodiment, a processor or controller, e.g., 106 in FIG. 1, associated with the product dispenser, e.g., 102A, may retrieve the product recipe list in response to receiving the consumer specified code from the consumer. The product recipe list may include, but is not limited to, a list of one or more products associated with the code, a list of one or more products associated with the consumer, or a predetermined list of one or more products. In one example, a processor or controller, e.g., 106, associated with a product dispenser, e.g., 102A, can retrieve a previously stored product list from an associated memory or other data storage device, e.g., 110. In another example, a local and/or remote server or data processing resource, such as 126, can generate or otherwise retrieve a product listing from an associated memory or data storage device and provide the product recipe listing to a processor or controller, such as 106, associated with the product dispenser, such as 102A. In any case, a list of product recipes can be retrieved.

In decision block 510 following block 508, a determination is made as to whether the current product recipe or formulation is on the consumer product recipe list. If the determination is positive, that is, the current product formula or formulation is on the consumer's product formula list, then the method 500 ends. If the determination is negative, that is, the current product formulation is not on the consumer product formulation list, the method 500 continues to block 512. In the illustrated embodiment, a processor or controller, e.g., 106 in FIG. 1, associated with a product dispenser, e.g., 102, can compare a current product formulation to one or more product formulations in a predetermined list of product formulations associated with a consumer. In another embodiment, the local and/or remote server or data processing resource, e.g., 126, can compare the current product formulation to one or more product formulations in a predetermined product formulation list associated with the consumer. In both cases, based at least in part on the comparison, the processor, controller, local and/or remote server or data processing resource, e.g., 126, can determine whether the current product formulation is on the consumer's product recipe list.

At block 512, the current product formulation is added to the consumer's product formulation list. In this embodiment, a processor or controller, e.g., 106 in FIG. 1, associated with the product dispenser, e.g., 102A, can add or otherwise store the current product formulation recipe in the consumer's product recipe list and store the new list in an associated memory or other data storage device, e.g., 110. In another embodiment, a local and/or remote server or data processing resource, such as 126, adds or otherwise stores the current product formulation recipe in the consumer's product recipe list and stores the new list in an associated memory or data storage device, such as 110. In any case, the current product formulation is added to the consumer's product formulation list.

The method 500 ends after block 512.

Referring to fig. 6, an example of a method 600 of customizing a formulation of a product is shown. The method 600 begins at block 602. At block 602, input from a consumer is received to select a product formulation. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow a consumer to select a product formulation associated with the product. For example, after a consumer has an opportunity to select a recommended product that is determined for the consumer to try, the consumer may decide or otherwise select to try a different party associated with the product in place of the recommended product. The consumer may select different parties associated with the product through a user interface associated with the product dispenser, such as user interface 112.

In block 604 following block 602, the consumer is prompted as to whether to customize the product. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with a product dispenser, such as 102A, may generate or otherwise communicate a communication to the consumer prompting the consumer whether he or she wants to customize a product formulation associated with the product prior to dispensing. For example, a processor or controller, e.g., 106, may provide a message and related prompts to a consumer via an output device, e.g., a user interface, e.g., 112. In another embodiment, a local and/or remote server or data processing resource, such as 126, may generate a communication or other output, such as a message, and transmit the message to a product dispenser, such as 102A, for communication with a consumer. A processor or controller, e.g., 106, associated with the product dispenser, e.g., 102A, can receive the message for communication with the consumer. In any event, the consumer is prompted prior to dispensing whether he or she wants to customize the product formulation associated with the product.

In decision block 606 following block 604, a determination is made as to whether the consumer wants to customize the product. If the determination is positive, that is, the consumer wants to customize a product formulation, method 600 continues to block 608. If the determination is negative, that is, the consumer does not want to customize a product formulation, method 600 continues to block 610. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether the consumer wants to customize the product. For example, a processor or controller, such as 106, may receive a consumer input or selection via a user interface, such as 112, and determine whether the input or selection corresponds to whether the consumer wants to customize a product.

At block 608, input from the consumer is received to adjust the sweetener level, flavorings, carbonation level, and/or other formulation factors of the selected product. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may provide the consumer with the option to adjust one or more formulation factors associated with a selected formulation of the product. For example, the processor or controller, e.g., 106, may provide options for consumer input or selection through a user interface, e.g., 112, and determine whether the input or selection corresponds to whether to adjust one or more formulation factors associated with a selected product formulation. Formulation factors may include, but are not limited to, sweetener levels, flavorings, carbonation levels, and/or other formulation factors associated with the product or product formulation.

In block 610, following block 608, the customized product is distributed to the consumer. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to dispense the desired customized product.

The method 600 ends after block 610.

In one embodiment, the consumer may be prompted as to whether he or she wants to customize the product formulation. In this regard, the consumer may adjust the product sweetener level, flavorings, carbonation level, and/or adjust other formulation factors for the product he or she has selected.

Referring to FIG. 7, an example method 700 is shown that allows a consumer to make his or her own recipe. The method 700 begins at block 702. At block 702, input from a consumer is received to select a product. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to select a product. For example, the consumer may make his or her own recipe from a product menu or product ingredient list, which may be provided by a controller, such as 106, and the consumer may decide or otherwise choose to try out products from the product menu or product ingredient list from which the consumer may make his or her own recipe. The consumer may select a product or various product ingredients through a user interface associated with the product dispenser, such as user interface 112.

In decision block 704, following block 702, a determination is made as to whether the consumer chooses to make his or her own recipe. If the determination is positive, that is, the consumer chooses to make his or her own recipe, the method 700 continues to block 706. If the determination is negative, that is, the consumer does not choose to make his or her own formula, the method 700 continues to block 714. In this embodiment, a processor or controller associated with the product dispenser, such as controller 106 in FIG. 1, may receive or otherwise obtain information associated with the product selection. Based at least in part on the information associated with the product selection, the processor or controller, e.g., 106, the product dispenser, e.g., 102A, can determine whether the consumer chooses to make his or her own formula.

At block 706, the list of ingredients is displayed or otherwise output to the consumer on the product dispenser graphical user interface. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may provide a list of ingredients to a consumer. For example, after the consumer indicates that he or she wants to make his or her own recipe, the controller, e.g., 106, can provide a list of ingredients, e.g., product ingredients, from which the consumer can make his or her own recipe, via a user interface, e.g., user interface 112, associated with the product dispenser.

In block 708 following block 706, input from the consumer is received to select a component from the displayed list of components. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, may prompt the consumer to enter or otherwise select an ingredient from a displayed list of ingredients. For example, a consumer may provide a selected ingredient from a displayed list of ingredients using a user interface associated with the product dispenser, such as user interface 112.

In block 710, following block 708, input from the consumer is received to select the ingredient proportion, volume, and/or portion of each selected ingredient. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, may prompt the consumer to enter or otherwise select one or more formulation parameters from a displayed list of ingredients. For example, a consumer may provide for selection of one or more formulation parameters from a displayed list of ingredients using a user interface associated with the product dispenser, such as user interface 112. Formulation parameters may include, but are not limited to, ingredient ratio, volume, and/or portion of each selected ingredient.

In one embodiment, not only the choice of ingredients, but also the manner in which the ingredients are combined affects the final product formulation, quality and/or taste. In this regard, the amount of the ingredient may be selected by the consumer. To achieve the ability of the consumer to specify how the ingredients are to be combined, the consumer can select the ingredient mix ratio relative to water or other ingredients and/or the total volume of each ingredient to be added, and/or the portion of the final product that should include the particular ingredient.

In block 712, following block 710, input from the consumer is received to adjust sweetener levels, flavorings, carbonation levels, and/or to adjust other formulation factors. In the illustrated embodiment, the processor or controller, e.g., 106, of fig. 1 may prompt the consumer to enter or otherwise select one or more formulation factors from the displayed list of ingredients. For example, a consumer may utilize a user interface associated with the product dispenser, such as user interface 112, to provide for selection of one or more formulation factors from a displayed list of ingredients. Formulation factors may include, but are not limited to, sweetener levels, flavors, and carbonation levels.

In block 714, following block 712, the customized product is distributed to the consumer. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to dispense the desired customized product.

The method 700 ends after block 714.

In one embodiment, the consumer may be allowed to select a product from a menu of product choices or to make his or her own product formulation. In this regard, the consumer may make his or her own formulation of the product by selecting one or more ingredients from a list of ingredients and adjusting various formulation parameters or factors including, but not limited to, sweetener level, flavor, carbonation level, and/or adjusting other formulation parameters or factors.

Referring to FIG. 8, an example of a method 800 for allowing a consumer to manage a recipe list profile using a website is shown. The method 800 begins at block 802. At block 802, input from a consumer is received to log onto a food and drink network. In this embodiment, the consumer may log onto a network, such as network 104 in FIG. 1, through a client type device or a wireless communication device, such as 214A-214C in FIG. 2. In one embodiment, the network may be a food and drink network or a website where one or more consumers may retrieve, manage, and create recipe list profiles. An example of a suitable network may be myokerewards.

In block 804, following block 802, input from the consumer is received to retrieve his or her recipe list configuration file. In the illustrated embodiment, the local and/or remote servers of FIG. 1 associated with the product dispenser, e.g., 102A, may retrieve files associated with the consumer, e.g., recipe list configuration files. The file or recipe list configuration file may be stored in an associated memory or data storage device, such as 110. For example, a file or recipe list configuration file may be a file updated with a list of products associated with a particular consumer. Recipe list profiles may include, but are not limited to, standard products, brand name products, and custom products. The customized product may be created or otherwise formulated by the consumer. In one embodiment, a local and/or remote server or data processing resource, such as 126, may retrieve a file associated with the consumer, such as a recipe list configuration file. The controller, e.g., 106, can obtain a file or recipe list configuration file from a local and/or remote server or data processing resource, e.g., 126. In any event, the consumer is allowed to retrieve his or her recipe list profile.

In decision block 806, following block 804, a determination is made as to whether the consumer wants to manage his or her recipe list profile. If the determination is positive, that is, the consumer wants to manage their recipe list profile, the method 800 continues to block 808. If the determination is negative, that is, the consumer does not want to manage his or her recipe list profile, then the method 800 ends. In the illustrated embodiment, a local and/or remote server or data processing resource, such as 126 in FIG. 1, can determine whether the consumer wants to manage his or her recipe list profile. For example, the data processing resource, e.g., 126, can determine whether the consumer wants to manage his or her recipe list profile by comparing the consumer's input or selection via a user interface associated with a client type device or a wireless communication device, e.g., 214A-214C in fig. 2. The user interface may provide the consumer with one or more options of choice, including an indication to manage a recipe list profile. The data processing resource, e.g., 126, can determine whether the input or selection corresponds to an indication that the consumer wants to manage his or her recipe list profile.

In block 808, the customer's recipe list configuration file is output. In the illustrated embodiment, a local and/or remote server or data processing resource, such as 126 in FIG. 1, associated with the product dispenser, such as 102A, may facilitate outputting or otherwise displaying the consumer's recipe list profile through a user interface associated with any client-type or wireless communication device, such as 214A-214C. Recipe list profiles may include, but are not limited to, standard products, brand name products, and custom products. The customized product may be created or otherwise made by the consumer.

In block 810 following block 808, input from the consumer is received to select a recipe from his or her recipe list profile. In the illustrated embodiment, a local and/or remote server or data processing resource, such as 126 in FIG. 1, may provide the consumer with one or more options to select at least one recipe from the consumer's recipe list profile. For example, the data processing resources, e.g., 126, may provide the consumer with access through a user interface associated with a client type device or wireless communication device, e.g., 214A-214C. The user interface may provide the consumer with one or more options for selecting from, including options to add, delete, or edit recipes in the recipe list profile.

In block 812, following block 812, the total list of available ingredients is displayed to the consumer. In the illustrated embodiment, a local and/or remote server or data processing resource, such as 126 in FIG. 1, associated with the product dispenser, such as 102A, may facilitate outputting or otherwise displaying the list of available ingredients to the consumer via a user interface associated with any client-type or wireless communication device, such as 124A-214C. The general list of ingredients may include a list of some or all of the ingredients available from the product dispenser that may be combined to make one or more standard or customized products.

In block 814, following block 812, input from the consumer is received to modify the recipe of the consumer recipe list profile by adding and/or subtracting ingredients. In the illustrated embodiment, a local and/or remote server or data processing resource, such as 126 in FIG. 1, may provide the consumer with the option to modify at least one recipe from the consumer recipe list profile. For example, the data processing resources, e.g., 126, may provide the consumer with access through a user interface associated with a client type device or wireless communication device, e.g., 214A-214C. The user interface may provide the consumer with one or more options to modify at least one recipe, including, but not limited to, determining proportions, volumes, and/or portions of ingredients, and adjusting sweetener levels, flavorings, carbonation levels, and/or modifying other formulation factors to create a customized product formulation.

In block 816, following block 814, the recipe list configuration file is stored. In the illustrated embodiment, a local and/or remote server or data processing resource, such as 126 in FIG. 1, associated with the product dispenser, such as 102A, may store a recipe list profile associated with the consumer. For example, upon receiving a storage command from a consumer, the data processing resource, e.g., 126, can store the product list configuration file in an associated memory or data storage device, e.g., 110. The product list configuration file may be retrieved by the data processing resource, e.g., 126, at a later time. In another embodiment, the consumer's recipe list profile may also be stored in memory associated with the wireless data processing devices, e.g., 214A-214C, and/or other storage media used on the product dispensers, e.g., 102A. In any event, the consumer is allowed to save the recipe list profile.

The method 800 ends after block 816.

In one embodiment, the consumer may manage the recipe list profile using a website. In this regard, consumers may log in, retrieve, and manage their recipe list profiles. Such management of their recipe list profiles may include adding, modifying, and/or deleting custom products from the list. In operation, a consumer may make a product from a standard product menu list and/or create a product from scratch by mixing the individual ingredients in the ingredient list. Additionally, the consumer may modify the products in the formula list by adjusting sweetener levels, flavorings, carbonation levels, and/or adjusting other formulation factors.

Referring to FIG. 9, an example method 900 is shown that allows a consumer to select between a standard product menu and his or her recipe list profile. The method 900 begins at block 902. At block 902, a consumer is identified. In this embodiment, a product dispenser, such as 102A in fig. 1, may receive or otherwise obtain identification information associated with a consumer. Based at least in part on the identification information, a processor or controller, e.g., 106, associated with the product dispenser, e.g., 102A, can identify the consumer by identifying the reader/scanner device, e.g., 106A. Such consumer identification may be by RFID, badge, card, loyalty card, personal identification number, PIN, consumer wireless data processing device, and/or by other types and kinds of identification devices or methods as may be needed and/or desired in a particular embodiment.

In block 904, which follows block 902, the product dispenser retrieves the consumer's recipe list configuration file. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may transmit the identification data to a local and/or remote server or data processing resource, such as 126. Based at least in part on the identification data, the local and/or remote server or data processing resource, such as 126, can obtain or otherwise locate a recipe list profile associated with the consumer. In one embodiment, a processor or controller, e.g., 126, may access an associated memory or data storage device, e.g., 110, to retrieve or otherwise locate a recipe list profile associated with a consumer. The recipe list profile may include, but is not limited to, a historical list of some or all prior or past products that a particular consumer has requested, ordered, dispensed, or otherwise received from one or more product dispensers or other types of dispensers or equipment. In any case, the product dispenser may be in data communication with a server or data processing resource locally and/or remotely to obtain a recipe list profile for the consumer.

In block 906 following block 904, input from the consumer is received to select a standard product recipe from a product menu or a product from a recipe list profile customized by the consumer. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to select a standard product recipe from a product menu or a product from a recipe list profile customized by the consumer. For example, the product dispenser, e.g., 102A, may provide the consumer, via an associated user interface, e.g., 112, with one or more options to select a standard product formulation from a product menu or a product from a recipe list profile customized by the consumer. The consumer may select a product formulation or product through a user interface associated with the product dispenser, such as user interface 112.

In decision block 908 following block 906, a determination is made as to whether the consumer wants to modify the selected product party. If the determination is positive, that is, the consumer wants to modify the product formulation, the method 900 continues to block 912. If the determination is negative, that is, the consumer does not want to modify the product formulation, the method 900 continues to block 910. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether the consumer wants to modify the selected product formulation. For example, the processor or controller, e.g., 106, may prompt the consumer to receive consumer input or selection via the user interface, e.g., 112, and determine whether the consumer's subsequent input or selection corresponds to whether the consumer wants to modify the selected product.

At block 910, the customized product is distributed to the consumer. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to dispense the desired customized product.

The method 900 ends after block 910.

Referring to block 912, input from the consumer is received to modify the recipe of the selected product by increasing and/or decreasing ingredients. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to modify the recipe of the selected product by adding and/or subtracting ingredients. For example, a processor or controller, e.g., 106, may provide a prompt to a consumer via an output device, e.g., user interface, e.g., 112, to modify the recipe of a selected product by adding and/or subtracting ingredients. In this example, the consumer may modify one or more formulation parameters and factors, including but not limited to, determining ingredient ratios, volumes, and/or portions of ingredients, as well as adjusting sweetener levels, flavorings, carbonation levels, and/or modifying other formulation factors to create a customized product formulation. A processor or controller, e.g., 106, associated with the product dispenser, e.g., 102A, may receive any number of modifications from the consumer via a user interface, e.g., 112. In any case, the consumer is allowed to modify the formula of the selected product by adding and/or subtracting ingredients.

In block 914 following block 912, if the selected product is from the consumer's recipe list profile, the consumer is prompted whether to save the change. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether the selected product is from the consumer's recipe list profile and, if so, the consumer is prompted whether to save changes to the consumer's recipe list profile. For example, a processor or controller, e.g., 106, may receive a consumer input or selection via a user interface, e.g., 112, and determine whether the input or selection corresponds to saving a change to the consumer's recipe list profile.

In block 916, following block 914, a determination is made as to whether the consumer wants to save changes to his or her recipe list profile. If the determination is positive, that is, the consumer wants to save the changes to their recipe list profile, the method 900 continues to block 918. If the determination is negative, that is, the consumer does not want to save changes to his or her recipe list profile, the method 900 continues to block 910. In this embodiment, the processor or controller, e.g., 106, may determine whether the consumer wants to save changes to his or her recipe list profile by receiving consumer input or selection via a user interface, e.g., 112.

At block 918, changes to the consumer recipe list profile are saved and, as needed, data transferred to the data processing resource. In the illustrated embodiment, a processor or controller, e.g., 106 in FIG. 1, associated with a product dispenser, e.g., 102A, may update a recipe list profile associated with a consumer with any changes made by the consumer. For example, the recipe list configuration file may be updated and stored in an associated memory or data storage device, such as 110. In one embodiment, a local and/or remote server or data processing resource, such as 126, may update a recipe list configuration file associated with the consumer and store the configuration file in a memory or data storage device, such as 110. In any case, changes to the consumer recipe list configuration file are saved and, as needed, data transferred to the data processing resource.

Referring to block 910, the desired customized product is distributed to the consumer. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to dispense the desired customized product.

In one embodiment, the consumer may wish to be at, for example, COCA-COLA^TM，DIETCOCA-COLA^TM，FANTA ORANGE^TMAnd the selection between the standard product and his or her recipe list profile product. Thus, the product dispenser may retrieve the consumer's recipe list profile and then provide the consumer with a choice between a standard product menu product and his or her custom recipe list profile product.

Referring to fig. 10, an example method 1000 of charging a product based on a volume of product dispensed and paying for the product via a cashless payment implementation is shown. The method 1000 begins at block 1002. At block 1002, input from a consumer is received to select a product. In the illustrated embodiment, the consumer may enter data via a user interface, such as 112 in FIG. 1, for example, with a product, such as DIETCHERRY COKE^TMSelection of the corresponding indicator. In other embodiments, other products may be selected by the consumer, or other data associated with one or more product selections may be entered by the consumer. In one embodiment, product selection may be accomplished by way of a graphical user interface, such as user interface 112, associated with the product dispenser.

In a block 1004 following block 1002, a PRICE PER OUNCE (PRICE PEROUNCE) is determined and optionally displayed. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, may determine a price per ounce or other cost per unit for the selected product. For example, the controller, e.g., 106, may communicate with an associated memory or data storage device, e.g., 110, to determine the cost and size of the selected product. The controller, e.g., 106, may optionally display the price per ounce or other cost per unit of the selected product via a user interface, e.g., 112, associated with the product dispenser, e.g., 102A. In one embodiment, a processor or controller, e.g., 106, may communicate with a local and/or remote server or data processing resource, e.g., 126, to determine a price per ounce or other cost per unit of the selected product. In any case, a price per ounce is determined and optionally displayed.

At a block 1006, following block 1004, the consumer purchase is authorized by way of the machine readable item. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may facilitate and authorize payment from a cashless implementation (cash implementation), such as a machine readable item associated with a consumer. For example, a processor or controller such as 106 may receive payment information from a cashless implementation such as a machine readable item associated with a consumer. The payment information may include, but is not limited to, a credit or debit card or account number. In one embodiment, the consumer may be provided with an option to purchase the product via a client type device or a wireless communication device, such as 214A-214C in FIG. 2. In this particular embodiment, the consumer may pay for the selected product by authorizing payment via a client type device or wireless communication device, e.g., 214A-214C, and the payment may be received via an associated network, e.g., 104. In any event, the cashless implementation provided by the consumer is accepted and the product purchase is authorized.

In a decision block 1008 following block 1006, a determination is made as to whether payment authorization was successful. If the determination is positive, that is, the authorization attempt is 'Normal (OK)', the method 1200 continues to block 1210. If the determination is negative, that is, the authorization attempt is not 'normal', then the method 1200 continues to block 1224. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether the payment authorization was successful. For example, a processor or controller such as 106 may receive authorization messages from local and/or remote servers or data processing resources such as 126. The authorization message may include, but is not limited to, an authorization code, a transaction code, or a transaction 'normal' message.

At block 1010, the selected product is dispensed. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to dispense a desired product.

In block 1012, following block 1010, the volume of product dispensed is monitored. In the illustrated embodiment, a processor or controller, such as 106, may detect and determine a product VOLUME, such as a BEVERAGE VOLUME (BEVERAGE VOLUME) or other unit of measure, for a selected product. For example, a controller such as 106 may communicate with an associated flow meter or device to determine a product volume, such as a beverage volume or other unit of measure, of the selected product. In one embodiment, the product volume, e.g., BEVERAGE volume, may be used in a calculation formula, e.g., a FINAL BEVERAGE COST (FINAL BEVERAGE COST) calculation formula, to limit the amount of product dispensed from exceeding an authorized upper limit, and/or for other purposes as may be needed and/or desired in a particular embodiment.

In block 1014, following block 1012, a product price is calculated. In the illustrated embodiment, a processor or controller, such as 106, may determine a PRICE of the selected product, such as a CURRENT PRICE (CURRENT PRICE) or other PRICE. In one embodiment, the calculation may be based in part on a formula that includes the price per ounce (or other unit of volume) multiplied by the volume of beverage dispensed.

At decision block 1016, following block 1014, a determination is made as to whether the consumer has finished dispensing the selected product. If the determination is positive, that is, the consumer has finished dispensing the selected product, the method 1000 continues to block 1018. If the determination is negative, that is, the consumer has not finished dispensing the selected product, the method 1000 continues to block 1012. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine that the consumer has finished dispensing the selected product. For example, the processor or controller, e.g., 106, can detect when a predetermined amount of the selected product is dispensed or when the dispenser stops dispensing the selected product, and thus determine whether the consumer has dispensed the selected product.

At block 1018, the consumer is prompted for the completion of the product dispensing. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may notify the consumer that the product dispensing is complete. For example, after the consumer requests product filling and the consumer completes filling of the selected product, the controller, e.g., 106, may provide a communication, e.g., a message, that the product dispensing is complete through a user interface, e.g., user interface 112, associated with the product dispenser.

In block 1020, following block 1018, a final product price is optionally determined and displayed. In the illustrated embodiment, the processor or controller, e.g., 106, may determine a final product price, e.g., final beverage cost or other cost per unit, for the selected product. For example, a controller such as 106 in FIG. 1 may communicate with an associated memory or data storage device such as 110 to determine a final product price, such as a final beverage cost, for the selected product. The controller, e.g., 106, may optionally display a final product price for the selected product, e.g., a final beverage cost or other cost for the selected product, via a user interface, e.g., 112, associated with the product dispenser, e.g., 102A. In one embodiment, a processor or controller, such as 106, may communicate with a local and/or remote server or data processing resource, such as 126, to determine a final beverage cost or other cost for the selected product. In any case, the final beverage cost is optionally determined and displayed.

In block 1022 following block 1022, the consumer's machine readable item is charged. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may facilitate and authorize payment from a cashless implementation, such as a machine readable item associated with a consumer. For example, a processor or controller such as 106 may receive payment information for a final beverage fee from a cashless implementation such as a machine readable item associated with a consumer. The payment information may include, but is not limited to, a credit or debit card or account number. In one embodiment, the consumer may be provided with an option to purchase the product via a client type device or a wireless communication device, such as 214A-214C in FIG. 2. In this particular embodiment, the consumer may pay for the selected product by authorizing payment via a client type device or a wireless communication device, e.g., 214A-C, and the payment may be received via an associated network, e.g., 104. In one embodiment, charging the customer's cashless implementation may include, but is not limited to, charging the customer's credit card, hotel room, pre-paid account, and/or charging other types and/or kinds of accounts associated with the customer's cashless implementation as may be needed and/or desired in a particular embodiment. In any case, the cashless implementation of the consumer is charged.

Method 1000 ends after block 1022.

Referring to block 1024, the consumer is prompted that the authorization attempt failed. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may determine that the consumer cashless implementation authorization was unsuccessful or otherwise failed. For example, a processor or controller such as 106 may receive authorization messages from local and/or remote servers or data processing resources such as 126. The authorization message may include, but is not limited to, a failure code, a transaction code, an error message, an insufficient funds message, or a message that the transaction is not 'normal'.

Method 1000 ends after block 1024.

In one embodiment, the consumer may activate the product dispenser using a cashless implementation. Once activated, the product dispenser may determine the price per ounce of a particular product. The total beverage cost for a product may be calculated based on the volume of beverage dispensed in ounces multiplied by the price per ounce. In this regard, the cost of the product may be based on the volume dispensed rather than a fixed cost for a cup size such as a small, medium or large cup. Once the total beverage cost is determined, the cashless implementation for the consumer of the product is charged to effect payment. Cashless implementations may include, but are not limited to, machine readable items, cashless loyalty icons, prepaid cards, credit cards, hotel room keys, stored value accounts, wireless devices, and/or other types and/or kinds of cashless implementations as may be needed and/or desired in a particular implementation. In one embodiment, the price per ounce may alternatively be the price per milliliter or any other unit of measure as may be needed and/or desired in a particular embodiment. In addition, other pricing and cost calculation formulas may be used as necessary to generate a total beverage cost and/or a PRICE PER VOLUME (PRICE PER VOLUME) based on the VOLUME dispensed.

Referring to fig. 11, an example method 1100 of charging a product based on a volume of the product being dispensed and paying for the product by way of a pre-paid fee is shown. The method 1100 begins at block 1102. At block 1102, input from the consumer is received to prepay for the product to establish a maximum BEVERAGE COST (MAX BEVERAGE COST). In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may prompt the consumer to prepay for the product, which may establish a maximum beverage cost value. For example, a processor or controller such as 106 may prompt the consumer to prepay by any monetary or financial transaction device or method, such as receiving a credit or debit card or account number. The prepayment for the selected products may be by cashless or currency-based transaction. In one embodiment, the consumer may be provided the option to prepay for products and/or promotional offers via a client type device or a wireless communication device, such as 214A-214C in FIG. 2. In this particular embodiment, the consumer may prepay for the selected products by authorizing a payment via a client type device or wireless communication device, e.g., 214A-214C, and the payment may be received via an associated network, e.g., 104. In any event, the consumer is allowed to prepay for the product, establishing a maximum beverage fee.

In block 1104, following block 1102, input from the consumer is received to select a product. In the illustrated embodiment, the consumer may enter data through a user interface, such as 112 in FIG. 1, for example, with a product, such as DIET CHERRY COKE^TMSelection of the corresponding indicator. In other embodiments, other products may be selected by the consumer, or other data associated with one or more product selections may be entered by the consumer. In one embodiment, product selection may be accomplished by way of a graphical user interface, such as user interface 112, associated with the product dispenser.

In a block 1106 following the block 1104, the price per ounce is determined and optionally displayed. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, may determine a price per ounce or other cost per unit of the selected product. For example, the controller, e.g., 106, may communicate with an associated memory or data storage device, e.g., 110, to determine the cost and size of the selected product. The controller, e.g., 106, may optionally display the price per ounce or other cost per unit of the selected product via a user interface, e.g., 112, associated with the product dispenser, e.g., 102A. In one embodiment, a processor or controller, such as 106, may communicate with a local and/or remote server or data processing resource, such as 126, to determine a price per ounce or other cost per unit of the selected product. In any case, a price per ounce is determined and optionally displayed.

In block 1108, following block 1106, the selected product is dispensed. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to dispense a desired product.

At block 1110, following block 1108, the volume of product dispensed is monitored. In the illustrated embodiment, a processor or controller, such as 106, may monitor and determine the BEVERAGE VOLUME (BEVERAGE VOLUME) or other unit of measure of the selected product. For example, a controller such as 106 may communicate with an associated flow meter or device to determine the beverage volume or other unit of measure of the selected product. In one embodiment, the beverage volume may be used in a final beverage cost calculation formula, limiting the amount of product dispensed to not exceed an upper limit of a maximum beverage cost, and/or for other purposes as may be needed and/or desired in a particular embodiment. In one embodiment, the beverage volume may be used in a final beverage cost calculation formula, limiting the amount of product dispensed to not exceed an upper limit for maximum beverage cost, and/or for other purposes that may be needed and/or desired in a particular embodiment.

In block 1112, following block 1112, the current product price is calculated. In the illustrated embodiment, the processor or controller, e.g., 106, may determine the current beverage price or other price for the selected product. In one embodiment, the calculation may be based in part on a formula that includes the price per ounce (or other unit of volume) multiplied by the volume of beverage dispensed.

In decision block 1114, following block 1112, a determination is made as to whether the consumer has reached a maximum beverage cost. If the determination is positive, that is, the consumer has reached a maximum beverage cost, the method 1100 continues to block 1120. If the determination is negative, that is, the consumer has not reached the maximum beverage cost, the method 1100 continues to decision block 1116. In the illustrated embodiment, the processor or controller, e.g., 106, can determine whether the maximum beverage cost or other cost per unit of the selected product is met or exceeded. For example, the controller, e.g., 106, may communicate with an associated memory or data storage device, e.g., 110, to compare the maximum beverage cost for the selected product to the current price of the beverage.

At decision block 1116, a determination is made as to whether the consumer has finished dispensing the selected product. If the determination is positive, that is, the consumer has finished dispensing the selected product, the method 1100 continues to block 1118. If the determination is negative, that is, the consumer has not finished dispensing the selected product, the method 1100 continues to block 1110. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether the consumer has finished dispensing the selected product. For example, the processor or controller, e.g., 106, can detect when a predetermined amount of the selected product has been dispensed, or when the dispenser stops dispensing the selected product, and thus determine whether the consumer has finished dispensing the selected product.

At block 1118, the consumer may obtain a refund if the maximum beverage cost is greater than the calculated cost of the final beverage cost. In the illustrated embodiment, the processor or controller, e.g., 106, can determine whether the maximum beverage cost is greater than the calculated cost of the final beverage cost, and if so, a refund can be provided to the consumer.

Following block 1118, at block 1120, the consumer is prompted for the completion of the product dispensing. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may notify the consumer that the product dispensing is complete. For example, after the consumer requests product filling and the consumer completes filling of the selected product, the controller, e.g., 106, may provide a communication, e.g., a message, that the product dispensing is complete through a user interface, e.g., user interface 112, associated with the product dispenser.

In block 1122, following block 1120, the final product price is optionally determined and displayed. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, may determine the final beverage cost or other cost per unit of the selected product. For example, the controller, e.g., 106, may communicate with an associated memory or data storage device, e.g., 110, to determine the final beverage cost for the selected product. The controller, e.g., 106, may optionally display the final beverage cost or other cost for the selected product via a user interface, e.g., 112, associated with the product dispenser, e.g., 102A. In one embodiment, a processor or controller, such as 106, may communicate with a local and/or remote server or data processing resource, such as 126, to determine a final beverage cost or other cost for the selected product. In any case, the final beverage cost is optionally determined and displayed.

Method 1100 ends after block 1122.

In one embodiment, the consumer may prepay for the product. For this, a maximum beverage cost equal to the prepaid fee may be determined. The consumer may then operate the product dispenser to dispense the product at a price per ounce pattern. In such a mode, the consumer may dispense a total beverage volume that defines, in part, a total beverage cost near a maximum beverage cost, where the total beverage cost is the total beverage volume multiplied by the price per ounce.

In one embodiment, the total volume of beverage dispensed is limited by the formula and price per ounce to a prepaid maximum beverage cost usage. Alternatively, if the consumer does not dispense a sufficient volume of product such that the maximum beverage cost cannot be reached, a partial refund may be calculated and returned to the consumer.

The capabilities of various embodiments of the present invention can be implemented in software, firmware, hardware or some combination thereof.

As one example, one or more aspects of the present invention can be included in an article of manufacture (e.g., one or more computer program products) having, for instance, computer usable media. The media has embodied therein, for instance, computer readable program code for providing and facilitating the capabilities of embodiments of the present invention. The article of manufacture may be included as a part of a computer system or sold separately. One example of a suitable article of manufacture is a consumer interaction engine or module, such as 114 depicted in FIG. 1.

Additionally, at least one program storage device readable by a machine, tangibly embodying at least one program or set of instructions executable by the machine to perform the capabilities of embodiments of the present invention can be provided. One example of a suitable program storage device readable by a machine is a memory or data storage device such as 110 depicted in FIG. 1.

The flow diagrams depicted herein are examples. There may be many variations to these diagrams or the elements (or operations) described therein without departing from the scope of the invention as claimed. For example, elements may be implemented in a different order, or elements may be added, deleted or modified. All of these variations are considered a part of the claimed invention.

While embodiments of the invention have been described, it will be understood that those skilled in the art, both now and in the future, may make various improvements and enhancements which fall within the scope of the claims which follow. These claims should be construed to maintain the proper protection for the invention first described.

Claims (25)

1. A product dispenser (102) comprising:

a user interface (112) operable to interact with a consumer and receive at least one input from the consumer; and

a controller (106) comprising a set of instructions operable to:

receiving a request from a consumer to dispense a customized product;

presenting, through the user interface (112), at least one of a list of selectable product ingredients or adjustable product formulation parameters; and

dispensing a product based at least in part on one or more of the selectable ingredients or the selected formulation parameters.

2. The dispenser (102) of claim 1, wherein the request from the consumer to dispense a customized product comprises at least one of: information received through a user interface associated with the product dispenser, a scanned machine code, information received from an RFID tag, communication information received from a client-type device, or communication information received from a wireless communication device.

3. The dispenser (102) of claim 1, wherein the controller (106) further comprises a set of instructions operable to:

receiving information associated with the consumer, wherein the information comprises previously stored optional product ingredients or adjustable product formulation parameters.

4. The dispenser (102) of claim 1, wherein the adjustable product formulation parameters comprise at least one of: volume, proportion, portion, carbonation level, sweetener, flavor pellet, or nutritional supplement.

5. The dispenser (102) of claim 1, wherein the controller (106) further comprises a set of instructions operable to:

one or more optional product ingredients or product formulation parameters entered by the consumer are stored.

6. The dispenser (102) of claim 1, wherein the information associated with the consumer comprises a code received from the consumer, and the set of instructions is further operable to:

retrieving a profile associated with the consumer.

7. The dispenser (102) of claim 3, wherein the information associated with the consumer further comprises identification information associated with the consumer, and the controller further comprises a set of instructions operable to:

a user profile associated with the consumer is retrieved.

8. The dispenser (102) of claim 1, wherein the controller (106) further comprises a set of instructions operable to:

storing the recipe associated with the dispensed product in a profile associated with the consumer.

9. The dispenser (102) of claim 1, wherein the controller (106) further comprises a set of instructions operable to:

providing a consumer, over a network, access to a profile associated with the consumer; and

receiving one or more selectable product ingredients or product formulation parameters from the consumer over a network.

10. A method for operating a product dispenser (102), comprising:

receiving a request from a consumer to dispense a customized product;

presenting at least one of a list of selectable product ingredients or adjustable product formulation parameters based at least in part on information associated with the consumer;

receiving input regarding at least one of selectable product ingredients or product formulation parameters; and

dispensing a product based at least in part on one or more of the selectable product ingredients or product formulation parameters.

11. The method of claim 10, wherein receiving a request from a consumer to dispense a customized product comprises at least one of: receiving information through a user interface associated with the product dispenser, scanning a machine code, receiving information from an RFID tag, receiving communication from a client-type device, or receiving communication from a wireless communication device.

12. The method of claim 10, further comprising:

receiving information associated with the consumer, wherein the information comprises previously stored optional product ingredients or adjustable product formulation parameters.

13. The method of claim 10, wherein the adjustable product formulation parameters comprise at least one of: volume, proportion, portion, carbonation level, sweetener, flavor pellet, or nutritional supplement.

14. The method of claim 10, further comprising:

one or more optional product ingredients or product formulation parameters entered by the consumer are stored.

15. The method of claim 12, wherein the step of receiving information associated with the consumer further comprises receiving a code from the consumer and retrieving a profile associated with the consumer.

16. The method of claim 12, wherein receiving information associated with the consumer further comprises receiving identification information associated with the consumer and retrieving a user profile associated with the consumer.

17. The method of claim 10, further comprising:

storing the recipe associated with the dispensed product in a profile associated with the consumer.

18. The method of claim 10, further comprising:

providing a consumer, over a network, access to a profile associated with the consumer; and

input from the consumer is received for one or more selectable product ingredients or product formulation parameters.

19. A method for operating a product dispenser (102), comprising:

receiving information associated with the consumer;

presenting, via a user interface (112) associated with the product dispenser (102), at least one product recipe comprising at least one selectable product ingredient or adjustable product formulation parameter based at least in part on the information associated with the consumer;

receiving consumer input regarding at least one of selectable product ingredients or product formulation parameters; and

dispensing the product based at least in part on the selected one or more of the product ingredients or product formulation parameters.

20. The method of claim 19, wherein receiving information associated with the consumer comprises at least one of: accessing a profile associated with the consumer, receiving consumer information from a remote server or data storage device, receiving information through a user interface associated with the product dispenser, scanning machine codes, receiving information from an RFID tag, receiving communication information from a client-type device, or receiving communication information from a wireless communication device.

21. The method of claim 19, wherein the adjustable product formulation parameters comprise at least one of: volume, proportion, portion, carbonation level, sweetener, flavor pellet, or nutritional supplement.

22. The method of claim 19, further comprising:

providing a consumer, over a network, access to a profile associated with the consumer, wherein the profile comprises one or more selectable product ingredients or product formulation parameters selected by the consumer; and

storing any changes to the configuration file.

23. A product dispenser (102) comprising:

a user interface (112) operable to interact with a consumer and receive at least one input from the consumer; and

a controller (106) comprising a set of instructions operable to:

receiving information associated with the consumer;

presenting, via the user interface associated with the product ingredient, at least one product recipe comprising at least one selectable product ingredient or adjustable product formulation parameter based at least in part on the information associated with the consumer;

receiving consumer input regarding at least one of selectable product ingredients or product formulation parameters; and

dispensing the product based at least in part on the selected one or more of the product ingredients or product formulation parameters.

24. The dispenser (102) of claim 23, wherein the controller further comprises a set of instructions operable to:

receiving information from a profile associated with the consumer over a network, wherein the profile comprises one or more selectable product ingredients or product formulation parameters previously selected by the consumer.

25. A system (100) comprising:

a communication network (104);

a plurality of product dispensers (102) in communication with the network, wherein each product dispenser comprises:

a user interface (112) operable to interact with a consumer and receive at least one input from the consumer; and

a controller (106) comprising a set of instructions operable to:

receiving information associated with the consumer over a network;

presenting, via the user interface (112) associated with the product dispenser (102), at least one product recipe comprising at least one selectable product ingredient or adjustable product formulation parameter based at least in part on the information associated with the consumer;

receiving consumer input regarding at least one of selectable product ingredients or product formulation parameters; and

dispensing the product based at least in part on one or more of the selected product ingredients or product formulation parameters.