1. Technical Field
The present disclosure generally relates to methods and systems of preparing beverages, and more particularly relates to methods and systems of analyzing ingredients and preparing beverages that meet certain criteria.
2. Background
Currently, most beverages are mass-produced for the general population. Many of the pre-packaged beverages are made using either artificial ingredients such as sugar and additives, or concentrates or a combination of the two. As a result, the public's choice of beverages has been limited to what was manufactured and not necessarily what is most desired or beneficial from an individual's stand point. Such mass-produced artificially enhanced beverages are not generally the beverage of choice for many individuals, particularly those who are health conscience, and/or those with a restricted diet or other specific requirements and/or goals.
Beverage manufacturers, on the other hand, typically do not produce products to meet individual requests. The divide between what is being produced by the manufacturers and what is desired by an individual may be bridged by producing customized beverages for the individuals.
A beverage distributor or seller, generally interacting with both the beverage manufacturers and the individuals, wish to generate more sales. For example, a seller who also owns a gym may benefit from introducing a beverage particularly designed for his gym clients. The beverage sellers, like the individuals, do not have the means to manufacture such beverages targeted for certain individuals. The beverage sellers may also profit from customized beverages.
As overall health consciousness throughout the world has increased, the population has an increasing desire to improve health and monitor food intake. For example, general health-consciousness and orientation to low-sugar and/or high-fiber diet are making consumers avoid artificial sugar which can cause obesity and decayed teeth, especially in the area of beverages. A general trend in beverages may be going toward using ingredients that are minimally processed, natural, and/or seasonal. Such beverages may contain be more beneficial as they may contain higher levels of fiber, vitamins, antioxidants and other components. Artificial beverages, generally required to have an extended shelf-life, have the additional shortcoming of not satisfying the consumer desire for more healthful and more natural beverages.
Because artificial beverages cannot sufficiently meet various needs and requirements of the population, there is a need for methods and systems of preparing beverages for a health conscience population.
This specification includes references to “one embodiment” or “an embodiment.” The appearances of the phrases “in one embodiment” or “in an embodiment” do not necessarily refer to the same embodiment. Particular features, structures, or characteristics may be combined in any suitable manner consistent with this disclosure.
This specification may use phrase such as “based on.” As used herein, this term is used to describe one or more factors that affect a determination. This term does not foreclose additional factors that may affect a determination. That is, a determination may be solely based on those factors or based only in part on those factors. Consider the phrase “determine A based on B.” This phrase connotes that B is a factor that affects the determination of A, but does not foreclose the determination of A from also being based on C. In other instances, A may be determined based solely on B.
A user may benefit from a beverage prepared with a target to meet certain specific requirements of the user. While a user's specific requirements may vary from one user to the next, each individual ingredient used to prepare the beverage may also vary from one to another. When the variations in individual ingredients are taken into account, the resulting beverage may closely comply with the specific requirements of the user.
In some embodiments, user 100 provides data such as personal data including gender, age, fitness and/or exercise level, types of allergy, weight, body mass index, insulin level, symptoms such as insomnia, and laboratory test data such as red blood cell count and others. In one embodiment, system 200 selects, from database 202, a recipe for the beverage. For example, a recipe with low or zero caffeine may be selected based on the insomnia of user 100. As another example, a recipe with low sugar content may be selected based on the insulin level of a diabetic user 100. As used herein, the word “content” and the word “level” is each used to describe a characteristic including, but not limited to, a numerical value, a concentration, a level, a range, a limit, a standard, a threshold, a percentage, a comparative value, a quantified or an unquantified amount, value, volume or others.
In the embodiment of diabetic user 100, a low-sugar beverage recipe may include apple juice 310 along with other ingredients generally illustrated as ingredients 300. Apple juice 310 may be freshly squeezed from organic apples. As a further embodiment, apple juice 310 may be freshly squeezed from organic apples including “Red Delicious” apples and other varieties. Depending on the apples (i.e., different varieties, different seasons of the year, different farmers, etc.) used to produce apple juice 310, however, the sugar content of apple juice 310 may vary. System 300 analyzes ingredients 300 such as apple juice 310 to determine various properties of apple juice 310.
The various properties of ingredients 300 (including apple juice 310) may include chemical properties such as pH level, pathogen content, bacteria content, acidity level, alkalinity level, water content, mold content, yeast content, allergen content, saturated fat content, unsaturated fat content, trans-fatty acid content, amino-acid content, sodium content, preservative content, mineral content, electrolytes content, fiber content, antioxidant count, and others.
Properties of ingredients 300 may also include physical properties such as temperature, pressure, viscosity, density, color, solubility, fluidity, refractive index, and others. System 200 may analyze one, some or all ingredients 300 (1-n). Ingredients may include vegetables, fruits, juices, purees, soups, oils, nuts, legumes, grains, spices, dairy items, vitamins, herbs, starches, and other items.
These properties define certain aspects or characteristics of an ingredient. The measurement, analysis, or determination of these properties include, but are not limited to, a numerical value, a range, a concentration, a limit, a standard, a threshold, a percentage, a comparative value, a quantified, or an unquantified amount, volume, value or others. For example, a pathogen count of an ingredient may be analyzed based on a threshold criterion such as a maximum acceptable pathogen count. The criterion may be predetermined, adjusted based on a predetermined criterion, or otherwise. As another example, a user with peanut allergy likely requires a beverage with a low or zero peanut (allergen) count, while users without peanut allergy may not have such requirement. And therefore, for users without peanut allergy, a threshold of peanut count may be increased for a particular beverage.
In certain embodiments, system 200 may extract a sample of one of ingredients 300 for testing or analyzing. The amount of the sample and the type of testing may vary. For example, without limitation, relevant tests and/or analyses may determine various properties include one or more of the following:
When system 200 determines a set of ingredients and amounts of ingredients for the beverage, the completed beverage 250 can be prepared using these ingredients and made available to user 100. Additional details regarding preparing the beverage will be discussed in later sections. User 100 may receive beverage 250 from a retail location 105B (which may or may not be the same as retail counter 102E), a vending machine 105C, or via shipment 105A, or other methods or means.
Turning to
Upon receiving data from user 100, system 200 may select a stored beverage recipe from recipe database 202.
For user 100 who may have a goal to lose weight, system 200 may select a stored recipe with low calorie content. User 100 may additionally have a vigorous exercise goal and may benefit from a high protein beverage. In this particular embodiment, system 200 may initially select a stored recipe which includes milk as an ingredient, for milk generally has high protein content. System 200 may, however, adjust the recipe, taking into account the goal to lose weight and other factors. Analyzing engine 208 may analyze and determine various properties of ingredients. For example, analyzing engine 208 may analyze a fat content of whole milk. In one embodiment, analyzing engine 208 may compare fat content of the whole milk to a threshold, a standard, or other similar types of boundary conditions.
Depending on the fat content and other properties of whole milk, system 200 may select skim milk instead of whole milk to reduce the overall calorie of the beverage. In other cases, system 200 may reduce the amount of whole milk used for the beverage, and/or add another ingredient (such as soy milk) that was not in the originally selected recipe. Supply database 212 may provide data relevant to the availability of ingredients and/or vendors from whom ingredients may be obtained.
In one embodiment, system 200 may use a reduced amount of whole milk and add to the originally selected recipe a certain amount of soy milk to meet the caloric and protein requirements of the beverage. If supply database 212 determines that an ingredient such as soy milk is not immediately available, system 200 which includes supply database 212 may determine if the ingredient may become available through other vendors or other channels.
In yet another embodiment, system 200 may have available soybeans instead of soy milk, and system 200 may make the soy milk from the soy beans. In this case, the originally selected recipe would additionally include a set instructions and relevant amounts of ingredients for the soy milk as an added ingredient for the beverage. System 200 which may include constraint engine 218 may additionally adjust the originally selected recipe, for example, by adjusting the length of time the ingredients are emulsified to account for the use of a new ingredient, in this case, soy milk instead of milk.
Moreover, user 100 may provide data such as preferences of a beverage. For example, user 100 may prefer a certain flavor, a texture, a shelf-life, an aesthetic component, and/or other characters of a beverage. For example, user 100 may prefer a beverage flavor that is sweet, bitter, sour, salty, savory, pungent, metallic, spicy, hot, warm, cold, icy, citrus, mild, chocolaty, vanilla, fruity, floral, umami, tangy, earthy, smoky, berry, or others. Flavor may include various levels, for example, a diagram of a pepper of a beverage may indicate that the beverage is spicy; whereas a diagram of three peppers may indicate that the beverage is spicier than the one with the one pepper diagram. As used herein, the word “flavor” includes taste and/or smell, objective and/or subjective perceptions, and/or sensations, whether quantifiable or not. Moreover, the word “flavor” is not limited to trigeminal senses but may include other senses.
Similarly, a beverage texture may be creamy, crisp, chunky, or other objective or subjective perceptions or characters. A shelf-life may be specified, for example, by an expiration date of the beverage. An aesthetic component may include a general appearance of the beverage. An aesthetic component may include both objective and subjective preferences, perception, feelings, and/or sensations. An aesthetic component is not limited to visual and may include other sensory components. Other embodiments may include a default set of flavor, texture, an aesthetic component, and/or shelf-life for a beverage. Similar to “one/three pepper diagram” discussed in relation to flavor above, any or all of user preferences may include, or be characterized by, various levels, ratings, scales, or others.
Moreover, if user 100 subsequently chooses to order the same beverage, instead of providing various data again, user 100 may instead provide data of the previously prepared beverage. Based on the data of the previous beverage, system 200 may prepare another similar beverage for user 100. In some embodiments, the data includes a bar code, a Quick Response Code (“QR Code”), other machine-readable codes, or other types of representation. Yet in other embodiments, the modified recipe (with the added soy milk, for example) may be stored along with a profile for user 100 by system 200 which may include user database 216.
System 200 may create, store and maintain a profile (not separately shown) for user 100. The profile may include personal data of user 100 such as age and gender. The profile may include various goals of user 100 such as weight loss goals. The profile may be used to track and/or trend various goals such as a progress of weight loss over a period of time. The profile may include historical data such as weight, body mass index, and other data over time. In some embodiments, user 100 may create, enter, access, delete, and/or edit the profile. In some embodiments, the profile may include particular recipes, either from a previously prepared beverage or otherwise. In yet other embodiments, meal database 214 in system 200 may store meal recipes including beverage recipes of user 100.
Turning now to
In
Assembly line 500 may include nitrogen flushing system 560 which may be used to remove oxygen from bins 512. Moreover, when bin 512 is empty, it may be flushed with nitrogen to minimize the risk of oxidation or contamination. Chiller 570 may be included to maintain a threshold temperature of ingredients 300 (not separately shown) in order to reduce bacteria growth and control temperature. As discussed earlier, finished products may be received by user 100 in a variety of ways.
At block 410, system 200 receives input data from user 100. The input data may include data such as a body mass index, health goals such as a goal to lose weight, beverage preferences such as a flavor of the beverage, and data related to previously prepared beverages. Flow proceeds to block 420.
At block 420, system 200 selects an initial beverage recipe for user 100. The selecting may take into account input data discussed in block 410. A beverage recipe may include a list of ingredient, amount of each ingredient, and instructions including time parameter to prepare the beverage. Flow proceeds to block 430.
At block 430, system 200 analyzes an ingredient for certain properties of the ingredient. As discussed earlier, the analysis may show that the ingredient (e.g., apple juice) has a certain sugar content or other properties. Flow proceeds to block 440.
At block 440, system 200 modifies the initial recipe by taking into account the analysis in block 430. Depending on the analysis, system 200 may add, subtract, and/or replace one or more ingredients in the initial recipe. System 200 may increase or reduce an amount of an ingredient in the initial recipe. System 200 may change the instructions in the initial recipe. For example, the initial receipt may instruct that an ingredient in the recipe should be steamed for a certain length of time. In modifying the initial recipe, system 200 may lengthen or shortened the length of steaming time, or replace it with a different instruction. Flow proceeds to block 450.
At block 450, system 200 finalizes the ingredients, the amounts of ingredients, and instructions to prepare the beverage. In some embodiments, this set of data may constitute a final recipe of the beverage. At least a portion of the final recipe may be represented by a machine-readable code such as a QR code. Relevant equipment in system 200 may scan the machine-readable code and atomically prepare the beverage. In other embodiments, the final recipe may be a set of detailed instructions for a human operator to prepare the beverage. Flow proceeds to block 460.
At block 460, beverage is prepared for user 100, and process 400 ends at block 460.
Although specific embodiments have been described above, these embodiments are not intended to limit the scope of the present disclosure, even where only a single embodiment is described with respect to a particular feature. Examples of features provided in the disclosure are intended to be illustrative rather than restrictive unless stated otherwise. The above description is intended to cover such alternatives, modifications, and equivalents as would be apparent to a person skilled in the art having the benefit of this disclosure.
The scope of the present disclosure includes any feature or combination of features disclosed herein (either explicitly or implicitly), or any generalization thereof, whether or not it mitigates any or all of the problems addressed herein. Accordingly, new claims may be formulated during prosecution of this application (or an application claiming priority thereto) to any such combination of features. In particular, with reference to the appended claims, features from dependent claims may be combined with those of the independent claims and features from respective independent claims may be combined in any appropriate manner and not merely in the specific combinations enumerated in the appended claims.
This application is a continuation of U.S. application Ser. No. 14/020,836, filed Sep. 7, 2013, which claims the benefit of, and priority of U.S. Provisional Appl. No. 61/698,354, filed Sep. 7, 2012; the disclosures of each of the above-referenced applications are incorporated by reference herein in their entireties.
Number | Date | Country | |
---|---|---|---|
61698354 | Sep 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14020836 | Sep 2013 | US |
Child | 14033065 | US |