The present invention relates to weight scales. More particularly, the present invention relates to interactive systems of weight scales and computing devices.
Recipes are commonly used to create culinary combinations of food or drink. As used herein, culinary combinations will include creations of mixology and of cooking. The foundations of all recipes are culinary ratios. A culinary ratio is a fixed proportion of one or more ingredients of a recipe relative to another. These ratios are fundamental to the crafts of cooking and mixology. Understanding that recipes are ratios allow one to consistently scale or adjust recipes and to fix a recipe if one makes a mistake and adds too much of a certain ingredient.
When preparing food or drinks, it is best to use weight rather than volume for measuring most ingredients. Properties of a culinary combination are more closely dependent on the ratio of the weights or masses of ingredients, than on their volumes. For a culinary combination to have the desired properties, the ratios of the masses or weights of the ingredients must be achieved. Volumetric measurements may be convenient approximations for weight, but it the weight or mass of the ingredients that is desired. Measuring by volume can introduce inaccuracies. The volume of a certain mass of a material can change based on environmental conditions such as temperature, pressure and humidity. Because of this, powder ingredients like flour are in particular more accurately measured by weight than by volume. The volumetric measurement of liquids has other sources of inaccuracy. The shape of the target container, the viewing angle of the user, and the surface tension of the liquid can easily cause a 20% variation when visually judging what is “full” for small amounts of liquid. Weighing ingredients is the most reliable and consistent form of measuring, and it is the preferred method when it comes to using culinary ratios.
The standard digital scale can measure in metric or imperial units (also referred to as the U.S. customary units or avoirdupois units). A scale measuring a liquid detects weight, but some are configured to report the amount detected in volume units such as milliliters or fluid ounces (defined as 1/16 of a pint or 1/128 of a gallon in the US customary units system). However, this assumes the liquid is water or has a similar volume/weight ratio (density) as water. Some liquids have densities that are different from water, which can throw off the accuracy of using a scale to determine volume. For example, one milliliter is one gram of water and 30 grams of water is approximately 1 fluid ounce. The specific gravity of water is 1.00 (specific gravity is the ratio of density of fluid in question to the density of water). The specific gravity of simple syrup is typically 1.33. If a recipe calls for a 1 fluid ounce of simple syrup, weighing out one ounce of simple syrup will be rather inaccurate unless the scale knows the specific gravity of the fluid it is weighing and calculates fluid ounces accordingly.
Using a scale to maintain ratios can be especially challenging for standard cocktail recipes, which typically specify volume measurements. As an example a classic margarita recipe calls for the following ingredients:
The specific gravity for each ingredient is approximately:
To measure a correct ratio by weight, the specific gravity of each ingredient must be considered. A scale assuming the specific gravity of water to measure ingredients would yield:
This would result in significantly different ratios of ingredients than the original recipe and would not taste the same. A correct measurement incorporating the specific gravity of each ingredient would measure the following:
The standard digital kitchen scale typically has a “tare” button. This is used to subtract the current weight on the smart scale 102, setting the current measured weight to zero. Using this button allows the weight of a containing vessel (like a bowl or glass) to be eliminated when measuring an ingredient. Using this button sequentially to build a multi-step recipe allows each ingredient to be measured independently as it is added.
This is a useful system and minimizes the use of containers. However, it does not have any awareness of the ingredients being measured or specific actions of the recipe. What if you make a mistake reading a recipe? Let's say a recipe asks for 70 grams of grape juice and 100 grams of apple juice and the user puts them in backwards (70 grams of apple juice and 100 grams of grape juice). It can be difficult to fix this, especially in the context of the entire recipe, where the measured amount for each ingredient must now be precisely altered to maintain a proper ratio.
Another problem is scaling a recipe. Simple scaling is practicable in one's head when doubling (2×) or halving (½) the recipe. However, other scaling changes, like making 30% less, or 1.75 times more, become more complicated. The common digital kitchen scale offers no assistance here.
The present invention will be described by way of exemplary embodiments, but not limitations, illustrated in the accompanying drawings in which like references denote similar elements, and in which:
The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more embodiments of the invention and, together with the detailed description, serve to explain the principles and implementations of the invention.
Before beginning a detailed description of the subject invention, mention of the following is in order. When appropriate, like reference materials and characters are used to designate identical, corresponding, or similar components in different figures. The figures associated with this disclosure typically are not drawn with dimensional accuracy to scale, i.e., such drawings have been drafted with a focus on clarity of viewing and understanding rather than dimensional accuracy.
In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application and business related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.
Use of directional terms such as “upper,” “lower,” “above,” “below”, “in front of,” “behind,” etc. are intended to describe the positions and/or orientations of various components of the invention relative to one another as shown in the various Figures and are not intended to impose limitations on any position and/or orientation of any embodiment of the invention relative to any reference point external to the reference.
The culinary ratio system 100 represents a significant advance in technology assisted cooking and mixology. As shown in the embodiments of
The culinary ratio system 100 has a software app on the smart device 104 which is configured to receive real-time information from the smart scale 102. The app has access to information regarding actions, ingredients, and target amounts involved in a recipe. The app presents a user with actions to be performed and ingredients to be added.
The app is configured to assist the user in maintaining the culinary ratios of a recipe. The app is configured to accept input so that a user can change the overall serving size for the recipe at any time and the target amounts of each ingredient are automatically re-calculated and displayed. If too much of one ingredient is added, the app detects this and helps the user maintain the proper ratios. The number of servings is recalculated and displayed along with new target amounts for all other ingredients.
The culinary ratio system 100 has one or more graphical displays to show the real-time amount for any ingredient being added and may also show which ingredients have been added, which are left to be added, which actions have been performed, and which have still to be performed. In the preferred embodiment, there is a scale display 108 that is part of the smart scale 102 and a smart device display 109 that is part of the smart device 104. Both may be used for displaying information about recipe ingredients. Other embodiments may use only one of these displays.
In the preferred embodiment, the smart scale 102 has a button pad 110 (see
The scale display 108 (see
The smart scale 102 may have lights and audio that can be used to help inform the user when pouring/adding an ingredient. This may be easier for some users when pouring—it allows them to look at the smart scale 102 instead of a smart device display 109. For example, the color of an LED can slowly change from green to red as an ingredient is added and approaches its target amount. Audio prompts from the smart device can be played though the smart scale 102 to call out ingredients and progress. Timers can also be started for actions requiring timing. These timers can be displayed on either the smart device 104 or the smart scale 102. An optional microphone in the smart scale 102 or the smart device 104 can be used for voice prompts/commands like “Next”, “Start Timer”, etc.
Real-time scale data. Since there is a way for the smart device 104 to receive real-time data from the smart scale 102 in this configuration, the app on the smart device 104 performs all the necessary tare operations and unit calculations. The scale display 108 may simply show a “connected” message or its own independent weight information.
Button events (
Container presence. The presence of a container can be detected by the smart scale 102 either by weight or by means of a sensor and this information sent to the smart device 104.
Scale Display (
Measurement/Unit Synchronization. Because the smart device 104 can send commands to the smart scale 102, either the smart scale 102 or the smart device 104 can perform actions like “tare”. These actions can be synchronized with the recipe. Units and measurements can be synchronized in real-time.
Audio. In some embodiments, the smart scale 102 has a speaker (not shown) for playing audio prompts and instructions. These commands may be generated by and played from the app. The audio connection between the smart scale 102 and the smart device 104 may be digital or analog.
LEDs. In some embodiments, the smart scale 102 has LEDs (not shown). The LEDs on the smart scale 102 can be controlled by the app for real-time feedback. This control can be any combination of the following: Blinking/Pulsing; Brightness; Color; and individual LED controlled separately.
Container presence. The presence of a container can be detected by the smart scale 102 either sensing the weight of the container or by using a different type of sensor. Information of the presence of the container may be sent to the app on the smart device 104.
Buttons (
Microphone. In some embodiments, the smart scale 102 has a microphone (not shown) that can record voice commands from the user and send them to the app for processing. A microphone/speaker combination on the smart scale 102 can be used to accomplish hands-free voice links with another remote user (like a phone call) during cooking. The audio connection for the microphone to the smart device 104 can be analog or digital. Voice commands could include: “Pause”; “Resume”; “Next”; “Back”; and “Start Timer”.
The smart scale 102 sends real-time data as analog audio data on the microphone channel, as illustrated in
To aid the user in following a recipe and measuring multiple ingredients the culinary ratio system 100 presents an organized view of tasks. Major functions of the culinary ratio system 100 include:
The culinary ratio system 100 displays ingredients and actions of a recipe in a logical and intuitive order.
The build column 112 has one or more recipe blocks 119, representing steps of the recipe. In the depicted embodiment, the build column 112 is shown as comprising recipe blocks 119 that are stacked vertically. However, in other embodiments, the recipe blocks 119 may be arranged in other ways, such as in a horizontal row or in montage. The recipe blocks may be of various types, including recipe action blocks 120 and recipe ingredient blocks 122. A recipe action block 120 is associated with an action step of the recipe. Information related to the associated action step is displayed with the recipe action block 120. Such information typically includes a text description of the action step. A recipe action block 120 can also include a timer icon 124 for an action that the recipe calls to be performed for a specific length of time, like baking, simmering, or mixing. The timer icon may be associated with a timer function of the app that can be set to play an audio alarm or send an email or text. The timer function may be invoked by the user or automatically by the app.
A recipe ingredient block 122 is associated with a step of adding one of the ingredients of the recipe. In some embodiments, each recipe ingredient block 122 has a size based on the target amount of the ingredient in the recipe. In some embodiments, each recipe ingredient block 122 has a small, medium, or large size based on the target amount of the ingredient relative to the other ingredients in the recipe. Optionally, the same size recipe block could be used for all ingredients and actions. As each recipe block becomes active, it could expand to a larger block with more information, and then shrink as the next recipe block is activated. An ingredient icon 129 can also be displayed with a recipe ingredient block 122 to indicate the ingredient's type like fruit juice, powder, or liquid, or to indicate a particular ingredient.
In the depicted embodiment, recipe construction is displayed from bottom to top. The first action in the build column 112 of
Another way to scale a recipe with the culinary ratio system 100 is to edit the amount used by one ingredient. The user selects one of the ingredients and then selects the target amount for the ingredient, which will cause the app to bring up an amount editor. The user simply enters a new target amount for this ingredient. The app changes the scaling factor of the recipe accordingly to maintain the culinary ratios. Then the target amounts for the other ingredients in rest of the build column 112 are automatically updated according to the scaling factor.
One more way to adjust the scale of a recipe with the culinary ratio system 100 is simply to add a larger amount for one of the ingredients during assembly of the recipe. The app may automatically change the scaling factor of the recipe if the measured amount of an ingredient exceeds the target amount for the ingredient, or in some embodiments, an upper threshold set slightly above the target amount. The app changes the scaling factor of the recipe accordingly to maintain the culinary ratios.
In
Weight-based auto-advance: This option applies to events that involve a measureable weight change. Some examples of events include:
Audio command advance: A microphone may be monitored for vocal commands. The microphone may be mounted in the smart scale 102, built into the smart device 104, or connected to the smart device 104 by some other means such as Bluetooth. Some examples of possible vocal commands are:
Recipe block selection: The user can actively choose another recipe block by interacting directly with the smart device 104 using touch screens or pointing devices like mice.
Scale button navigation: Buttons or touch sensors on the smart scale 102 can be used to advance or navigate up and down the build column. These buttons could be labeled “Next” or “Previous” or simply have arrows.
When adding ingredients it may be too much to ask any human to add the perfect amount with double-digit accuracy.
For ingredients that are added by pouring it can be helpful if the dead-band is off-center and to make it easier for the user to get close to the target amount.
The user can choose the active ingredient at any time.
The culinary ratio system 100 keeps an ingredient history of ingredient events. An ingredient event is essentially any measured ingredient activity occurring out-of-order or between periods of inactivity. Each significant ingredient event is delineated graphically for the user.
The ingredient history is particularly useful for correcting mistakes. If the user accidentally added “lime juice” while the second recipe block 144 (“tequila”) is active, this will be recorded as its own ingredient event. The user can correct this mistake by selecting the ingredient event region 156 related to the mistake and moving it to the fourth recipe block 152 (“Lime Juice”). This correction is shown in
The ingredient history is tracked in an ingredient history table.
Those skilled in the art will recognize that numerous modifications and changes may be made to the preferred embodiment without departing from the scope of the claimed invention. It will, of course, be understood that modifications of the invention, in its various aspects, will be apparent to those skilled in the art, some being apparent only after study, others being matters of routine mechanical, chemical and electronic design. No single feature, function or property of the preferred embodiment is essential. Other embodiments are possible, their specific designs depending upon the particular application. As such, the scope of the invention should not be limited by the particular embodiments herein described but should be defined only by the appended claims and equivalents thereof.
This application is a continuation of co-pending U.S. Non-Provisional Application Ser. No. 14/339,126, filed 23 Jul. 2014 which is a continuation of U.S. Non-Provisional application Ser. No. 13/918,984, filed 16 Jun. 2013, which in turn claims the benefit of, and priority to U.S. Provisional Patent Application Ser. No. U.S. Provisional Application No. 61/800,252 filed on 15 Mar. 2013, all incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
3655003 | Yamajima | Apr 1972 | A |
4102295 | Crook | Jul 1978 | A |
4807169 | Overbeck | Feb 1989 | A |
4840239 | Slagg | Jun 1989 | A |
5167289 | Stevenson | Dec 1992 | A |
5544684 | Robinette | Aug 1996 | A |
5960440 | Brenner | Sep 1999 | A |
6064050 | Ishikawa | May 2000 | A |
6354996 | Drinan | Mar 2002 | B1 |
6375043 | LeBlanc | Apr 2002 | B1 |
6422422 | Forbes | Jul 2002 | B1 |
6452608 | Goken | Sep 2002 | B1 |
6587739 | Abrams | Jul 2003 | B1 |
6674019 | Oldendorf | Jan 2004 | B2 |
6789067 | Liebenow | Sep 2004 | B1 |
6837148 | Deschenes et al. | Jan 2005 | B1 |
6978221 | Rudy | Dec 2005 | B1 |
7076733 | Smith | Jul 2006 | B2 |
7170016 | Dumornay | Jan 2007 | B2 |
7292146 | Nguyen | Nov 2007 | B1 |
7509588 | Van Os | Mar 2009 | B2 |
7523302 | Brown | Apr 2009 | B1 |
7770117 | Uy | Aug 2010 | B1 |
7875813 | Hackathorne | Jan 2011 | B2 |
8200548 | Wiedl | Jun 2012 | B2 |
8342847 | Do | Jan 2013 | B2 |
8636516 | Batsikouras | Jan 2014 | B2 |
8657604 | Gilchrist | Feb 2014 | B2 |
8770983 | Batsikouras | Jul 2014 | B2 |
20020074170 | Oldendorf | Jun 2002 | A1 |
20030159857 | Lin | Aug 2003 | A1 |
20040118618 | Davidson | Jun 2004 | A1 |
20040148117 | Kirshenbaum | Jul 2004 | A1 |
20080135309 | Yuyama | Jun 2008 | A1 |
20090009815 | Karasik | Jan 2009 | A1 |
20090083327 | Ringham | Mar 2009 | A1 |
20090157752 | Gonzalez | Jun 2009 | A1 |
20090164933 | Pederson | Jun 2009 | A1 |
20090178857 | Yuyama | Jul 2009 | A1 |
20090258331 | Do | Oct 2009 | A1 |
20090259687 | Do | Oct 2009 | A1 |
20100000801 | Smith | Jan 2010 | A1 |
20100038149 | Corel | Feb 2010 | A1 |
20100184479 | Griffin | Jul 2010 | A1 |
20100240962 | Contant | Sep 2010 | A1 |
20110167100 | Brodowski | Jul 2011 | A1 |
20110168456 | Sharawi | Jul 2011 | A1 |
20110213667 | Ierullo | Sep 2011 | A1 |
20120136864 | Ochtel | May 2012 | A1 |
20120179665 | Baarman | Jul 2012 | A1 |
20120226698 | Silvestre | Sep 2012 | A1 |
20130007615 | Goldman | Jan 2013 | A1 |
20130029298 | Batsikouras | Jan 2013 | A1 |
20130101709 | Rader | Apr 2013 | A1 |
20130171304 | Huntley | Jul 2013 | A1 |
20130183642 | Wan | Jul 2013 | A1 |
20140318874 | Moses | Oct 2014 | A1 |
20140332289 | Gallagher | Nov 2014 | A1 |
20150260699 | Minvielle | Sep 2015 | A1 |
20150325142 | Ghalavand | Nov 2015 | A1 |
Number | Date | Country |
---|---|---|
201221791 | Apr 2009 | CN |
101464685 | Mar 2010 | CN |
102401689 | Apr 2012 | CN |
2251960 | Jul 1992 | GB |
2251960 | Jul 1992 | GB |
2397657 | Jul 2004 | GB |
2450003 | Dec 2008 | GB |
S6111615 | Jan 1986 | JP |
62067415 | Mar 1987 | JP |
S6267415 | Mar 1987 | JP |
H0552724 | Mar 1993 | JP |
05052724 | Jul 1993 | JP |
2001336756 | Dec 2001 | JP |
2003004518 | Jan 2003 | JP |
2005010951 | Jan 2005 | JP |
2007128305 | May 2007 | JP |
2007132567 | May 2007 | JP |
2009139186 | Jun 2009 | JP |
2009151787 | Jul 2009 | JP |
2011102753 | May 2011 | JP |
2012027031 | Feb 2012 | JP |
2012120791 | Jun 2012 | JP |
20110139492 | Dec 2011 | KR |
1020110139492 | Dec 2011 | KR |
0238456 | May 2002 | WO |
2004065916 | Aug 2004 | WO |
2009100868 | Aug 2009 | WO |
2014021710 | Feb 2014 | WO |
Entry |
---|
Lee W. Young, Written Opinion of the International Searching Authority, PCT/US14/25051, Sep. 23, 2014, pp. 1-26, IPEA/USPTO, Alexandria VA, USA. |
My Recipe Book,“Typing Recipes into the App”, Oct. 5, 2012, Retrieved on Apr. 9, 2013 from http://www.myrecipebookapp.com/?p=90 , Retrieved on Oct. 28, 2016, 8 pages. |
Pham, Coung et al., “The Ambient Kitchen: A Pervasive Sensing Environment for Situated Services” http://www.clarehooper.net/publications/2012/DIS2012demo.pdf, Jun. 11, 2012, retrieved Oct. 28, 2016, 2 pages. |
Seth, Radhika, “Tasy Tasings”, http://www.yankodesign.com/2012/10/23/tasty-tastings/, Oct. 23, 2012, Retrieved Oct. 28, 2016, 8 pages. |
Turnage, Will, “Kitchen Scale App Prototype”, http://www.youtube.com/watch?v=S5WNCv4cqfg Apr. 22, 2012, Retrieved on Oct. 28, 2016, 5 pages. |
Turnage, Will; Lee, Mike “My Robotic Kitchen”, Oct. 21, 2014, https://www.youtube.com/watch?v=ZndhNk-sBfA Retrieved on Oct. 28, 2016, 5 pages. |
Wiasmitinow, Alexis, “EveryCook”, Dec. 20, 2012, https://www.youtube.com/watch?v=HDx75KTG8h0#! Retrieved on Aug. 25, 2015, 9 pages. |
First Office Action, Chinese Application No. 201480016063.4, National Stage of PCT/US14/25051, May 30, 2016, pp. 1-6, State Intellectual Property Office of the People's Republic of China, Beijing, P.R. China. |
Kim, Min-Seok, Notice of Allowance, Korean Application No. 10-2015-7029078, National Stage of PCT/US14/25051, dated Nov. 14, 2016, pp. 1-2, Korean Intellectual Property Office, Daejeon, ROK. |
Second Office Action, Chinese Application No. 201480016063.4, National Stage of PCT/US14/25051, Jan. 25, 2017, dated pp. 1-5, State Intellectual Property Office of the People's Republic of China, Beijing, P.R. China. |
Kosuke Kumondai, First Office Action, Japanese Application No. 2016-501733, National Stage of PCT/US14/25051, dated Apr. 14, 2016, pp. 1-10, Japan Patent Office, Chiyoda-kuTokyo, Japan. |
Kosuke Kumondai, Notice of Allowance, Japanese Application No. 2016-501733, National Stage of PCT/US14/25051, dated Nov. 14, 2016, pp. 1-3, Japan Patent Office, Chiyoda-kuTokyo, Japan. |
Couzy, Francois, Supplemental Search Report, European Application No. 14 76 8278, National Stage of PCT/US14/25051, dated Nov. 25, 2016, pp. 1-7, European Patent Office, Munich, Germany. |
Jean Fortin, First Examiners Report, Canadian Application No. 2901934, National Stage of PCT/US14/25051, dated Nov. 9, 2015, pp. 1-4, Canadian Intellectual Property Office, Vancouver, Canada. |
Jean Fortin, Notice of Allowance, Canadian Application No. 2901934, National Stage of PCT/US14/25051, dated Feb. 11, 2016, p. 1, Canadian Intellectual Property Office, Vancouver, Canada. |
Randy Gibson, First Office Action, U.S. Appl. No. 14/339,126, Continuation of U.S. Appl. No. 13/918,984 (U.S. Pat. No. 8,829,365), dated Nov. 7, 2016, pp. 1-19, United States Patent and Trademark Office, Alexandria, Virginia. |
Randy Gibson, Notice of Allowance, U.S. Appl. No. 14/339,126, Continuation of U.S. Appl. No. 13/918,984 (U.S. Pat. No. 8,829,365), dated Nov. 7, 2016, pp. 1-5, United States Patent and Trademark Office, Alexandria, Virginia. |
John M. Hotaling II, First Office Action, U.S. Appl. No. 90/013,856, Reexamination of U.S. Appl. No. 13/918,984 (U.S. Pat. No. 8,829,365), dated Mar. 9, 2017, pp. 1-53, United States Patent and Trademark Office, Alexandria, Virginia. |
John M. Hotaling II, Notice of Intent to Issue Ex Parte Reexamination Certificate, U.S. Appl. No. 90/013,856, Reexamination of U.S. Appl. No. 13/918,984 (U.S. Pat. No. 8,829,365), dated Jul. 5, 2017, pp. 1-17, United States Patent and Trademark Office, Alexandria, Virginia. |
Number | Date | Country | |
---|---|---|---|
20150351441 A1 | Dec 2015 | US |
Number | Date | Country | |
---|---|---|---|
61800252 | Mar 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14339126 | Jul 2014 | US |
Child | 14831778 | US | |
Parent | 13918984 | Jun 2013 | US |
Child | 14339126 | US |