The present invention relates to temperature monitoring systems and methods, such as for food preparation.
In many heating processes such as food preparation and cooking, the temperature of the item or material being heated is of critical importance in obtaining a suitable or desired result. In cooking, for example, the temperature of the food plays a role, often determinative, in the degree to which the food is cooked. The temperature itself may be indicative as to the degree to which the food is cooked. The degree to which the food is cooked is not only relevant to the taste of the food, as may be desired by the person consuming food, but also highly relevant to the safety of the food. To this end, for example, the U.S. Department of Agriculture (USDA) has issued guidelines establishing food temperatures at which it considers the food, e.g., beef, poultry, pork, etc. to be adequately cooked to sufficiently destroy microbial or other biological contaminants in the food so as to be generally safe to eat. In addition, the temperatures necessary to provide a desired degree of cooking or taste (e.g., rare, medium, well-done) are generally known.
For this purpose, food thermometers may be used to measure the temperature of the food. A drawback of standard food thermometers is that one is required to be physically present at the location the food is being cooked in order to view the temperature of the food displayed by the thermometer. This inconveniently prevents the user from attending to other activities and/or requires the user to return to the cooking location to monitor the progress of the cooking. If the user does not return in time, the food may be overcooked.
Devices that remotely monitor the temperature of the food being cooked are known. However, known devices have several drawbacks. First, such devices require specialized equipment including a first unit located at the location the food is being cooked, and a second unit located remotely from the food cooking location. The use of two specialized units incurs increased costs. Further, known devices have limited flexibility in use and limited programmability.
The present invention provides temperature monitoring systems and methods whereby the temperature status of an item or items may be monitored and/or controlled from a location that is different from the location at which the item is located. In various embodiments, the temperature status may be monitored and/or controlled via communication between a first unit located at or near the location at which the item is located, and a second unit located at a different location. The first unit may include or be operatively connected to one or more temperature sensors by which the temperature(s) of the item(s) is determined. Temperature information is then transmitted to the second unit, which is relayed to a user by visual or other indication.
The heating parameters of the item may be entered, programmed, or selected by a user using the second unit. The second unit may then determine various heating characteristics of the item, such as, by way of example only, heating time. The second unit may utilize the temperature received from the first unit to update the status and heating characteristics on a real-time or near real-time basis. In additional embodiments, heating parameters may be set, modified, or altered by a user utilizing the first unit, which communicates this information to the second unit. The second unit then may adjust or update its programming and its determination of the heating characteristics and status of the item.
In various embodiments, the second unit is a computer or computerized electronic device that is not specific to heating applications or the first unit, but has the necessary existing hardware, firmware and/or software capabilities so that a heating application, e.g., a program or computer application, may be installed and executed, on a temporary or permanent basis, to communicate with the first unit. Examples of such devices include, but are not limited to, smartphones (BLACKBERRY, IPHONE, etc.), computers (desktop, laptop, etc.), handheld computing devices, and other portable computerized devices (PDA, IPAD, IPOD, etc.). In these embodiments, only the first unit and temperature sensor need be provided and/or purchased by the user, and a software application installed on the user's existing (or otherwise acquired) second unit. Thus, the cost of a second unit, from both the manufacturing and purchasing perspective, is avoided.
Such second units also provide flexibility in the software application because it can take advantage of the existing capabilities of the second unit. Such capabilities may include, by way of example only, storing and/or downloading (e.g., Internet) information such as multimedia for presentation or playback to the user, and the ability to easily alter or update the software application itself and the information stored in the second unit utilized by the application. Further, where the second unit is portable, the user may move to other locations and/or attend to other activities and remain updated as to the status of the item. To where the user may move and remain updated from the first unit is limited only by the built-in communication capabilities of the second unit. In embodiments where the second unit has multiple communication modes, e.g., wireless, Bluetooth, Internet, etc., these may be utilized and/or selected as needed or desired so that the second unit may receive the temperature information from the first unit.
Certain embodiments of the invention may be used for food preparation, such as for cooking or heating food. In such embodiments, the status of a food being cooked is monitored and/or controlled from a location that is different from the location at which the food is being cooked. More specifically, the status of the food is monitored and/or controlled via communication between a first unit located at or near the location at which the food is being cooked, and a second unit located at a different location. In such embodiments, the user may select the cooking parameters for the food using the second unit, which then determines the cooking characteristics of the food. The user may then attend to other activities while the food is cooking, and may monitor the temperature and/or status of the food on the second unit. Yet further, the second unit may notify the user when the food is done so that the user can locate to the cooking equipment and turn it off or otherwise remove the food from the cooking device. In yet additional embodiments, if the user wishes to cook the food more, the user can update one or more cooking parameters on the first unit, which transmits those updated parameters to the second unit, which updates the cooking characteristics. The user can then proceed to another location and be re-notified when the food is done cooking in accordance with the newly entered parameters.
Other objects and advantages of the present invention will become apparent in view of the following detailed description of the embodiments and the accompanying drawings.
In
A temperature sensor 30 is used to determine the temperature of the food item 5. The temperature sensor 30 may be a temperature probe, such as those that are currently known and available. Such probes are available from multiple sources, such as Cooper-Atkins Corporation of Middlefield, Conn. The probe may be a thermistor-type temperature sensor, a thermocouple-type sensor, or another type of sensor as may be known or become known.
The sensor 30 has a sensing portion 32 at a distal end that contacts or is inserted into the food 5 and senses the temperature, and a cable 35 that provides the information or signal from the sensor 30. A sensor connector 38 is located at a proximal end of the sensor 30 for connecting the sensor 30 to another component and transmitting the temperature information or signal to that component. The cable 35 and connector 38 may also be used to supply electrical current to the sensing portion 38. For example, in a thermistor-type sensor, an electrical current, usually a small current, is supplied to the probe 30.
In
The sensor 30 is constructed so that it may sense the temperature of the food 5 at a desired location. For example, it may be desired to sense the temperature of an internal portion of the food. In such embodiments, the sensing portion 32 is constructed so that it may be inserted into the food an appropriate distance to measure the temperature at the desired location. For example, the sensing portion 32 may contain a piercing portion 40 configured to pierce the food via a cutting or piercing shape, e.g., a needle shape. The temperature may be sensed at the location of the piercing portion 40. In further embodiments, the sensing portion 32 contains one or more indicia 42 indicating the depth that the sensing portion 32 is inserted. These depth indicators 42 can assist a user in positioning the sensing portion 32 at the desired depth or location.
In the embodiment of
It should be understood that while
As shown in
As shown in
In other embodiments, the remote unit 100 may have more than one receptacle 120 or sensor connection so that more than one sensor 30 may be used at one time. Alternatively, two sensors may be connected to the remote unit using one cable 35 and receptacle. In such embodiments, the remote unit 100 determines the sensed temperature of each sensor 30 and communicates those temperatures to the control unit 200. For example, two sensors 30 may be used to sense the temperatures of separate food items 5 being cooked, which may require different cooking temperatures from each other. Accordingly, the food items may be cooked in separate cooking devices 10. Alternatively, multiple sensors 30 may be placed in different parts of a single food item to monitor the temperature in more than one location. The use of multiple temperatures may assist in the determination of whether the food item as whole is cooked or heated as desired.
The remote unit 100 determines the temperature sensed by the sensor 30 by any suitable techniques that are currently known of may become known. For example, when using a thermistor-type sensor 30, the temperature is determined by correlating the electrical resistance or change in resistance of the material in the sensor that changes with temperature (e.g., by measuring voltage or current passing though the sensor 30) to a temperature of the material. In a thermocouple-type sensor, the temperature is determined by correlating the voltage or change in voltage across the sensor 30, which changes with temperature, to the temperature of the sensor 30. Those of ordinary skill in the art should understand how to determine the temperature of the food item using temperature sensors as contemplated by the invention.
The remote unit 100 comprises a case 110 that encloses the internal components of the remote unit. The case 110 may be of any suitable material and construction, as will be appreciated by those in the art. The case 110 may be constructed to provide relative durability of the remote unit 100 in the operating environment. For example, in case of use of the remote device 100 with a grill 10 as depicted in
The remote unit 100 may include a handle 130 to facilitate carrying, placement or storage of the remote unit 100. As shown in the figures, the handle 130 has a bent, hooked, or C-shaped configuration so that it may be removably, hangingly placed, e.g., hanging from the grill cover handle 16. The handle 130 is movable from a folded position as shown in
Those in the art should appreciate that the handle 130 may take many different forms, shapes, and configurations. For example, in some embodiments the handle 130 is fixed in one position. In yet other embodiments, the handle 130 may be movably connected to the remote unit 100 by means other than a hinge. For example, the handle 135 may be slidingly connected to the remote unit so that it may be slid from a retracted or closed position to an extended or open position. Those skilled in the art will appreciate the various configurations of connections and movement of the handle that may be utilized in the present invention.
The case 110 may contain one or more cavities 142, 145 facilitating the storage and carrying of the sensor 30. As seen in the figures, cavities 142 receive the cable 35 and cavity 145 receives at least a portion of the sensing portion 32. In this manner, the cable 35 and/or sensing portion 32 are maintained in compact condition with the remote unit 100.
The remote unit 100 may contain a user interface 150 that displays information to the user and/or allows the user to control various functions of the remote unit 100. For example, the user interface 150 may display the current sensed temperature 155 of the food, as shown in
The user interface 150 may contain additional functionality as desired. For example, as seen in
As those of ordinary skill will appreciate, the user interface 150 may have various different configurations. For example, the buttons 156, 157, 159 or keypad may be mechanical or electromechanical in nature, e.g., switches. The temperature display 155 may be, for example, an LED, LCD, plasma, or other type of display. In some embodiments, the user interface 150, or parts thereof, may be a touch sensor or touch screen interface, as is known, where the temperature display 155, keypad/keyboard, buttons 156, 157, 159 and other controls are virtual in nature and may be altered or modified. In such embodiments, for example, the user could toggle between the current sensed temperature 155 of the food and the set temperature 155 by touching the display, e.g., the temperature 155. In yet further embodiments, the remote unit 100 can dim or turn off the user interface 150 after a predetermined interval of non-use or in a power conservation mode, and then reactivate the interface 150 upon the user touching the interface 150.
As seen in
The power supply 172 may include or be operatively connected to any suitable power source sufficient to supply power to the remote unit 100. In some embodiments, the power supply may include a battery or batteries 172a. The battery 172 may be a rechargeable or non-rechargeable battery that can be removed from the remote unit 100 when depleted, or a rechargeable battery that generally remains within the remote unit 100 and is recharged via a power jack 172b connectable to an external power source, e.g., an electrical outlet. Alternatively, the power supply 172 may receive power directly from an external power source without utilizing a battery.
Under the control of the processor 170, the communication unit 174 transmits information to, and in some embodiments, may receive information from the control unit 200. The remote unit 100 transmits the currently sensed temperature 155 to the control unit 200 for utilization by the control unit 200 as further discussed below. In addition, in embodiments where the user can alter the set temperature 155 using the remote unit 100, the revised set temperature may be transmitted to the control unit 200. These transmissions may be made by any suitable transmission methods as will be appreciated by those of ordinary skill in the art. Examples of such methods include, but are limited to, Bluetooth, radio frequency, infrared, and wireless network (e.g., IEEE 802.11/a/b/g/n) protocols. Suitable wireless components include, but are not limited to, Bluetooth modules with Class 2 power output, implementing at least Bluetooth specification V2.0+EDR (Enhanced Data Rate) compliance. Suitable modules include, but are not limited to, modules from ZBA Inc. (BT44-191S) of Hillsborough, N.J., Bluegiga Technologies Inc. (WT12) of Duluth, Ga., and Laird Technologies (BTM411) of St. Louis, Mo. In other embodiments, the remote unit 100 may communicate with the control unit 200 through a wired connection, e.g., a hard-wire or wired network connection, or a combination of wired and wireless connection(s). Those of ordinary skill in the art will understand how to construct and implement the remote unit 100 so as to communicate with the control unit 200 as discussed herein.
The temperature 155 may be communicated to the control unit 200 utilizing a “push” protocol, in which the temperature 155 is communicated to the control unit 200 without a query or request from the control unit 200 to do so. The temperature 155 may be transmitted to the control unit 200 continuously. Alternatively, the temperature 155 may be transmitted to the control unit 200 at intervals in order to conserve power or minimize processing time the control unit 200 must dedicate to the cooking application. The transmission interval may be pre-set or definable, e.g., every 1 to 10 seconds, such as, for example, every 5 seconds. However, it should be understood that whether continuous or interval transmission is used may depend on the food item 5 being cooked or heated, or the degree of cooking/heating, and the cooking method 10. For example, for a food item that is being cooked or heated very quickly, or is expected to reach its desired temperature quickly, it may be desirable to implement continuous transmission or short intervals. On the other hand, a food item 5 that is being heated very slowly or is expected to cook for a long time (e.g., hours), a longer interval, e.g., several minutes, may be suitable. Those of ordinary skill should understand how to implement a suitable transmission schedule.
In other embodiments, the temperature 155 transmission may implement a “pull” protocol, where the temperature is communicated to the control unit 200 when the control unit 200 communicates, and the remote unit 100 receives, a request or query from the control unit 200 (e.g., via communication unit 174) to relay the temperature 155. In this manner, the temperature 155 may be transmitted when the control unit 200 requires or otherwise determines it is necessary to receive the temperature, conserving power and control unit 200 processing resources, e.g., based on the cooking and/or food profiles as discussed further below. In further embodiments, both “push” and “pull” protocols may be utilized.
As described above, the control unit 200 wirelessly receives data about the cooking process from the remote unit 100 and displays the data via the interface 300 in a useful manner to the user. As one example, the interface 300 may display the current temperature of the cooking item 5, as measured by the sensing portion 32 of the probe(s) 30. The control unit 200 can be relatively small to be portable and be able to be carried or moved by the user so that the user need not remain close to the control unit 200 and view, or be alerted by, the interface 300. The display means of the interface 300 may be any means, currently known or that later become known, capable of relaying the received data to the user, such as means that visually displays the data. In some embodiments, the interface 30 is an electronic screen that visually displays the data, such as a liquid crystal display or a plasma display. In the illustrated embodiment shown in
In some embodiments, the interface 300 only displays received data that is transmitted from the remote unit 200, such as the temperature of the cooking item 5, elapsed cooking time, whether the remote unit 100 is “on” and/or “connected” to the control unit 300, etc. In other embodiments, the interface 300 allows a user to input, selectively access, and/or manipulate data or commands in addition to displaying received data. For example, if the control unit 200 is capable of storing and running computer programs or applications (e.g., includes at least some memory and a processor), the interface 300 may allow a user to access a program that manages the connection between the control unit 200 and the remote unit 100. In some embodiments, the interface 300 also displays and allows users to access or manipulate data that is retrieved, accessed, and/or computed by the control unit 200. For example, the interface 300 may display data that is computed or extrapolated by the program or application from data that is received from the remote unit 100, entered by the user, and/or otherwise obtained or entered into the control unit 200 and/or the program/application. In some such embodiments, the control unit 200 and/or interface 300 includes input means for accessing the program, inputting data, or otherwise communicating with the control unit 200. Such input means may be any means, currently known or that later becomes known, capable of allowing a user to input data, enter commands, access data stored in, or accessible by, the control unit 200, and combination thereof. For example, the input means may be a keyboard, mouse, trackball, touch-screen, microphone, motion sensor, light sensor, etc., and may be part of, or combined with, the display means of the interface 300. In the illustrated embodiment shown in
As shown in
One function of the application may be to manage the wireless connection between the remote unit 100 and the control unit 200 (e.g., via a Bluetooth (short length radio waves) based connection, as described above). In one embodiment, when the application is accessed by the user it automatically “searches” for the signal emitted by the remote unit 100 and either automatically “connects” or “syncs” to the signal, or prompts the user via the interface 300 to make the connection (e.g., by selecting a “connect” or “sync” link or icon displayed on the interface 300). In other embodiments, the user is prompted or manually commands the application to connect or sync with the remote unit 100. Such a prompt may occur soon after the application is opened or loaded by the user. Further, an indication that the sync or connection between the remote unit 100 and the control unit 200 was successful or not may be displayed, at least just after the “sync” or “connection” is attempted, so that the user knows whether or not the sync or connection was successful.
In some embodiments, the application further includes a connection drop notification feature. The connection drop notification feature includes a communication to the user via the interface 300 (e.g., a blinking light, vibration, or visual notification) that a previously established connection between the remote unit 100 and the control unit 200 has been “dropped” or has otherwise failed (and thus the control unit 200 is no longer receiving data from the remote unit 100, such as the temperature of the cooking item 5). The connection drop notification feature may check or test the connection at predetermined set time intervals after a connection has been established, such as every 30 seconds, minute, 2.5 minutes, 5 minutes, or any other time interval. In other embodiments, the connection drop notification feature may be initiated when the application detects a drop in the amount of received data that is beyond a predetermined data set point or a set point that is calculated by the application based on the average amount of data received over a certain time frame after the “connection” was initially established. In some embodiments, the connection drop notification includes a connection monitor that can be accessed by the user or is continuously displayed on the interface 300, which evaluates and displays the strength and/or quality of the connection. The connection monitor may thereby allow a user to determine which locations of the control unit 200, in respect to the location of the remote unit 100, may be more or less likely prone to a connection failure.
In some embodiments, the application includes an event log feature that saves the data received from the remote unit 100 before a connection is lost or dropped. For example, the event log feature may save and display the estimated “finish” time and the amount of time between the current time and the estimated “finish” time (as explained in further detail below), and alert the user via the interface 300 before (e.g., approximately five minutes before) the estimated “finish” time and at the estimated “finish” time. Thereby, the event log feature prevents against a failed connection from completely disabling the alert feature of the control unit 300/program (to ensure that the user does not mistakenly overcook the cooking item 5) by providing an alert based on the estimated “finish” time.
As shown in
As shown in the illustrated embodiment, the tabbed categories of information on the menu bar 302 may include stats 306 relating to the cooking item 5 and cooking process, tips 308, recipes 310, and a browser 312. However, these categories are only exemplary, and any other categories that are known, or that later become known, may equally be employed. For example, other categories relating to the cooking item 5 (e.g., a meat), method (e.g., barbeque, stove, grill, etc.), style (e.g., Cajun), equipment (e.g., coal burning barbeque), technique (e.g., rotisserie), occasion (e.g., a particular holiday), location (e.g., a location that carries a particular food connotation or style), safety (e.g., how to properly prepare or handle a certain cooking item 5), menu (e.g., shopping list associated with a particular menu), audience (e.g., children), etc.
The cooking item's profile 314 may include (and display) information relating to the actual cooking item 5. For example, the cooking item's profile 314 can include the type of cooking item 5 (e.g., a particular type of meat, poultry, fish, vegetable, fruit, etc.), information about the actual cooking item 5 (e.g., the specific cut of the meat, poultry part, fish, vegetable, fruit, etc.), and information about the physical attributes of the cooking item 5 (e.g., thickness, weight, length, volume, area, etc.). These types or categories of information are exemplary, and any other type of information that may be beneficial in determining how the cooking item 5 should be prepared (e.g., heated) may equally be employed. The cooking item's profile 314 is particularly advantageous because it can be used to determine the specific ultimate temperature that the cooking item 5 must reach to be safe to eat (e.g., the temperature at which harmful bacteria have been destroyed) and when the cooking item 5 is prepared to a particular user's taste (e.g., the graduation of the cooking amount, such as rare, medium, well-done, etc.). For example, some embodiments use data (e.g., an internal temperature cooking chart or table) that is either provided by the application (e.g., saved in the memory of the control unit 200) or accessed by the program (e.g., via the Internet) regarding the USDA's or other suggested correct (cooked) temperatures for all possible cooking graduations of all possible cooking item profiles 314. In some such embodiments, the application can parse the data to match the correct USDA temperature (e.g., internal temperature) with the cooking item's profile 314. As an example, if a cooking item's profile matches that of the cooking item's profile 314 shown in
Another advantageous feature of the application and the cooking item's profile 314 (e.g., the desired ultimate temperature (e.g., internal temperature) of the cooking item 5) is that that the application can trigger the user interface 300 to alert the user when the actual, current internal temperature of the cooking item 5 has reached the user's desired ultimate internal temperature or cooking condition (e.g., a temperature corresponding to a particular cooking graduation). For example, the program may alert the user via the interface 300 (e.g., display a message on the interface 300, vibrate, display blinking lights, play a sound(s), etc.) when the sensing portion 32 of the probe(s) 30 indicates that the current, internal temperature of the cooking item 5 has reached the user's desired ultimate internal temperature. In this manner, the remote unit 100, control unit 200, interface 300 and/or application prevent the user from over-cooking or under-cooking the cooking item 5, but rather alerts the user when the cooking item 5 has been cooked to the user's liking (i.e., the cooking item's profile 314). As another example, and as explained in further detail in the “current status 316” section below, the application also may trigger the user interface 300 to alert the user that the internal temperature of the cooking item 5 will be reaching the user's desired internal temperature in a set time period (e.g., the user's desired ultimate temperature will be reached in about five minutes).
The cooking item's profile 314 may be input by the user via the interface 300 into the program at the “home” or other screen (as shown in
In some embodiments, the user is able to input the specific temperature to which they wish to heat the cooking item 5, instead of, or in addition to, the cooking item's profile 314. For example, if the user knows the temperature that they would like their cooking item 5 to reach, the user would not need to enter the cooking item's profile 314 to determine such temperature. In some embodiments, the application and interface 300 would also allow the user to change the cooking item's profile 314 (e.g., the ultimate internal temperature of the cooking item 5) during cooking (e.g., a change from rare to medium). In some such embodiments, the program may allow the user to simply adjust the desired internal temperature of the cooking item 5, such as by increasing or decreasing the temperature degree-by-degree or degree interval (e.g., by entering a new temperature or by selecting a button, link, icon, or the like on the interface 300 to increase or decrease the ultimate internal temperature). As explained above, if the ultimate temperature is changed (or even initially set) at the remote unit 100, the remote unit 100 may transmit the desired ultimate temperature to the control unit 200 and the program would automatically be updated with the adjusted desired ultimate temperature.
The cooking item's temperature 320 displayed on the interface 300 may include information relating to the current temperature (e.g., interior) of the cooking item 5. As described above, the sensing portion 32 of the probe(s) 30 can be used to measure the actual, current temperature (e.g., internal) of the cooking item 5, and the remote unit 100 used to transmit the temperature data to the control unit 200. As discussed above, the remote unit 100 may transmit the actual, current temperature reading of the cooking item 5 at intervals, e.g., about every five seconds. However, any other time interval may equally be employed. Similarly, as discussed above, the control unit 200 and/or application may request a temperature reading from the remote unit 100 at set time intervals and/or by a specific command or request by the user that is in addition to, or instead of, the remote unit 100 automatically sending the temperature reading at set time intervals. The cooking item's temperature 320 may also display the temperature trend on the cooking item 5, and/or the current temperature reading as compared to the user's desired ultimate temperature. See, e.g., cooking item's temperature 320 of
As also shown in
Similar to how the alert is triggered when the temperature of the cooking item 5 approaches or reaches the correct ultimate temperature determined by the cooking item's profile 314, in some embodiments the application may trigger the interface 300 to alert the user when the temperature of the cooking item 5 surpasses the correct ultimate temperature (e.g., by a predetermined or user selected temperature difference, such as 15 degrees). In some embodiments, the application alerts the user when the temperature of the cooking item 5 falls below a certain temperature (e.g., a predetermined or user selected temperature). In some embodiments, the application alerts the user when the estimated time until the cooking item 5 reaches the ultimate correct temperature surpasses a certain time limit (e.g., a predetermined or user selected time limit, such as one hour).
The timer 318 on the interface 300 may include the current cooking time duration, the time that the cooking process began, and/or the estimated time at which the cooking process should be complete according to the cooking item's profile 314 (to achieve the desired cooking graduation). In some embodiments, the cooking duration is calculated by the program by recording the time at which the cooking process began, and subtracting the starting time as compared to the current time. In some such embodiments, the program may record, or is aware of, the times through the use of an internal clock that is present in by the control device 200 and/or accessed by the control device 200 or the program, such as via the Internet. In some embodiments, the elapsed time is calculated by recording the time at which the temperature started to increase above a predetermined level (e.g., above normal ambient temperatures) or when the user indicated that the cooking process began (such as in response to a prompt), and subtracting such time from the current time. In yet another embodiment, the elapsed time is calculated by initiating a timer when the cooking process began. The start time may similarly be determined or recorded. The estimated time at which the cooking process should be complete according to the cooking item's profile 314 may be calculated in a substantially similar manner as the time frames regarding the yet to be achieved cooking graduations, as discussed above with respect to the cooking item's current status 316.
As shown in
As shown in the exemplary illustrated embodiment of
The individual tips displayed in the detailed information sections 304 (whether they are selected from the featured tips section 326 or the series of tips 332) may take on any format that is capable of relaying the tip to the user, such as video, picture, text, audio, or any other means. In this regard, the application may utilize the existing audio, video, etc. capabilities of the control unit 200. In the illustrated embodiment shown in
Similar to the tips category 308,
As shown in the exemplary illustrated embodiment of
The individual recipes displayed in the detailed information section 304 (whether they are selected from the featured recipe section 340 or the series of recipes 346) may take on any format that is capable of relaying the recipe to the user, such as video, picture, text, audio, or any other means. In the illustrated embodiment shown in
Similar to the tips category 308 and the recipe category 310,
Those skilled in the art should recognize that functionality of the control unit 200 may also be present in the remote unit 100. This applies to any or all of the functionality of the control unit 200 as desired. By way of example only, the remote unit 100 may provide the user with an indication that the food 5 has reached the desired temperature or cooking status. As with the control unit 200, this may be a visual indication, e.g., a message or flashing indicator, an audio indication, e.g., a sound or alarm, a tactile indication, e.g., vibration, or other indication. In this manner, if the user is in the vicinity of the remote unit 100, or not in the vicinity of the control unit 200, the user can be notified of the cooking status. The remote unit 100 may determine the desired cooking status independently of the control unit 200, such as, for example, by determining that the sensed temperature has reached the temperature set on the device. In such embodiments, the remote unit 100 may be used without the control unit 200. Alternatively, the control unit 200 may communicate that the desired temperature or cooking status has been reached to the remote unit 100, whereby the remote unit 100 provides the indication to the user. Those skilled in the art will understand how to provide the remote unit 100 with any desired functionality of the control unit 200.
As may be recognized by those of ordinary skill in the pertinent art based on the teachings herein, numerous changes and modifications may be made to the above-described and other embodiments of the present disclosure without departing from the spirit of the invention as defined in the claims. For example, though the embodiments described above relate to the cooking of food, the invention may be utilized to monitor the temperatures of other items and materials. Accordingly, this detailed description of embodiments is to be taken in an illustrative, as opposed to a limiting sense.
This application is a continuation of U.S. patent application Ser. No. 16/411,814, filed May 14, 2019, which is a continuation of U.S. patent application Ser. No. 15/218,330, filed Jul. 25, 2016, which is a continuation of U.S. patent application Ser. No. 14/595,868, filed Jan. 13, 2015, which is a continuation of U.S. patent application Ser. No. 12/790,764, filed May 28, 2010, which claims priority to U.S. Provisional Patent Application No. 61/213,306, filed May 28, 2009. The entireties of U.S. patent application Ser. No. 16/411,814, U.S. patent application Ser. No. 15/218,330, U.S. patent application Ser. No. 14/595,868, U.S. patent application Ser. No. 12/790,764, and U.S. Provisional Patent Application No. 61/213,306 are hereby incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
4447692 | Mierzwinski | May 1984 | A |
4636949 | Longabaugh | Jan 1987 | A |
4727799 | Ohshima et al. | Mar 1988 | A |
4812963 | Albrecht et al. | Mar 1989 | A |
5349162 | Holling | Sep 1994 | A |
5378874 | Holling et al. | Jan 1995 | A |
5539671 | Albrecht et al. | Jul 1996 | A |
5746114 | Harris | May 1998 | A |
6029141 | Bezos et al. | Feb 2000 | A |
6043461 | Holling et al. | Mar 2000 | A |
6046674 | Irwin | Apr 2000 | A |
6080972 | May | Jun 2000 | A |
6313758 | Kobayashi | Nov 2001 | B1 |
6316758 | Ubowski et al. | Nov 2001 | B1 |
6539842 | Chapman | Apr 2003 | B1 |
6568848 | Chapman | May 2003 | B1 |
6615706 | Wu | Sep 2003 | B1 |
6686838 | Rezvani et al. | Feb 2004 | B1 |
6698923 | Bedetti et al. | Mar 2004 | B2 |
6712505 | Chapman | Mar 2004 | B2 |
6811308 | Chapman | Nov 2004 | B2 |
6850861 | Faiola et al. | Feb 2005 | B1 |
6949729 | Ishikawa et al. | Sep 2005 | B1 |
7057142 | Lubrina | Jun 2006 | B1 |
7075442 | Lion et al. | Jul 2006 | B2 |
7102107 | Chapman | Sep 2006 | B1 |
7128466 | Chang et al. | Oct 2006 | B2 |
7201099 | Harris, Jr. et al. | Apr 2007 | B2 |
7202454 | Wiedemann et al. | Apr 2007 | B2 |
7355150 | Baarman et al. | Apr 2008 | B2 |
7372368 | Chapman et al. | May 2008 | B2 |
7703389 | McLemore et al. | Apr 2010 | B2 |
7722248 | Chapman et al. | May 2010 | B1 |
7733224 | Tran | Jun 2010 | B2 |
7775709 | Biscotti et al. | Aug 2010 | B2 |
8384562 | Wall et al. | Feb 2013 | B2 |
8398303 | Kuhn | Mar 2013 | B2 |
8532843 | Nagura et al. | Sep 2013 | B2 |
8920025 | Andreatti | Dec 2014 | B2 |
8931400 | Allen | Jan 2015 | B1 |
9183738 | Allen, Sr. et al. | Nov 2015 | B1 |
9247588 | Baarman et al. | Jan 2016 | B2 |
9497572 | Britt et al. | Nov 2016 | B2 |
9799199 | Allen | Oct 2017 | B2 |
9841287 | Hayward | Dec 2017 | B1 |
9980321 | Sorenson et al. | May 2018 | B2 |
10025282 | Wilkinson | Jul 2018 | B1 |
10067004 | Allen | Sep 2018 | B1 |
10158720 | Colston | Dec 2018 | B2 |
10169665 | Zhang et al. | Jan 2019 | B1 |
10213046 | Nonaka et al. | Feb 2019 | B2 |
10235884 | Song et al. | Mar 2019 | B2 |
10299088 | Uchiyama | May 2019 | B2 |
10339783 | Allen, Sr. | Jul 2019 | B2 |
10388141 | Allen, Sr. | Aug 2019 | B2 |
10395506 | Allen, Sr. | Aug 2019 | B2 |
10416311 | Huang et al. | Sep 2019 | B2 |
10417714 | Christensen et al. | Sep 2019 | B1 |
10462608 | Santarelli et al. | Oct 2019 | B1 |
10491738 | Colston | Nov 2019 | B2 |
10516976 | Rivard et al. | Dec 2019 | B2 |
10559186 | Allen, Sr. | Feb 2020 | B2 |
10674866 | Colston | Jun 2020 | B2 |
10701199 | Colston | Jun 2020 | B2 |
10757244 | Colston | Aug 2020 | B2 |
10785363 | Colston | Sep 2020 | B2 |
10789827 | Allen, Sr. | Sep 2020 | B2 |
11132885 | Allen, Sr. | Sep 2021 | B2 |
11250686 | Allen, Sr. | Feb 2022 | B2 |
20020113057 | Lerner | Aug 2002 | A1 |
20020189462 | Guess | Dec 2002 | A1 |
20030098888 | Guenther et al. | May 2003 | A1 |
20030202558 | Chung et al. | Oct 2003 | A1 |
20040022258 | Tsukada et al. | Feb 2004 | A1 |
20040074435 | Kaiser et al. | Apr 2004 | A1 |
20040115325 | Greiner et al. | Jun 2004 | A1 |
20050274710 | Toyos et al. | Dec 2005 | A1 |
20060027086 | Boyer, Jr. et al. | Feb 2006 | A1 |
20060044935 | Benelli et al. | Mar 2006 | A1 |
20060074546 | DeKock et al. | Apr 2006 | A1 |
20060113295 | Fisher et al. | Jun 2006 | A1 |
20060202848 | Volodarsky | Sep 2006 | A1 |
20060254432 | McLemore | Nov 2006 | A1 |
20060260601 | Styron, Sr. | Nov 2006 | A1 |
20070210062 | Gaynor et al. | Sep 2007 | A1 |
20070215599 | Kahler | Sep 2007 | A1 |
20070221668 | Baarman et al. | Sep 2007 | A1 |
20080043809 | Herbert | Feb 2008 | A1 |
20080056328 | Rund | Mar 2008 | A1 |
20080141868 | Cook et al. | Jun 2008 | A1 |
20080217999 | Baarman et al. | Sep 2008 | A1 |
20090116535 | Rund | May 2009 | A1 |
20090134151 | Bogatin et al. | May 2009 | A1 |
20090194526 | Buchanan | Aug 2009 | A1 |
20090229475 | Bally et al. | Sep 2009 | A1 |
20100034935 | Wally et al. | Feb 2010 | A1 |
20100132692 | Shaffer | Jun 2010 | A1 |
20100301034 | Greenwood et al. | Dec 2010 | A1 |
20100303972 | Srivastava | Dec 2010 | A1 |
20110231099 | Elkins | Sep 2011 | A1 |
20130156902 | Shirali et al. | Jun 2013 | A1 |
20130247117 | Yamada et al. | Sep 2013 | A1 |
20130247898 | Balcerzak et al. | Sep 2013 | A1 |
20130292520 | Alden et al. | Nov 2013 | A1 |
20130326137 | Bilange et al. | Dec 2013 | A1 |
20150091740 | Bai et al. | Apr 2015 | A1 |
20150142489 | Block et al. | May 2015 | A1 |
20150194041 | Allen | Jul 2015 | A1 |
20150196161 | Myllymaki | Jul 2015 | A1 |
20160088049 | Seed et al. | Mar 2016 | A1 |
20160153789 | Gallar et al. | Jun 2016 | A1 |
20160229435 | Ryan | Aug 2016 | A1 |
20160253049 | Wild et al. | Sep 2016 | A1 |
20160335874 | Allen, Sr. | Nov 2016 | A1 |
20170006449 | Igumnov et al. | Jan 2017 | A1 |
20170113512 | Park et al. | Apr 2017 | A1 |
20170243485 | Rubin et al. | Aug 2017 | A1 |
20170288722 | Berry | Oct 2017 | A1 |
20170311228 | Zavesky et al. | Oct 2017 | A1 |
20180005508 | Allen, Sr. | Jan 2018 | A1 |
20180005509 | Allen, Sr. | Jan 2018 | A1 |
20180055284 | Dacic et al. | Mar 2018 | A1 |
20180082134 | Sivaraman | Mar 2018 | A1 |
20180097923 | Pandurangarao | Apr 2018 | A1 |
20180097928 | Pandurangarao | Apr 2018 | A1 |
20180125296 | Gafford | May 2018 | A1 |
20180283895 | Aikin | Oct 2018 | A1 |
20180297210 | Peterson et al. | Oct 2018 | A1 |
20180324908 | Denker et al. | Nov 2018 | A1 |
20180333002 | Joyce | Nov 2018 | A1 |
20180338351 | Schmeski | Nov 2018 | A1 |
20180342157 | Donnelly et al. | Nov 2018 | A1 |
20190045417 | Logan et al. | Feb 2019 | A1 |
20190053332 | Cheng et al. | Feb 2019 | A1 |
20190132703 | Ramasamy | May 2019 | A1 |
20190266876 | Allen, Sr. | Aug 2019 | A1 |
20190285483 | Cheng | Sep 2019 | A1 |
20190301891 | Rowitch | Oct 2019 | A1 |
20190333360 | Allen, Sr. | Oct 2019 | A1 |
20190385432 | Allen, Sr. | Dec 2019 | A1 |
20200143661 | Allen, Sr. | May 2020 | A1 |
20200357260 | Allen, Sr. | Nov 2020 | A1 |
Number | Date | Country |
---|---|---|
2355805 | Feb 2001 | GB |
2003015621 | Jan 2003 | JP |
170087 | Sep 2001 | WO |
Entry |
---|
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 16/738,170, dated May 14, 2021, 9 pages. |
Brookstone, “Grill Alert Talking Remote Meat Thermometer instructions,” Mar. 18, 2005. |
Weber, “Style Digital Thermometer,” available prior to May 28, 2009, retrieved on May 28, 2010, from [http://store.weber.com//items/WeberStyle/Detail/aspx?pid=1131, 1 page. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 14/595,868, dated Nov. 10, 2016, 8 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 14/595,868, dated Mar. 30, 2017, 5 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 14/595,868, dated Jul. 25, 2017, 5 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” ssued in connection with U.S. Appl. No. 15/218,330, dated Jun. 6, 2018, 8 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 15/218,330, dated Oct. 16, 2018, 7 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 15/218,330, dated Feb. 14, 2019, 9 pages. |
United States Patent and Trademark Office, “Restriction,” issued in connection with U.S. Appl. No. 15/704,406, dated Sep. 5, 2018, 6 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) due,” issued in connection with U.S. Appl. No. 15/704,406, dated Apr. 8, 2019, 14 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 16/504,946, dated Oct. 3, 2019, 9 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 15/704,382, dated Jul. 13, 2018, 17 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 15/704,382, dated Dec. 17, 2018, 20 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 15/704,382, dated Apr. 12, 2019, 10 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 16/509,800, dated Oct. 3, 2019, 6 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 16/509,800, dated Jan. 13, 2020, 15 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 16/509,800, dated May 5, 2020, 10 pages. |
United States Patent and Trademark Office, “Non-Final Office Action” issued in connection with U.S. Appl. No. 16/411,814, dated Sep. 14, 2021, 9 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 16/738,170, dated Jul. 26, 2021, 11 pages. |
United States Patent and Trademark Office, “Non-Final Office Action” issued in connection with U.S. Appl. No. 16/944,300, dated Aug. 26, 2021, 6 pages. |
United States Patent and Trademark Office, “Final Office Action” issued in connection with U.S. Appl. No. 16/411,814, dated Dec. 10, 2021, 8 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 16/944,300, dated Nov. 8, 2021, 9 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due” issued in connection with U.S. Appl. No. 16/411,814, dated Jan. 18, 2022,6 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 12/790,764, dated Mar. 15, 2013, 7 pages. |
United States Patent and Trademark Office, “Final Office Action,” issued in connection with U.S. Appl. No. 12/790,764, dated Apr. 24, 2014, 8 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 12/790,764, dated Oct. 15, 2013, 7 pages. |
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 12/790,764, dated Sep. 3, 2014, 5 pages. |
Number | Date | Country | |
---|---|---|---|
20220223025 A1 | Jul 2022 | US |
Number | Date | Country | |
---|---|---|---|
61213306 | May 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16411814 | May 2019 | US |
Child | 17707704 | US | |
Parent | 15218330 | Jul 2016 | US |
Child | 16411814 | US | |
Parent | 14595868 | Jan 2015 | US |
Child | 15218330 | US | |
Parent | 12790764 | May 2010 | US |
Child | 14595868 | US |