Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are hereby incorporated by reference under 37 CFR 1.57.
The invention is directed to an actively heated drinkware container, and more particularly to an actively heated or cooled infant bottle system.
Existing systems for heating milk in infant bottles suffer from various problems that make them difficult to use or inconvenient for use by parents and caregivers in preparing heated milk to feed an infant. Such problems include lack of portability, and the inability to readily heat the milk for consumption by the infant (e.g., during nighttime feedings, while traveling, etc.), and the inability to maintain the milk in a cooled state before the milk is fed to the baby.
There is a need for an improved infant bottle system (e.g., baby bottle, sippy cup) that does not have the drawbacks of existing systems. In accordance with one aspect of the invention, an improved infant bottle system (e.g., baby bottle, sippy cup) is provided that maintains the contents (e.g., water, milk, breast milk, infant formula, etc.) in the container in a cooled state for an extended period of time (e.g., while traveling or commuting), and that can readily and controllably heat the contents (e.g., water, milk, breast milk, infant formula, etc.) in the container to an appropriate feeding temperature for consumption by the infant.
In accordance with another aspect, a smart infant bottle system is provided that optionally can communicate with mobile electronic devices (e.g., smartphones, tablet computers, laptop computers) to allow easy operation of the infant bottle system and/or collect information associated with the consumption of liquid (e.g., water, milk, breast milk, infant formula, etc.) from the bottle (e.g., time of day of feeding, number of feedings a day, volume of liquid, such as milk, consumed per feeding, etc.). The smart infant bottle system can optionally be programmed to heat (e.g., automatically without user actuation) the liquid (e.g., water, milk, breast milk, infant formula, etc.) at specific time(s) of day (e.g., based on collected data of feeding patterns of infant).
The smart infant bottle system can optionally include a detachable module that includes electronics and one or more power storage elements (e.g., batteries, such as rechargeable batteries), and which can be mechanically coupled to the container to effect an electrical connection between the module and the container to effect communication between electronics in the module and electronics (e.g., one or more sensors) in the container, and effect communication between the one or more power storage elements in the module and one or more heating elements in the container that are operable to heat the liquid (e.g., water, milk, breast milk, infant formula, etc.) in a chamber of the container. Optionally, the module can be detachably coupled to each of a plurality of containers (e.g., to a plurality of infant bottles), thereby allowing use of the module with a plurality of containers. Detaching the module from the container advantageously allows a user to wash the container without risk of damaging the electronics in the module.
In accordance with another aspect, an infant bottle feeding system is provided. The system comprises an infant bottle having a body with a chamber configured to receive a liquid (e.g., water, milk, breast milk, infant formula, etc.) therein. The infant bottle comprises one or more heating elements housed in the body and in thermal communication with the chamber and operable to heat a liquid (e.g., water, milk, breast milk, infant formula, etc.) in the chamber, and one or more sensors in communication with the chamber and operable to sense one or more parameters of the liquid in the chamber. The system also comprises a power base removably attached to a bottom surface of the infant bottle and configured to deliver power to electronics in the infant bottle. The system also comprises a thermal cover configured to fit over the infant bottle and to releasably couple to the power base to completely enclose the infant bottle, the thermal cover configured to insulate the infant bottle and inhibit heat loss of liquid in the chamber. The power base is configured to deliver power to the one or more heating elements and one or more sensors in the infant bottle only when the infant bottle is on the power base, and wherein the infant bottle, thermal cover and power base define a single travel pack unit when coupled together.
In accordance with another aspect, an infant bottle feeding system is provided. The system comprises an electronic base configured to removably support an infant bottle on an upper surface thereof. The electronic base comprises one or more sensors, at least one of the one or more sensors configured to sense a weight of the infant bottle when placed on the electronic base, a transceiver, and circuitry configured to communicate with the one or more sensors and the transceiver. The circuitry is operable to one or more of: record one or both of a start time and start weight of the infant bottle prior to an infant feeding event, record one or both of an end time and end weight of the infant bottle following an infant feeding event, calculate one or both of an elapsed time between the start time and end time and a consumption amount based on a difference between the start weight and end weight, and one or both of store the elapsed time and consumption amount in a memory of the electronic base and wirelessly communicate via the transceiver the elapsed time and consumption amount to one or both of a remote electronic device and a to the cloud-based data storage system for storage and from which data is accessible via a dashboard interface on an electronic device. The system also comprises a thermal cover configured to fit over the infant bottle and to releasably couple to the electronic base to completely enclose the infant bottle between the thermal cover and the electronic base, the thermal cover configured to insulate the infant bottle and inhibit heat loss of liquid in the infant bottle.
In accordance with another aspect, an infant bottle feeding system is provided. The system comprises an infant bottle having a body with a chamber configured to receive a liquid therein. The infant bottle comprises one or more heating elements housed in the body and in thermal communication with the chamber and operable to heat a liquid in the chamber, and one or more sensors in communication with the chamber and operable to sense one or more parameters of the liquid in the chamber. The system also comprises an electronic base removably attached to a bottom surface of the infant bottle and configured to deliver power to electronics in the infant bottle. The system also comprises a thermal cover configured to fit over the infant bottle and to releasably couple to the electronic base to completely enclose the infant bottle, the thermal cover configured to insulate the infant bottle and inhibit heat loss of liquid in the chamber. The electronic base is configured to deliver power to one or both of the one or more heating elements and the one or more sensors in the infant bottle only when the infant bottle is on the electronic base, and wherein the infant bottle, thermal cover and electronic base define a single travel pack unit when coupled together.
Disclosed herein are drinkware container systems with active temperature control (e.g., actively heated drinkware container systems, actively cooled drinkware container systems, actively heated and cooled drinkware container systems). Though the figures and description of the instant application may refer to the drinkware container system in the context of an infant bottle system (e.g., baby bottle, sippy cup), the features disclosed herein for the drinkware container system also apply to (and can be incorporated in) other drinkware (e.g., cups, mugs, travel mugs) and plateware (e.g., bowls, plates, platters, serving dishes, etc.). Also disclosed herein is a power base or smart base (e.g., electronic base) that can be used with the actively heated or cooled drinkware container. As disclosed herein, the power base or smart base (e.g., electronic base) can also be used with conventional drinkware containers (e.g., with conventional infant bottles, sippy cups, etc.) that do not have any electronics or heating/cooling elements in the containers.
Though not shown, a seal (e.g., hermetic seal) is optionally disposed between the module 30 and the vessel 10, for example between the proximal portion of the module 30 that fits over the distal portion 14B (e.g., reduced diameter portion) of the vessel 10. The seal advantageously provides a watertight seal between the vessel 10 and the module 30. In one implementation, the seal is an elastomer seal. In another implementation, the seal includes a heat activated film. In another implementation, the seal includes a laser activated adhesive. In another implementation, the seal includes a pressure activated adhesive.
Optionally, the module 30 is removably attached to the distal end of the vessel 10. Alternatively, the module 30 is fixed (e.g., not readily detachable) from the vessel 10. For example, the module 30 can be adhered to the vessel 10 (e.g., with an adhesive, a weld, a press fit connection, etc.). Though not shown in
The vessel 10 is optionally transparent or translucent (e.g., made of glass, plastic, etc.). Alternatively, the vessel 10 can be opaque. The vessel 10 can define a passage 16 (e.g., open space) between an opening at the proximal end 12 and an opening at the distal end 14. The passage 16 defines at least a portion of the chamber C in the container 100 that holds liquid, as further described below.
With reference to
One or more heating or cooling elements 42 can optionally thermally communicate with (e.g., thermally contact) at least a portion of the circumferential wall 36 and/or the base 40. As shown in
The power base 50 optionally has one or more visual indicators 51 that can indicate one or more operating conditions of the power base 50. For example, the one or more visual indicators 51 can indicate one or more of: attachment of drinkware container 100 to the power base 50, transfer of power to the one or more heating or cooling elements 42, communication with an electronic device (described further below), and temperature of the liquid in the drinkware container (e.g., to indicate the liquid is ready to consume or has not yet reached the desired temperature). For example, the one or more visual indicators 51 can be hidden-til-lit LED lights operable to illuminate in one or more (e.g., a plurality of) colors. For example, the visual indicator 51 can illuminate in a green color when the liquid is at the desired temperature for consumption and red when it has not yet reached the desired consumption temperature. Additionally, the one or more visual indicators 51 can flash in one or more (e.g., a plurality of) frequencies to indicate an operation of the power base 50 (e.g., optionally pairing of the power base 50 with an electronic device to communicate information from the power base 50 to the electronic device and optionally to provide user operating instructions to the power base 50 from the electronic device). Further details on the components and operation of the power base 50 are provided further below.
The drinkware container system 100A includes a nipple N disposed over the vessel 10 and under the lid 20. The module 30 is disposed on top of the power base 50, in a similar manner as described above in connection with the drinkware container 100. The power base 50 can be a smart base, as described further below. Optionally, the bottom surface 32B of the module 30 contacts a top surface 52 of the power base 50. The power base 50 can optionally be wider than the module 30 so as to define a circumferential shoulder 54 outward of the module 30 when the module 30 is disposed on the power base 50. Optionally, the module 30 can mechanically couple to the power base 50 (e.g., via one or more threads, key and slot connection, magnets, etc.). Alternatively, the module 30 can be disposed on the power base 50 but not be mechanically coupled to it. Advantageously, the power base 50 can provide power to the module 30 to, for example, provide power to the one or more heating or cooling elements 42.
The drinkware container system 100A optionally includes a cover 70 that can be disposed over the drinkware container (e.g., the bottle assembly defined by the vessel 10, module 30, optional nipple N, and optional lid 20). The cover 70 can optionally be dome shaped with a closed proximal end 72, an open distal end 74, and a chamber or cavity C between the closed proximal end 72 and open distal end 74 that removably receives the drinkware container 100A. The cover 70 optionally encloses at least a portion of the drinkware container 100A. In one implementation, the cover 70 encloses the entire drinkware container 100A. The cover 70 is optionally defined by a wall 75 having an inner surface 76 and an outer surface 78, the wall 75 having a width W between the inner and outer surfaces 76, 78. The width W can optionally range between about 5 mm and about 10 mm, optionally about 7 mm. However, the wall 75 can have other suitable widths W.
Optionally, the cover 70 is sized so that the inner surface 76 is adjacent (e.g., in contact with) at least a portion of an outer surface of the drinkware container 100A (e.g., at least a portion of an outer surface of the vessel 10 and/or the module 30, and or the lid 20). In one implementation, one or both of the cover 70 (e.g., the proximal end 72 of the cover 70) and the lid 20 can optionally have a pressure relief valve incorporated therein to allow pressure build up in the drinkware container 100 (e.g., in the liquid in the chamber C of the drinkware container 100) to be released. In another implementation, the cover 70 is sized so as to define an annular gap between the inner surface 76 of the cover and at least a portion of the outer surface of the drinkware container (e.g., at least a portion of an outer surface of the vessel 10 and/or the module 30 and/or the lid 20). In one implementation, the cover 70 optionally includes a thermally insulative material with low thermal conductivity properties between the inner surface 76 and the outer surface 78, thereby allowing the liquid in the drinkware container to retain its temperature for a prolonged period of time (e.g., 5 hours, 6 hours, 8 hours, 10 hours). In another implementation, the cover 70 has an gap or cavity defined between the inner surface 76 and the outer surface 78, so that the inner surface 76 is insulated relative to the outer surface 78. Optionally, the gap or cavity G is filled with air. In another implementation, the gap G can be under vacuum.
Optionally, the cover 70 can mechanically couple to the power base 50, allowing the cover 70 and power base 50 to be portable as a single unit (e.g., with the power base 50 attached to the cover 70 while in transit), and defining a portable travel pack with the baby bottle assembly (e.g., the drinkware container 100, a conventional infant bottle, etc.) under the cover 70. For example, the distal end 74 of the cover 70 can couple with the shoulder 54 of the power base 50. In one implementation, the cover 70 can couple with the power base 50 via a threaded connection. In another implementation, the cover 70 can couple with the power base 50 via a key-and-slot mechanism. In another implementation, the cover 70 can couple with the power base 50 via one or more magnets, such as one or more electromagnets as further described below. In another implementation, the cover 70 can couple with the power base 50 via a press-fit connection. As shown in
As shown in
In one implementation, the cover 70″ can be placed in a cooler, refrigerator or freezer to charge (e.g., cool) the PCM 130″. A user can then take the cover 70″ from the cooler, refrigerator or freezer and dispose it over a drinkware container (e.g., infant feeding bottle), where the cover 70″ will maintain the drinkware container in a cooled state due to the PCM 130″ (e.g., the PCM 130″ will absorb heat from the drinkware container to thereby cool the drinkware container). Optionally, the cover 70″ can be attached to the power base 50 so that the drinkware container (e.g., infant feeding bottle) is disposed between the cover 70″ and the power base 50, as shown in
In one implementation, the inner surface 76″, outer surface 78″, and intermediate wall 79″ of the cover 70″ are made of the same material (e.g., a metal, such as stainless steel; a plastic material, a ceramic coated metal material). In another implementation, the inner surface 76″ (optionally along with the intermediate wall 79″) is made of a different material (e.g., stainless steel) than the outer surface 78″ (e.g., plastic, ceramic, ceramic covered metal).
In one implementation, the cover 70″ can maintain the drinkware container (e.g., infant feeding bottle) disposed in a chamber of the cover 70″, and/or the liquid in the drinkware container at a cooled temperature (e.g., 40 F, 45 F, 50 F, 55 F, etc.) for an extended period of time (e.g., 8 hours or less, 6 hours or less, 4 hours or less, 2 hours or less, about 1 hour, about 30 minutes, etc.).
The unit 300 has one or more first heat sinks (e.g., cold side heat sinks) 370 disposed in the body 305, one or more second heat sinks (e.g., hot side heat sinks) 350 disposed in the body 305, and one or more thermoelectric elements (TECs) (e.g., Peltier elements) 326 in thermal communication (e.g., direct contact) with, and interposed between, the one of more first heat sinks 370 and one or more second heat sinks 350. The unit 300 also has one or more fans 380 in fluid communication with the one or more first heat sinks 370. In the illustrated embodiment, the one or more fans 380 are disposed within (e.g., integrated in between) a first portion 372 and a second portion 374 of the first heat sink 370 (e.g., integrated into a center portion of the first heat sink 370). However, the one or more fans 380 can be located elsewhere in the body 305 relative to the one or more first heat sinks 370.
In operation, the one or more TECs 326 are operated to draw heat from the one or more first heat sinks 370 and to transfer heat to the one or more second heat sinks 350 to reduce the temperature (e.g., cool) the one or more first heat sinks 370. The one or more fans 380 are operated to flow air past one or more surfaces (e.g., fins) of the one or more first heat sinks 370, thereby cooling said air. In one implementation, the one or more first heat sinks 370 are cooled to a temperature of about 10 F-50 F and cools the air that flows over it to a temperature of about 10 F-50 F. The cooled air is directed through the one or more openings 320 into the chamber C2″ of the cover 70″, where it cools the inner surface 76″. The cooled air also charges the PCM 130″ (e.g., causing the PCM 130″ to transition from one state to another, such as from liquid to solid), allowing the PCM 130″ to absorb heat once a heated liquid or object (e.g., drinkware container, such as infant feeding bottle) is disposed in the chamber C2″ of the cover 70″. The cooled air can exit the chamber C2″ via one or more openings (not shown) in the docking portion 310 and exit the body 305 via one or more of the vent openings 340.
In some implementations, the cooling unit 300 is a standalone unit that is separate from (e.g., not integrated into) a beverage preparation and/or dispensing machine (e.g., infant formula preparation and/or dispensing machine). In other implementations the cooling unit 300 are optionally incorporated into (e.g., integral with, a part of, coupled to, removably coupled to) a beverage dispending machine (e.g., an infant formula preparation and/or dispensing machine). Optionally, the electronics in the beverage dispensing machine can control the operation of one or more components of the cooling unit 300, such as providing power to and/or operating the one or more thermoelectric modules 326 (e.g., turning them on or off or adjusting power to each), providing power to and/or operating the one or more fans 380 (e.g., turning them on or off or adjusting power to each), providing power to and/or operating the dispensing unit, such as turning it on or off.
The drinkware container system 100″ optionally includes a nipple N. The vessel 10 optionally includes one or more sensors 80. Though
The one or more electrical contacts 33 contact one or more electrical contacts 53 on the top surface 52 of a power base 50C (see
Optionally, one or more sensors in the drinkware container 100C can transmit information (e.g., sensed temperature data, sensed liquid level data) to circuitry in the power base 50C via one or more of the electrical contacts 33A, 33B. Optionally, the power base 50C can calculate the amount and/or weight of the liquid in the drinkware container 100C based at least in part on the transmitted information (e.g., based on the sensed liquid level data).
Optionally, the module 30 has a button at the center of the bottom surface 32B and coaxial with the electrical contact rings 33A, 33B. The button can be operable to effect one or more operations for the drinkware container 100C, such as to begin a heating operation by the one or more heating elements 42 in the drinkware container 100C to heat a liquid therein. In another implementation, the button is excluded and the operation of the drinkware container 100C is effected via the power base 50C when the drinkware container 100C is disposed thereon, as further discussed below. In another implementation, operation of the drinkware container 100C is alternatively (or additionally) effected via an electronic device (e.g., mobile electronic device such as a smartphone, tablet computer, etc.) that communicates a signal wirelessly to the power base 50C and/or the drinkware container 100C, as further discussed below.
In another implementation, the electrical contacts 33, 53 are excluded and communication between the power base 50C and the drinkware container 100C is done wirelessly (e.g., using inductive coupling to transmit power from the power base 50C to the drinkware container 100C to power the one or more heating or cooling elements 42, sensors, etc. in the drinkware container). Further details on the components and operation of the power base 50C are provided below.
In another implementation, the electrical contacts 33′, 53′ are excluded and communication between the power base 50C′ and the drinkware container 100C′ is done wirelessly (e.g., using inductive coupling to transmit power from the power base 50C′ to the drinkware container 100C to power the one or more heating elements 42, sensors, etc. in the drinkware container). Further details of the components and operation of the power base 50C′ are provided below.
The drinkware container system 100D has a cover structure 70′ similar to the cover 70. The cover structure 70′ includes a top or proximal cover portion 70A and a bottom or distal cover portion 70B. The bottom cover portion 70B has a cavity defined by a circumferential wall 75B sized to receive at least a portion of the drinkware container (e.g., receive the vessel 10 and module 30) therein. Optionally, the circumferential wall 75B defines a cavity sized so that an inner surface of the wall 75B contact at least a portion of an outer surface of the drinkware container (e.g., contacts at least a portion of an outer surface of the vessel 10 and/or module 30). Optionally, a proximal end of the vessel 10 (e.g., the reduced diameter portion 12B) protrudes from a proximal end of the bottom cover portion 70B. The wall 75B has a width W′, which can optionally be similar to the width W of the wall 75 in
The bottom cover portion 70B optionally includes a power base 50D incorporated (e.g., embedded) therein, so that the power base 50D is not separable from the bottom cover portion 70B. The power base 50D can optionally be a smart base, as further described below. The power base 50D operates in a similar manner as the power base 50 to provide power to the one or more heating or cooling elements 42 of the drinkware container. In another implementation, at least a portion of the power base 50D can be removably disposed in a distal end of the bottom cover portion 70B, such that the power base 50D can be detached or removed from the bottom cover portion 70B. Additional details on the operation of the power base 50D are provided further below.
In use, the top cover portion 70A can be disposed over the lid 20 so that a distal end of the top cover portion 70A is proximal to (e.g., adjacent to, in contact with) a proximal end of the lower cover portion 70B, to thereby define a travel pack TP for the drinkware container system 100D, allowing the user to maintain the liquid in the drinkware container thermally insulated for a prolonged period of time (e.g., while traveling, while commuting). The top cover portion 70A can be removed from over the lid 20 when the liquid in the drinkware container is ready to be consumed.
As previously discussed, the drinkware container 100 (e.g., module 30 of the drinkware container 100) has one or more heating or cooling elements 42, which optionally includes a heating or cooling element 42A disposed about at least a portion of the circumference of the chamber C in the container 100. The one or more heating or cooling elements 42 optionally includes a heating or cooling element 42B disposed adjacent a base of the chamber C. The drinkware container 100 optionally has one or more sensors 80 operable to sense one or more parameters (e.g., temperature, level, volume) of liquid in the chamber C.
As shown in
With continued reference to
The power base 50 can optionally include a power button PS1 on or proximate the bottom surface 58 of the power base 50. Additionally or alternatively, the power base 50 can optionally include a power button PS2 on or proximate a top surface 52 of the power base 50. The power base 50 can optionally be turned on or off via one or both of the power button PS1, PS2.
With continued reference to
Proximity Sensor
The power base 50 optionally includes one or more proximity sensors 57 (e.g., an inductive proximity sensor, a capacitive proximity sensor, a magnetic proximity sensor) that communicate with the circuitry 56. In one implementation, the one or more proximity sensors 57 can be one or more Hall effect sensors. The drinkware container 100 (e.g., the module 30 of the drinkware container 100) can optionally have one or more objects 23 (e.g., metal object, magnet, etc.) that can be detected by the one or more proximity sensors 57 when the drinkware container 100 is adjacent (e.g., disposed upon) the power base 50. Where the proximity sensor 57 is a Hall effect sensor, the one or more objects 23 are optionally one or more magnets.
In operation, the one or more proximity sensors 57 can communicate a signal to the circuitry 56 upon sensing the one or more objects 23 (e.g., when the power base 50 is disposed on the power base 50), and in response to such a signal the circuitry 56 (e.g., a switch of the circuitry 56) can allow communication of power from the one or more power storage elements 55 to the one or more electrical contacts 53A, 53B, which can then be transferred to the one or more electrical contacts 33A, 33B in the drinkware container 100, as further discussed below. When the drinkware container 100 is not proximal to (e.g., not adjacent to, not disposed upon) the power base 50, the one or more proximity sensors 57 will not communicate a proximity signal to the circuitry 56, and the circuitry 56 in response can disallow communication of power from the one or more power storage elements 55 to the one or more electrical contacts 53A, 53B (e.g., the circuitry 56 can prevent communication of power from the power storage elements 55 to the electrical contacts 53A, 53B unless it received the proximity signal from the sensor 57, such as unless the drinkware container 100 is placed on the power base 50). Advantageously, such an arrangement would inhibit (e.g., prevent) a user from receiving a shock from touching the electrical contacts 53A, 53B of the power base 50.
Electromagnetic Coupling
The power base 50 optionally includes one or more electromagnets 59 that communicate with the circuitry 56. One or both of the drinkware container 100 (e.g., module 30 of the drinkware container 100) and the cover 70 optionally includes one or more magnets 24 (e.g., permanent magnets). In one implementation, only the cover 70 includes the one or more magnets 24 and the drinkware container 100 is retained between the cover 70 and the power base 50 by an attraction force between the electromagnets 59 and the magnets 24 in the cover 70.
The circuitry 56 can operate the one or more electromagnets 59 in the power base 50 to have an opposite polarity as the magnets 24, thereby allowing the coupling of the power base 50 to one or both of the drinkware container 100 (e.g., module 30 of the drinkware container 100) and the cover 70, for example, to retain them in a coupled state. The circuitry 56 can also operate the one or more electromagnets 59 in the power base 50 to have the same polarity as the magnets 24, thereby allowing the decoupling of the power base 50 from one or both of the drinkware container 100 (e.g., module 30 of the drinkware container 100) and the cover 70. For example, the circuitry 56 can operate the one or more electromagnets 59 to have the power base 50 decouple from one or both of the drinkware container 100 (e.g., module 30 of the drinkware container 100) and the cover 70 in response to a user instruction (e.g., via a user interface on the power base 50, or via a remote instruction provided to the power base 50 by the user via a remote electronic device or a mobile electronic device).
In use, the circuitry 56 can optionally actuate (e.g., upon receipt of user instructions via a user interface on the power base 50 or wirelessly via a remote electronic device such as a mobile electronic device) the one or more electromagnets 59 to couple the power base 50 to one or both of the drinkware container 100 (e.g., module 30 of the drinkware container 100) and the cover 70. In another implementation, the circuitry 56 can automatically actuate the one or more electromagnets 59 to couple the power base 50 to one or both of the drinkware container 100 (e.g., module 30 of the drinkware container 100) and the cover 70 upon placement of the drinkware container 100 and/or cover 70 proximal to (e.g., adjacent to, in contact with) the power base 50.
Such coupling could allow the power base 50 and drinkware container 100 and/or cover 70 to form a single travel unit, making it easy to carry while traveling. Additionally, such coupling could facilitate the efficient heating of liquid in the drinkware container 100 by maintaining the drinkware container 100 and/or cover 70 attached to the power base 50 during the heating process. Once the heating process was completed, circuitry 56 in the power base 50 can actuate the one or more electromagnets 59 to decouple the drinkware container 100 and/or cover 70 from the power base 50, thereby allowing the consumption of the liquid in the drinkware container 100 without having the electronics in the power base 50 attached to the drinkware container 100 during said consumption. In one implementation, the circuitry 56 can actuate the one or more electromagnets 59 to decouple the drinkware container 100 and/or cover 70 from the power base 50 upon receipt of a command from the user (e.g., via a user interface of the power base 50, such as optionally via a gesture; wirelessly via an electronic device, such as a mobile electronic device, that optionally communicates with the circuitry 56, etc.), such as a command that the contents of the drinkware container 100 are ready for consumption (e.g., a “feeding” command). In another implementation, the circuitry 56 can actuate the one or more electromagnets 59 to decouple the drinkware container 100 and/or cover 70 from the power base 50 upon receipt of a signal from the one or more sensors 80 (as further described below) that the contents (e.g. liquid) in the chamber C are at a predetermined temperature for consumption (or within a predetermined temperature range for consumption). Said predetermined temperature or temperature range can optionally be a user selected temperature or temperature range, or can be a temperature value or temperature range stored in a memory of the drinkware container 100 (e.g., module 30 of the drinkware container 100) or memory of the power base 50.
Optionally, the circuitry 56 allows or facilitates the transfer of power and/or to the drinkware container 100, for example from the one or more batteries 55 to the one or more heating or cooling elements 42 (e.g., via the one or more electrical contacts 33A, 33B, 53A, 53B), when at least one of the one or more sensors 80 (e.g., a liquid level sensor, a capacitance sensor, etc.) in the drinkware container 100 or weight sensors 81 in the electronic (e.g., power, smart) base 50 indicates that there is liquid in the chamber C (e.g., above a predetermined liquid level or above a predetermined amount or weight).
Optionally, the circuitry 56 can inhibit (e.g. prevent) transfer of power and/or automatically terminates transfer of power to the drinkware container 100, for example from the one or more batteries 55 to the one or more heating or cooling elements 42 (e.g., via the one or more electrical contacts 33A, 33B, 53A, 53B), when at least one of the one or more sensors 80 (e.g., a liquid level sensor, a capacitance sensor, etc.) in the drinkware container 100 or weight sensors 81 in the electronic (e.g., power, smart) base 50 indicates that the chamber C is empty or near empty (e.g., below a predetermined liquid level).
As shown in
The power base 50′ can optionally have one or more electrical contacts 53D that communicate with the circuitry 56. Optionally, when the cover 70′ is disposed adjacent the power base 50′, the one or more electrical contacts 53D of the power base 50′ can contact the one or more electrical contacts 73 of the cover 70′. Optionally, the control circuitry 56 can provide power (e.g., from the one or more power storage elements or batteries 55) to the one or more thermoelectric elements 71 via the one or more electrical contacts 53D, 73 to operate the one or more thermoelectric elements 71. In operation, the one or more thermoelectric elements 71 draw heat from the drinkware container 100 via the cold side 71B and transfer it to the hot side 71A, thereby actively cooling the drinkware container 100 and the contents (e.g., water, milk, breast milk, baby formula, etc.) in the container 100 (e.g., in the chamber C of the container 100). Optionally, the cover 70′ can have one or more heat sinks (e.g., fins) to dissipate heat from the hot side 71A to the environment. Advantageously, operation of the one or more thermoelectric elements 71 as described above can allow the contents of the drinkware container 100 to be selectively chilled until ready for use (e.g., chilled while in transit, during travel, etc.). Operation (e.g., turning on) of the one or more thermoelectric elements 71 can optionally be effected automatically by the circuitry 56 upon coupling of the cover 70′ to the power base 50′. Alternatively, operation of the one or more thermoelectric elements 71 can effected upon receipt of instructions by the circuitry 56 from a user (e.g., via a user interface on the power base 50′ or wirelessly via an electronic device, such as a mobile electronic device, that sends instructions to the power base 50′, as further described below).
With continued reference to
With reference to
The power base 50 optionally includes one or more antennae 63 that communicate with a transceiver 62 and optionally implement a wireless telecommunication standard (e.g., WiFi 802.11, 3G, BLUETOOTH®). The power base 50 can have a printed circuit board (PCB) 56 that optionally has a processor or microcontroller unit (MCU) 60 and optionally has a computer readable medium (e.g., memory) 61 mounted thereon. Optionally, the optional transceiver 62 and optional antennae 63 can also be mounted on the PCB 56. The power base 50 optionally includes a user interface 64 that communicates with the processor 60. The user interface 64 can optionally include one or more of: a digital screen, a dot matrix display, a visual indicator, an indicator light, a capacitive touch sensor, a gesture sensor, etc. The power base 50 can also include one or more timers 69 that communicate time information to the MCU 60.
The transceiver 62 can generate wireless (e.g., RF) signals for transmission via the antenna 63. Furthermore, the transceiver 62 can receive incoming wireless (e.g., RF) signals from the antenna 63. It will be understood that various functionalities associated with transmitting and receiving of wireless (e.g., RF) signals can be achieved by one or more components that are collectively represented in
In
In
The processor 60 can optionally facilitate the implementation of various processes disclosed herein on the power base 50. The processor 60 can be a general purpose computer, special purpose computer, or other programmable data processing apparatus. In certain implementations, the power base 50 optionally includes a computer-readable memory 61, which can include computer program instructions (e.g., power delivery algorithms, temperature setpoints at which to operate the one or more heating or cooling elements 42) that may be provided to and executed by the processor 60. The one or more power storage elements 55 (e.g., batteries) can optionally be any suitable battery for use in the power base 50, including, for example, a lithium-ion battery.
Communication with Cloud
With continued reference to
In another variation, the graphical user interface (GUI) screen of the remote electronic device 150 can optionally provide a dashboard display of one or more parameters associated with the use of the drinkware container 100. For example, the GUI can provide an indication of power supply left in the one or more batteries 55, such as % of life left or time remaining before battery power drains completely, temperature in chamber C, etc., for example while the drinkware container 100 is in transit (e.g., during a commute) and before the one or more heating or cooling elements 42 are actuated to heat the contents in the chamber C of the drinkware container 100.
Optionally, the power base 50 can communicate information (e.g., one or more of a temperature of the contents in the chamber C, a start time of a feeding event, an end time of a feeding event, a duration of a feeding event, the number of feeding events per day, an amount, for example volume, consumed during a feeding event) to the cloud CL on a periodic basis (e.g., every hour, one a day, on a continuous basis in real time, etc.). For example, the start time of a feeding event (START_TIME) can substantially coincide with the time the drinkware container 100 is removed from the power base 50 after the alert has been sent to the user (e.g., wirelessly sent to the remote electronic device 150) that the desired temperature of the contents in the chamber C of the drinkware container 100 has been reached. The end time of a feeding event (END_TIME) can substantially coincide with the time the drinkware container 100 is placed back on the power base 50 after a START_TIME has been logged by the power base 150 (e.g., by the MCU 60). The duration of the feeding event (DURATION_TIME) can be calculated (e.g., by the MCU 60) based on the difference between the END_TIME and START_TIME logged by the power base 150 (e.g., by the MCU 60). The number of feedings (FEEDING_COUNT) can be calculated (e.g., by the MCU 60) based on the number of START_TIMES logged and/or number of END_TIMES logged (e.g., by the MCU 150) in a twenty-four hour period. The amount (e.g., volume) consumed in a feeding event (FEEDING_AMOUNT) can be calculated (e.g., by the MCU 60) based on the difference in the measured weight (from the weight sensor 81) of the drinkware container 100 at the logged START_TIME and the measured weight (from the weight sensor 81) at the logged END_TIME for a feeding event.
Once stored on the cloud CL, such information can be accessed via one or more remote electronic devices 150 (e.g., via a dashboard on a smart phone, tablet computer, laptop computer, desktop computer, etc.), advantageously allowing, for example, a user (e.g., parent, caregiver) to track the number of feeding events and/or timing of feeding events and/or amounts consumed (e.g., of milk, breast milk, infant formula, water, etc.) by an infant. Optionally, such information (e.g., one or more of start time, end time, duration and amount, such as volume, of feedings) can be communicated (e.g., via a push notification) from the cloud CL to the remote electronic device 150. Such a dashboard can allow a user (e.g., parent, guardian) to view and compare (e.g., in bar chart form, pie chart form, etc.) infant feeding events (e.g., duration, start time and stop time, amount (volume) consumed) during a period selected by the user (e.g., day to day, over a week, week-to-week, over a month, etc.). Additionally or alternatively, the power base or smart base 50 can store in a memory 61 such information, which can be accessed from the power base 50 by the user via a wired or wireless connection (e.g., via the remote electronic device 150).
Optionally, the power base or smart base 50 can provide one or more alerts (e.g., visual alerts, aural alerts) to a user via one or both of the user interface 64 on the power base or smart base 50 and the remote electronic device 150 (e.g., via a GUI screen of an app associated with the power base 50 and/or drinkware container 100). Such alerts and indicate to the user one or more of the following: a) instructions to place the empty drinkware container 100 on the power or smart base 50 to record (with the weight sensor 81) an initial weight (EMPTY) of the drinkware container 100 without liquid, b) instructions to place drinkware container 100 (once filled with liquid) on the power base 50 to record (with the weight sensor 81) initial weigh-in and/or to start a heating process of the contents in the chamber C, c) instructions to remove the drinkware container 100 from the power base 50 once the temperature setpoint for the contents in the chamber C is reached, recording a feeding start time once the drinkware container 100 is removed, d) instructions to place the drinkware container 100 on the power base 50 to record (with the weight sensor 81) an end weigh-in after drinkware container 100 was removed at step c), e) recording a feeding end time once the drinkware container 100 is replaced on the power base 50, and f) battery power available.
The smart base 50″ differs from the power base 50 in
The smart base 50′″ differs from the power base 50′ in
The smart base 50″, 50′″, 50G, 50H in
The smart base 50G differs from the power base 50 in
The smart base 50H differs from the power base 50G in
Communication of Sensor Signals
With reference to
The power base 50 optionally includes an RFID reader 67. Optionally, the RFID reader 67 communicates with one or both of the circuitry 56 (e.g., with the processor 60) and the one or more power storage elements 55. The RFID reader 67 can read (e.g., wirelessly) the signals or sensed data on the RFID tag 25 (e.g., sensed data communicated by the one or more sensors 80), for example when the drinkware container 100 (e.g., when the module 30 of the drinkware container 100) is proximate to (e.g., disposed upon, adjacent to, in contact with or supported on) the power base 50, and can optionally communicate the signals or sensed data to the processor 60, where the processor 60 can optionally process the data. Optionally, where the power base 50 includes a transceiver 62, the sensed data can be communicated from the power base 50 to a remote electronic device or mobile electronic device, such as a smartphone or tablet computer.
Optionally, the RFID tag 25 is a passive tag and is powered by the RFID reader 67. That is, there is no power source in the drinkware container 100 (e.g., in the module 30 of the drinkware container 100) and communication of the sensed data or signals from the one or more sensors 80 via the RFID tag 25 is powered by the one or more power storage elements 55 in the power base 50, for example when the drinkware container 100 (e.g., when the module 30 of the drinkware container 100) is proximate to (e.g., disposed upon, adjacent to, in contact with or supported on) the power base 50.
With reference to
The power base 50 optionally includes a receiver (e.g., radiofrequency receiver) 62B. In one implementation, the receiver 62B can be part of the transceiver 62; in another implementation the receiver 62B can be a separate component than the transceiver 62. Optionally, the receiver 62B communicates with the circuitry 56 (e.g., with the processor 60 of the circuitry 56). The antenna 22B can optionally be a short range antenna, and the receiver 62B can be a short range RF receiver.
The receiver 62B can receive (e.g., wirelessly) the signals or sensed data (e.g., sensed data communicated by the one or more sensors 80) via the antenna 22B, for example when the drinkware container 100 (e.g., when the module 30 of the drinkware container 100) is proximate to (e.g., disposed upon, adjacent to, in contact with or supported on) the power base 50, and can optionally communicate the signals or sensed data to the processor 60, where the processor 60 can optionally process the data. Optionally, where the power base 50 includes a transceiver 62, the sensed data can be communicated from the power base 50 to a remote electronic device or mobile electronic device, such as a smartphone or tablet computer.
Optionally, the antenna 22B, circuitry 22 and one or more sensors 80 are powered by the power base 50. That is, there is no power source in the drinkware container 100 (e.g., in the module 30 of the drinkware container 100) and communication of the sensed data or signals from the one or more sensors 80 via the antenna 22B is powered by the one or more power storage elements 55 in the power base 50, for example when the drinkware container 100 (e.g., when the module 30 of the drinkware container 100) is proximate to (e.g., disposed upon, adjacent to, in contact with or supported on) the power base 50.
With reference to
In one implementation the drinkware container 100 (e.g., the module 30 of the drinkware container 100) optionally includes circuitry 22 with a processor or microcontroller unit 22A. As previously discussed, the one or more sensors 80 can communicate with (e.g., communicate signals corresponding to sensed data to) the circuitry 22, which are optionally processed by the processor 22A. Additionally, the drinkware container 100 (e.g., the module 30 of the drinkware container 100) optionally includes one or more light emitters 22C (e.g., infrared light emitter, ultraviolet light emitter, light emitting diodes (LEDs)) in communication with the circuitry 22 (e.g., in communication with the processor 22A of the circuitry 22). Optionally, the processor 22A can process the signals from the one or more sensors 80 and operate the one or more light emitters 22C (e.g., at one or more frequencies) to communicate said signals as one or more light signals. For example, the processor 22A can process the signals from the one or more sensors 80 into on/off instructions for the one or more light emitters 22C at one or more frequencies (e.g., to convert the signals into binary code). The one or more light emitters 22C can then be operated (e.g., flash on and off) according to the on/off instructions from the processor 22A.
The power base 50 optionally includes one or more receivers 68 (e.g., having a photodiode, image sensor, etc.) that can receive (e.g., wirelessly) the one or more light signals from the one or more light emitters 22C, for example when the drinkware container 100 (e.g., when the module 30 of the drinkware container 100) is proximate to (e.g., disposed upon, adjacent to, in contact with or supported on) the power base 50. The receiver 68 optionally interprets the received light signal (e.g., the binary code provided by the light signals) and communicates the received information to the circuitry 56 (e.g., to the processor 60 of the circuitry 56). In another implementation, the receiver 68 communicates the light signal from to the circuitry 56 without interpreting the signal. The circuitry 56 (e.g., the processor 60 of the circuitry) optionally processes the received light signal (e.g., interprets the binary code communicated by the signal). Accordingly, the receiver 68 can receive (wirelessly) the signals or sensed data (e.g., sensed data from the one or more sensors 80) via the one or more light emitters 22C.
Optionally, where the power base 50 includes a transceiver 62, the sensed data can be communicated from the power base 50 (via the transceiver 62) to a remote electronic device or mobile electronic device, such as a smartphone or tablet computer.
Optionally, the circuitry 22, one or more light emitters 22C and one or more sensors 80 are powered by the power base 50. That is, there is no power source in the drinkware container 100 (e.g., in the module 30 of the drinkware container 100) and communication of the sensed data or signals from the one or more sensors 80 via the one or more light emitters 22C is powered by the one or more power storage elements 55 in the power base 50, for example when the drinkware container 100 (e.g., when the module 30 of the drinkware container 100) is proximate to (e.g., disposed upon, adjacent to, in contact with or supported on) the power base 50.
With reference to
In one implementation the drinkware container 100 (e.g., the module 30 of the drinkware container 100) optionally includes circuitry 22 with a processor or microcontroller unit 22A. As previously discussed, the one or more sensors 80 can communicate with (e.g., communicate signals corresponding to sensed data to) the circuitry 22, which are optionally processed by the processor 22A. Additionally, the drinkware container 100 (e.g., the module 30 of the drinkware container 100) optionally includes one or more electrical contacts 33A, 33B, 33C in communication with the circuitry 22 (e.g., in communication with the processor 22A of the circuitry 22). The processor 22A can optionally process the signals from the one or more sensors 80. For example, the processor 22A can optionally convert the signals from the one or more sensors 80 into one or more pulsed signals (e.g., on/off signal) at one or more frequencies (e.g., to convert the signals into binary code) and communicate pulsed signal to at least one of the one or more electrical contacts 33A, 33B, 33C.
At least one of one or more electrical contacts 53A, 53B, 53C of the power base 50 can receive the one or more pulsed signals from said at least one of the one or more electrical contacts 33A, 33B, 33C, for example when the drinkware container 100 (e.g., when the module 30 of the drinkware container 100) is proximate to (e.g., disposed upon, adjacent to, in contact with or supported on) the power base 50. The one or more electrical contacts 53A, 53B, 53C can communicate with the circuitry 56 (e.g., with a processor 60 of the circuitry). For example, the processor 60 can optionally process the received signals from the one or more electrical contacts 53A, 53B, 53C (e.g., to interpret the binary code in the received pulsed signal).
Optionally, where the power base 50 includes a transceiver 62, the sensed data can be communicated from the power base 50 to a remote electronic device or mobile electronic device, such as a smartphone or tablet computer.
Optionally, the circuitry 22, one or more electrical contacts 33A, 33B, 33C and one or more sensors 80 are powered by the power base 50. That is, there is no power source in the drinkware container 100 (e.g., in the module 30 of the drinkware container 100) and communication of the sensed data or signals from the one or more sensors 80 via the one or more light electrical contacts 33A, 33B, 33C is powered by the one or more power storage elements 55 in the power base 50, for example when the drinkware container 100 (e.g., when the module 30 of the drinkware container 100) is proximate to (e.g., disposed upon, adjacent to, in contact with or supported on) the power base 50.
In another implementation, each of the drinkware container 100 and the power base 50 can instead have only two electrical contacts (e.g., 33A, 33B; 53A, 53B), which are used to transmit power from the power base 50 to the drinkware container 100 as well as to communicate signals or sensed data from the one or more sensors 80 to the power base 50. The circuitry 22 (e.g., the processor 22A of the circuitry) can optionally convert the signals from the one or more sensors 80 into a pulsed signal and communicate the pulsed signal along with the power signal through the electrical contacts 33A, 33B to the contacts 53A, 53B, which in turn communicate the pulsed signal along with the power signal to the circuitry 56 (e.g., to the processor 60 of the circuitry 56). The circuitry 56 (e.g., the processor 60) can optionally separate the pulsed signal from the power signal and process it (e.g., interpret the binary code in the received pulsed signal).
With reference to
With reference to
With reference to
Method of Operation
In one implementation, there is no power source in the drinkware container 100 (e.g., in the module 30 of the drinkware container 100). Instead, power is transmitted to the drinkware container 100 (e.g., to the circuitry 22, one or more heating elements 42, one or more sensors 80) from the power base 50, for example when the drinkware container 100 (e.g., when the module 30 of the drinkware container 100) is proximate to (e.g., disposed upon, adjacent to, in contact with or supported on) the power base 50. Accordingly, the electronics in the drinkware container 100 (e.g., circuitry 22, one or more sensors 80, one or more heating elements 42) are not operable while the drinkware container 100 is detached from the power base 50, such as during consumption of the contents (e.g. liquid) in the drinkware container 100. For example, where the drinkware container 100 is an infant bottle (or sippy cup), electronics in the drinkware container 100 are advantageously not operable while the child consumes the liquid in the infant bottle (or sippy cup). Optionally, the circuitry 22 in the drinkware container 100 can require low power (e.g., a low power processor 22A, low power antenna 22B, 25B).
In use, a user can pour liquid (e.g., cold milk) in the chamber C of the drinkware container 100 and cover the container 100 with the cover 70 and couple the container 100 and/or cover 70 (e.g., via a threaded connection, via magnets such as electromagnets) to the power base 50. The cover 70 advantageously thermally insulates the drinkware container 100, allowing the liquid in the chamber C to substantially retain its cooled temperature for an extended period of time (e.g., 8 hours or less, 6 hours or less, 4 hours or less, 2 hours or less).
The user can actuate the heating of the contents in the chamber C by providing a “start heating” instruction to the power base 50. For example, the user can actuate (e.g., touch, press, push, gesture at) a user interface (such as user interface 64) of the power base 50 to deliver power to the one or more heating elements 42 in the drinkware container 100 (e.g., via the electrical contacts 53A, 53B in the power base 50 and electrical contacts 33A, 33B in the module 30). Further, the user can optionally select a temperature setpoint or temperature range to which the contents of the chamber C are to be heated via the user interface of the power base 50. Where the power base 50 includes a transceiver 62, the user can additionally (or alternatively) provide the “start heating” instruction and user selected temperature setpoint or temperature range to the power base 50 wirelessly (e.g., via a remote electronic device 150).
The remote electronic device 150 can optionally be a mobile electronic device, such as smartphone or tablet computer, which can communicate with the power base 50 via, for example WiFi or BLUETOOTH®. The remote electronic device 150 can optionally be a voice activated intelligent personal assistant (e.g., ALEXA™ by AMAZON®) device that can communicate with the power base 50, for example via WiFi. Accordingly, in an additional or alternative implementation, the operation of the power base 50, and therefore the operation of the heating or cooling of the contents of the drinkware container 100, can be effected via wireless instructions received from the remote electronic device 150 (e.g., received via voice activation of an intelligent personal assistant that communicates with the power base 50).
In an additional or alternative implementation, the temperature setpoint or temperature range is not communicated by the use but is instead preset and stored in the power base 50 (e.g., in the computer readable medium 61), for example during manufacturing. In this implementation, the power base 50 operates the delivery of power to the drinkware container 100 to operate the one or more heating elements 42 to achieve said preset temperature during the heating process.
Advantageously, the cover 70 remains over the drinkware container 100 during the heating operation, making the heating process more efficient as the cover 70 inhibits loss of heat through the walls of the vessel 10, module 30 or lid 200. The one or more sensors 80 sense one or more parameters of the contents in the chamber C. For example, the one or more sensors 80 sense temperature in the chamber C, liquid level in the chamber C, etc. and communicate the sensed information to the power base 50 in the manners disclosed above. Circuitry 56 in the power base 50 optionally determines when the contents in the chamber C have reached the temperature setpoint, for example via the sensed data communicated by the one or more sensors 80 to the power base 50. In one optional implementation, the circuitry 56 automatically ends the heating process (e.g., by disallowing transfer of power from the power base 50 to the drinkware container 100) when the temperature setpoint or temperature range is reached.
The power base 50 optionally communicates a signal (e.g., visual signal, audio signal) to the user indicating the heating process is complete and the contents (e.g., liquid) in the chamber C are ready for consumption. Said signal can optionally include a color light (e.g., green) of the indicator light 51, or can optionally include a text message displayed on a user interface (e.g., user interface 64) of the power base 50, or can optionally include a signal communicated wirelessly by the power base 50 to the mobile electronic device 150. In another optional implementation, the power base 50 ends the heating process upon receiving a “stop heating” instruction from the user (e.g., via a user interface on the power base 50, or wirelessly via the mobile electronic device 150).
Upon disallowing transfer of power from the power base 50 to the drinkware container 100 (when the heating process has completed), the cover 70 can be decoupled from the power base 50 and the drinkware container 100 can be detached from the power base 50. For example, where electromagnetic coupling is used between the power base 50 and the cover 70, disallowing transfer of power from the power base 50 to the drinkware container 100 optionally automatically switches off the electromagnets 59, allowing the cover 70 to be decoupled from the power base 50. Where the power base 50 includes one or more power storage elements 55, the power base 50 can be connected to power source to recharge the one or more power storage elements 55, in the manner discussed above.
In implementations where the power base 50 includes a transceiver 62 (see
In one implementation, at least one of the one or more sensors 80 can optionally be operated to sense a level of liquid in the chamber C and to communicate the sensed information to the power base 50 (e.g., to the circuitry 56 of the power base 50), as discussed above. The circuitry 56 can optionally calculate a volume of liquid based on the sensed liquid level (e.g., using information stored on the computer readable medium (e.g., memory) 61 on the size of the chamber C in the drinkware container 100). Alternatively, at least one of the one or more sensors 80 can sense a volume of liquid in the chamber C and communicate the sensed volume data to the power base 50 (e.g., to the circuitry 56 of the power base 50).
Advantageously, the power base 50 can log information on the volume of liquid consumed in any feeding (e.g., save it on the computer readable medium 61), as well as the time the feeding began and the duration of the feeding period (e.g., via time information provided by the timer 69 to the MCU 60). For example, when a heating operation of the liquid (e.g., milk) in the drinkware container 100 is started, the power base 50 can log the start volume (e.g., sensed volume, calculated volume) of the liquid. Once the heating process is completed, the drinkware container 100 is removed from the power base 50 and the infant is fed the contents of the drinkware container 100. Upon completion of the feeding session, the user can place the drinkware container 100 back onto the power base 50, at which point the power base 50 can again log the end volume (e.g., sensed volume, calculated volume) of the liquid in the drinkware container 100 and the circuitry 56 can calculate the volume consumed by the infant (e.g., by subtracting the end volume from the start volume).
Optionally, the power base 50 can communicate data associated with the feeding, such as one or more of feeding start time, feeding end time, feeding duration, and volume consumed to a user. For example, the power base 50 can communicate such data wirelessly to a mobile electronic device (e.g., via an app in the mobile electronic device), which can log feeding data over a period of time (e.g., per day, per week, per month) that the user can access to view the consumption history by the infant. Additionally, or alternatively, the power base 50 can optionally save data in the computer readable medium 61, and provide it to the user when requested by the user via the remote electronic device 150 (e.g., via a smartphone or via a voice activated intelligent personal assistant).
In embodiments of the present invention, an infant bottle feeding system may be in accordance with any of the following clauses:
While certain embodiments of the inventions have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the disclosure. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms. For example, though the features disclosed herein are described in connection with infant bottles (e.g., baby bottles, sippy cups), the features are applicable to other drinkware containers and other containers (e.g., dishware, such as plates and bowls, serverware such as serving dishes and hot plates, food storage containers such as tortilla warmers, bread baskets) and the invention is understood to extend to such other containers. Furthermore, various omissions, substitutions and changes in the systems and methods described herein may be made without departing from the spirit of the disclosure. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the disclosure. Accordingly, the scope of the present inventions is defined only by reference to the appended claims.
Features, materials, characteristics, or groups described in conjunction with a particular aspect, embodiment, or example are to be understood to be applicable to any other aspect, embodiment or example described in this section or elsewhere in this specification unless incompatible therewith. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or steps are mutually exclusive. The protection is not restricted to the details of any foregoing embodiments. The protection extends to any novel one, or any novel combination, of the features disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed.
Furthermore, certain features that are described in this disclosure in the context of separate implementations can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations, one or more features from a claimed combination can, in some cases, be excised from the combination, and the combination may be claimed as a subcombination or variation of a subcombination.
Moreover, while operations may be depicted in the drawings or described in the specification in a particular order, such operations need not be performed in the particular order shown or in sequential order, or that all operations be performed, to achieve desirable results. Other operations that are not depicted or described can be incorporated in the example methods and processes. For example, one or more additional operations can be performed before, after, simultaneously, or between any of the described operations. Further, the operations may be rearranged or reordered in other implementations. Those skilled in the art will appreciate that in some embodiments, the actual steps taken in the processes illustrated and/or disclosed may differ from those shown in the figures. Depending on the embodiment, certain of the steps described above may be removed, others may be added. Furthermore, the features and attributes of the specific embodiments disclosed above may be combined in different ways to form additional embodiments, all of which fall within the scope of the present disclosure. Also, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described components and systems can generally be integrated together in a single product or packaged into multiple products.
For purposes of this disclosure, certain aspects, advantages, and novel features are described herein. Not necessarily all such advantages may be achieved in accordance with any particular embodiment. Thus, for example, those skilled in the art will recognize that the disclosure may be embodied or carried out in a manner that achieves one advantage or a group of advantages as taught herein without necessarily achieving other advantages as may be taught or suggested herein.
Conditional language, such as “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements, and/or steps. Thus, such conditional language is not generally intended to imply that features, elements, and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or steps are included or are to be performed in any particular embodiment.
Conjunctive language such as the phrase “at least one of X, Y, and Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to convey that an item, term, etc. may be either X, Y, or Z. Thus, such conjunctive language is not generally intended to imply that certain embodiments require the presence of at least one of X, at least one of Y, and at least one of Z.
Language of degree used herein, such as the terms “approximately,” “about,” “generally,” and “substantially” as used herein represent a value, amount, or characteristic close to the stated value, amount, or characteristic that still performs a desired function or achieves a desired result. For example, the terms “approximately”, “about”, “generally,” and “substantially” may refer to an amount that is within less than 10% of, within less than 5% of, within less than 1% of, within less than 0.1% of, and within less than 0.01% of the stated amount. As another example, in certain embodiments, the terms “generally parallel” and “substantially parallel” refer to a value, amount, or characteristic that departs from exactly parallel by less than or equal to 15 degrees, 10 degrees, 5 degrees, 3 degrees, 1 degree, or 0.1 degree.
The scope of the present disclosure is not intended to be limited by the specific disclosures of preferred embodiments in this section or elsewhere in this specification, and may be defined by claims as presented in this section or elsewhere in this specification or as presented in the future. The language of the claims is to be interpreted broadly based on the language employed in the claims and not limited to the examples described in the present specification or during the prosecution of the application, which examples are to be construed as non-exclusive.
Number | Name | Date | Kind |
---|---|---|---|
730337 | Bonnefont | Jun 1903 | A |
1649067 | Karlson | Nov 1927 | A |
1721311 | Muenchen | Jul 1929 | A |
2046125 | Lacy | Jun 1936 | A |
2300891 | Hanks | Nov 1942 | A |
2505092 | Brewer | Apr 1950 | A |
2582781 | Johnson | Jan 1952 | A |
2843719 | Smith | Jul 1958 | A |
2992316 | Baumstein | Jul 1961 | A |
3064113 | Mani | Nov 1962 | A |
3155260 | Widener | Nov 1964 | A |
3345934 | Steiner | Oct 1967 | A |
3463140 | Rollor | Aug 1969 | A |
3603106 | Ryan | Sep 1971 | A |
3622753 | Lax | Nov 1971 | A |
3676248 | Swartz | Jul 1972 | A |
3678248 | Tricault | Jul 1972 | A |
3739148 | Ryckman, Jr. | Jun 1973 | A |
3766975 | Todd | Oct 1973 | A |
3797563 | Hoffmann | Mar 1974 | A |
3805440 | Becker | Apr 1974 | A |
3892945 | Lerner | Jul 1975 | A |
3931494 | Fisher | Jan 1976 | A |
4068115 | Mack | Jan 1978 | A |
4095090 | Pianezza | Jun 1978 | A |
4134004 | Anderson | Jan 1979 | A |
4240272 | Tiede | Dec 1980 | A |
4442343 | Genuit | Apr 1984 | A |
4470999 | Carpiac | Sep 1984 | A |
4531046 | Stover | Jul 1985 | A |
4537044 | Putnam | Aug 1985 | A |
D296509 | Fuke | Jul 1988 | S |
4801782 | Ineson | Jan 1989 | A |
4827107 | Peery | May 1989 | A |
4978833 | Knepler | Dec 1990 | A |
4980539 | Walton | Dec 1990 | A |
4982722 | Wyatt | Jan 1991 | A |
4983798 | Eckler | Jan 1991 | A |
5042258 | Sundhar | Aug 1991 | A |
5090209 | Martin | Feb 1992 | A |
5163290 | Kinnear | Nov 1992 | A |
5199275 | Martin | Apr 1993 | A |
5208896 | Katayev | May 1993 | A |
5217064 | Kellow | Jun 1993 | A |
5243684 | Edwards | Sep 1993 | A |
5274215 | Jackson | Dec 1993 | A |
5283420 | Montalto | Feb 1994 | A |
5313787 | Martin | May 1994 | A |
5343368 | Miller | Aug 1994 | A |
5388565 | Ou | Feb 1995 | A |
5448809 | Kraus | Sep 1995 | A |
5497883 | Monetti | Mar 1996 | A |
5508494 | Sarris | Apr 1996 | A |
5508600 | Myslinski | Apr 1996 | A |
5549035 | Wing-Chung | Aug 1996 | A |
5550452 | Shirai | Aug 1996 | A |
5603220 | Seaman | Feb 1997 | A |
5603858 | Wyatt | Feb 1997 | A |
5643485 | Potter | Jul 1997 | A |
5678925 | Garmaise | Oct 1997 | A |
5692627 | Feng | Dec 1997 | A |
5731568 | Malecek | Mar 1998 | A |
5737923 | Gilley | Apr 1998 | A |
D394581 | Paris | May 1998 | S |
5771788 | Lee | Jun 1998 | A |
5786643 | Wyatt | Jul 1998 | A |
5842353 | Kuo-Liang | Dec 1998 | A |
5884006 | Frohlich | Mar 1999 | A |
5903133 | Amero, Jr | May 1999 | A |
5948301 | Liebermann | Sep 1999 | A |
5954984 | Ablah | Sep 1999 | A |
5959433 | Rohde | Sep 1999 | A |
6000224 | Foye | Dec 1999 | A |
6005233 | Wyatt | Dec 1999 | A |
6013901 | Lavoie | Jan 2000 | A |
6020575 | Nagle et al. | Feb 2000 | A |
6032481 | Mosby | Mar 2000 | A |
6042720 | Reber | Mar 2000 | A |
6072161 | Stein | Jun 2000 | A |
6075229 | Vanselow | Jun 2000 | A |
6089409 | Hart | Jul 2000 | A |
6108489 | Frohlich | Aug 2000 | A |
6110159 | Tsujita | Aug 2000 | A |
6123065 | Teglbjarg | Sep 2000 | A |
6140614 | Padamsee | Oct 2000 | A |
6141975 | Tatsumi | Nov 2000 | A |
6144016 | Garvin | Nov 2000 | A |
6158227 | Seeley | Dec 2000 | A |
6180003 | Reber | Jan 2001 | B1 |
6212959 | Perkins | Apr 2001 | B1 |
6232585 | Clothier | May 2001 | B1 |
RE37213 | Staggs | Jun 2001 | E |
6274856 | Clothier | Aug 2001 | B1 |
6279470 | Simeray | Aug 2001 | B2 |
6281611 | Chen | Aug 2001 | B1 |
6314867 | Russell | Nov 2001 | B1 |
6316753 | Clothier | Nov 2001 | B2 |
6320169 | Clothier | Nov 2001 | B1 |
6350972 | Wright | Feb 2002 | B1 |
6353208 | Bostic | Mar 2002 | B1 |
6376803 | Klinger | Apr 2002 | B1 |
6384387 | Owens | May 2002 | B1 |
6403928 | Ford | Jun 2002 | B1 |
6414278 | Frohlich | Jul 2002 | B1 |
6415624 | Connors | Jul 2002 | B1 |
6417498 | Shields et al. | Jul 2002 | B1 |
6427863 | Nichols | Aug 2002 | B1 |
6433313 | Owens | Aug 2002 | B1 |
6444961 | Clothier | Sep 2002 | B2 |
6543335 | Lassota | Apr 2003 | B1 |
6555789 | Owens | Apr 2003 | B2 |
6571564 | Upadhye | Jun 2003 | B2 |
6584374 | Lee | Jun 2003 | B2 |
6634417 | Kolowich | Oct 2003 | B1 |
6651445 | Clark | Nov 2003 | B1 |
6657170 | Clothier | Dec 2003 | B2 |
6662978 | Lin | Dec 2003 | B2 |
6664520 | Clothier | Dec 2003 | B2 |
6674052 | Luo | Jan 2004 | B1 |
6702138 | Bielecki | Mar 2004 | B1 |
6703590 | Holley, Jr. | Mar 2004 | B1 |
6742665 | Augustyn | Jun 2004 | B2 |
6818867 | Kressmann | Nov 2004 | B2 |
6852954 | Liu | Feb 2005 | B1 |
6864462 | Sanoner | Mar 2005 | B2 |
6870135 | Hamm | Mar 2005 | B2 |
6921880 | Berger | Jul 2005 | B2 |
6953913 | Hara | Oct 2005 | B1 |
6968888 | Kolowich | Nov 2005 | B2 |
7002111 | Bauer | Feb 2006 | B2 |
7022946 | Sanoner | Apr 2006 | B2 |
7034256 | Phillips | Apr 2006 | B1 |
7059387 | Kolowich | Jun 2006 | B2 |
7073678 | Dibdin | Jul 2006 | B1 |
7091455 | Fung | Aug 2006 | B2 |
7109445 | Patterson | Sep 2006 | B2 |
7174720 | Kennedy | Feb 2007 | B2 |
7193190 | Kissel, Jr. | Mar 2007 | B2 |
7208707 | Clothier | Apr 2007 | B2 |
7212955 | Kirshenhaum | May 2007 | B2 |
7227108 | Clothier | Jun 2007 | B2 |
7263283 | Knepler | Aug 2007 | B2 |
7276676 | Thompson | Oct 2007 | B1 |
7287386 | Upadhye | Oct 2007 | B2 |
7287656 | Guilford, III | Oct 2007 | B2 |
7414380 | Tang | Aug 2008 | B2 |
7419073 | Crisp | Sep 2008 | B2 |
7431174 | Thissen | Oct 2008 | B2 |
7571830 | Lin | Aug 2009 | B2 |
7592084 | Hoffjann | Sep 2009 | B2 |
D606661 | Colombo | Dec 2009 | S |
7659493 | Reusche | Feb 2010 | B2 |
7681754 | Ross | Mar 2010 | B1 |
7683572 | Toya | Mar 2010 | B2 |
7748223 | Minoura | Jul 2010 | B2 |
7815067 | Matsumoto | Oct 2010 | B2 |
7825353 | Shingler | Nov 2010 | B2 |
7836722 | Magill | Nov 2010 | B2 |
7861538 | Welle | Jan 2011 | B2 |
7872214 | Schandel | Jan 2011 | B2 |
7886655 | Lassota | Feb 2011 | B1 |
7934537 | Kolowich | May 2011 | B2 |
7942145 | Palena | May 2011 | B2 |
7948209 | Jung | May 2011 | B2 |
7966927 | Yoakim | Jun 2011 | B2 |
7997786 | Liu | Aug 2011 | B2 |
8045848 | Wortley | Oct 2011 | B2 |
8055310 | Beart | Nov 2011 | B2 |
8061149 | Gowans | Nov 2011 | B1 |
8076620 | Maupin | Dec 2011 | B2 |
8146485 | Ozanne | Apr 2012 | B2 |
8205468 | Hemminger | Jun 2012 | B2 |
8272532 | Michaelian | Sep 2012 | B2 |
8274016 | Montana | Sep 2012 | B2 |
8280453 | Beart | Oct 2012 | B2 |
8319154 | Shaikh | Nov 2012 | B2 |
8336729 | Kelly | Dec 2012 | B2 |
8400104 | Adamczyk | Mar 2013 | B2 |
8448809 | Kelly | May 2013 | B2 |
8467669 | Widanagamage | Jun 2013 | B2 |
8479941 | Matsumoto | Jul 2013 | B2 |
8618448 | Alexander | Dec 2013 | B2 |
8621980 | Bunn | Jan 2014 | B2 |
8759721 | Alexander | Jun 2014 | B1 |
8907796 | Sweeney | Dec 2014 | B2 |
9035222 | Alexander | May 2015 | B2 |
9138097 | Driel et al. | Sep 2015 | B2 |
9151545 | Soukhojak | Oct 2015 | B2 |
9184427 | Chuang | Nov 2015 | B2 |
9265371 | Glucksman et al. | Feb 2016 | B2 |
9351600 | Rime | May 2016 | B2 |
9480363 | Delattre et al. | Nov 2016 | B2 |
9648970 | Lee | May 2017 | B2 |
9814331 | Alexander | Nov 2017 | B2 |
9839324 | Xiao et al. | Dec 2017 | B2 |
9863695 | Alexander et al. | Jan 2018 | B2 |
9967924 | Heczko | May 2018 | B2 |
9974401 | Alexander | May 2018 | B2 |
10098498 | Alexander | Oct 2018 | B2 |
10182674 | Alexander et al. | Jan 2019 | B2 |
D842020 | Augustyn | Mar 2019 | S |
20010009609 | Bradenhaugh | Jul 2001 | A1 |
20010022304 | Roche | Sep 2001 | A1 |
20010023866 | Wang | Sep 2001 | A1 |
20020023912 | McGee | Feb 2002 | A1 |
20020083840 | Lassota | Jul 2002 | A1 |
20020104318 | Jaafar | Aug 2002 | A1 |
20020129712 | Westbrook | Sep 2002 | A1 |
20020162339 | Harrison | Nov 2002 | A1 |
20020175158 | Sanoner et al. | Nov 2002 | A1 |
20030024250 | Haas | Feb 2003 | A1 |
20030029662 | Piech | Feb 2003 | A1 |
20030029862 | Clothier | Feb 2003 | A1 |
20030066638 | Qu | Apr 2003 | A1 |
20030074903 | Upadhye | Apr 2003 | A1 |
20030145621 | Kidwell | Aug 2003 | A1 |
20040004072 | Clothier | Jan 2004 | A1 |
20040006996 | Butcher | Jan 2004 | A1 |
20040159240 | Ill | Aug 2004 | A1 |
20040167592 | Grove | Aug 2004 | A1 |
20040194470 | Upadhye | Oct 2004 | A1 |
20050045615 | Sanoner | Mar 2005 | A1 |
20050121431 | Yuen | Jun 2005 | A1 |
20050242804 | Hintz | Nov 2005 | A1 |
20060021513 | Ide | Feb 2006 | A1 |
20060023480 | Plummer | Feb 2006 | A1 |
20060081599 | Anderson | Apr 2006 | A1 |
20060173259 | Flaherty | Aug 2006 | A1 |
20060207442 | Pettersson | Sep 2006 | A1 |
20060209628 | Jones | Sep 2006 | A1 |
20060231109 | Howell | Oct 2006 | A1 |
20060261233 | Williams et al. | Nov 2006 | A1 |
20070017890 | Ai-Jadh | Jan 2007 | A1 |
20070092773 | Guo | Apr 2007 | A1 |
20070151457 | Rabin | Jul 2007 | A1 |
20070182367 | Partovi | Aug 2007 | A1 |
20070223895 | Flemm | Sep 2007 | A1 |
20070278207 | Van Hoy | Dec 2007 | A1 |
20070279002 | Partovi | Dec 2007 | A1 |
20080011077 | Ramus | Jan 2008 | A1 |
20080019122 | Kramer | Jan 2008 | A1 |
20080022695 | Welle | Jan 2008 | A1 |
20080022696 | Welle | Jan 2008 | A1 |
20080041233 | Bunn | Feb 2008 | A1 |
20080041859 | Teglbjarg | Feb 2008 | A1 |
20080087270 | Shaikh | Apr 2008 | A1 |
20080121630 | Simard | May 2008 | A1 |
20080135564 | Romero | Jun 2008 | A1 |
20080141681 | Arnold | Jun 2008 | A1 |
20080149624 | Tamura | Jun 2008 | A1 |
20080179311 | Koro | Jul 2008 | A1 |
20080213449 | Wisner | Sep 2008 | A1 |
20080251063 | Palena et al. | Oct 2008 | A1 |
20080272134 | Rohe | Nov 2008 | A1 |
20090049845 | Mcstravick | Feb 2009 | A1 |
20090058352 | Lin | Mar 2009 | A1 |
20090064687 | Tuszkiewicz | Mar 2009 | A1 |
20090071952 | Kuwabara | Mar 2009 | A1 |
20090102296 | Greene | Apr 2009 | A1 |
20090166350 | Ho | Jul 2009 | A1 |
20090184102 | Parker, Jr. | Jul 2009 | A1 |
20090230117 | Fernando | Sep 2009 | A1 |
20100000980 | Popescu | Jan 2010 | A1 |
20100028758 | Eaves | Feb 2010 | A1 |
20100089247 | Yang | Apr 2010 | A1 |
20100108694 | Sedlbauer | May 2010 | A1 |
20100125417 | Hyde | May 2010 | A1 |
20100147014 | Kim | Jun 2010 | A1 |
20100158489 | Siu | Jun 2010 | A1 |
20100158660 | Radhakrishnan | Jun 2010 | A1 |
20100186499 | Ramus et al. | Jul 2010 | A1 |
20100206833 | Minca | Aug 2010 | A1 |
20100251755 | Lauchnor | Oct 2010 | A1 |
20110056215 | Ham | Mar 2011 | A1 |
20110062149 | Oriel | Mar 2011 | A1 |
20110072978 | Popescu | Mar 2011 | A1 |
20110108506 | Lindhorst-Ko | May 2011 | A1 |
20110121660 | Azancot | May 2011 | A1 |
20110143000 | Fiset | Jun 2011 | A1 |
20110152979 | Driscoll | Jun 2011 | A1 |
20110155621 | Lindquist | Jun 2011 | A1 |
20110174993 | Blain | Jul 2011 | A1 |
20110179807 | Holloway | Jul 2011 | A1 |
20110180527 | Abbott | Jul 2011 | A1 |
20110198255 | Baumfalk | Aug 2011 | A1 |
20110259871 | Li | Oct 2011 | A1 |
20110265562 | Li | Nov 2011 | A1 |
20120061050 | Petrillo | Mar 2012 | A1 |
20120064470 | Delattre | Mar 2012 | A1 |
20120082766 | Maupin | Apr 2012 | A1 |
20120090333 | Deliamorte, Jr. | Apr 2012 | A1 |
20120103562 | Alexander | May 2012 | A1 |
20120118874 | Williams | May 2012 | A1 |
20120132646 | England | May 2012 | A1 |
20120138597 | Quella | Jun 2012 | A1 |
20120187066 | Redl | Jul 2012 | A1 |
20120193999 | Zeine | Aug 2012 | A1 |
20120235505 | Schatz | Sep 2012 | A1 |
20120235636 | Partovi | Sep 2012 | A1 |
20120248096 | Lee | Oct 2012 | A1 |
20120255946 | Kim | Oct 2012 | A1 |
20120256585 | Partovi | Oct 2012 | A1 |
20120258229 | Mindrup | Oct 2012 | A1 |
20120312031 | Olsen | Dec 2012 | A1 |
20120319500 | Beart | Dec 2012 | A1 |
20130016462 | Howitt | Jan 2013 | A1 |
20130059259 | Oldani | Mar 2013 | A1 |
20130103463 | Briar | Apr 2013 | A1 |
20130167730 | Behm | Jul 2013 | A1 |
20130200064 | Alexander | Aug 2013 | A1 |
20130206015 | Jacoby | Aug 2013 | A1 |
20130221013 | Kolowich | Aug 2013 | A1 |
20130239607 | Kelly | Sep 2013 | A1 |
20130247591 | Demasi | Sep 2013 | A1 |
20130255824 | Williams et al. | Oct 2013 | A1 |
20130275075 | Johnson | Oct 2013 | A1 |
20140165607 | Alexander | Jun 2014 | A1 |
20140230484 | Yavitz | Aug 2014 | A1 |
20140238985 | Sweeney | Aug 2014 | A1 |
20140354438 | Hazen | Dec 2014 | A1 |
20150024349 | Bischoff | Jan 2015 | A1 |
20150122688 | Dias | May 2015 | A1 |
20150245723 | Alexander | Sep 2015 | A1 |
20150335184 | Balachandran | Nov 2015 | A1 |
20160183730 | Bedi | Jun 2016 | A1 |
20160242598 | Alexander | Aug 2016 | A1 |
20170150840 | Park | Jun 2017 | A1 |
20170245678 | Wakeham | Aug 2017 | A1 |
20170360253 | Alexander | Dec 2017 | A1 |
20180290875 | Swears | Oct 2018 | A1 |
20190008317 | Alexander | Jan 2019 | A1 |
20200093326 | Alexander | Mar 2020 | A1 |
Number | Date | Country |
---|---|---|
631614 | Aug 1982 | CH |
1338240 | Mar 2002 | CN |
1502513 | Jun 2004 | CN |
2684824 | Mar 2005 | CN |
2708795 | Jul 2005 | CN |
1748112 | Mar 2006 | CN |
1776992 | May 2006 | CN |
2922666 | Jul 2007 | CN |
101069606 | Nov 2007 | CN |
200980833 | Nov 2007 | CN |
101109795 | Jan 2008 | CN |
201042350 | Apr 2008 | CN |
201076180 | Jun 2008 | CN |
201308643 | Oct 2008 | CN |
201171801 | Dec 2008 | CN |
201237271 | May 2009 | CN |
101507261 | Aug 2009 | CN |
201303850 | Sep 2009 | CN |
201445353 | May 2010 | CN |
101721314 | Jun 2010 | CN |
101820128 | Sep 2010 | CN |
201612420 | Oct 2010 | CN |
201668739 | Dec 2010 | CN |
202168958 | Mar 2012 | CN |
102802294 | May 2012 | CN |
202681700 | Jan 2013 | CN |
202682376 | Jan 2013 | CN |
101052368 | Apr 2013 | CN |
202919767 | May 2013 | CN |
203123058 | Aug 2013 | CN |
102266184 | Oct 2013 | CN |
101945599 | Mar 2014 | CN |
203468187 | Mar 2014 | CN |
103784326 | May 2014 | CN |
102512085 | Jun 2014 | CN |
203777334 | Aug 2014 | CN |
203874128 | Oct 2014 | CN |
203915518 | Nov 2014 | CN |
203989073 | Dec 2014 | CN |
104473771 | Apr 2015 | CN |
204261058 | Apr 2015 | CN |
204352215 | May 2015 | CN |
204428452 | Jul 2015 | CN |
204483720 | Jul 2015 | CN |
204501704 | Jul 2015 | CN |
103622425 | Sep 2015 | CN |
204709427 | Oct 2015 | CN |
204766593 | Nov 2015 | CN |
204862692 | Dec 2015 | CN |
103989380 | Jan 2016 | CN |
204931161 | Jan 2016 | CN |
204931162 | Jan 2016 | CN |
204950604 | Jan 2016 | CN |
204972308 | Jan 2016 | CN |
205054911 | Mar 2016 | CN |
205163676 | Apr 2016 | CN |
205459941 | Aug 2016 | CN |
205698560 | Nov 2016 | CN |
205849824 | Jan 2017 | CN |
205849825 | Jan 2017 | CN |
205948058 | Feb 2017 | CN |
205948059 | Feb 2017 | CN |
205994186 | Mar 2017 | CN |
206006757 | Mar 2017 | CN |
206026710 | Mar 2017 | CN |
206044395 | Mar 2017 | CN |
206045000 | Mar 2017 | CN |
206063431 | Apr 2017 | CN |
206102985 | Apr 2017 | CN |
206102987 | Apr 2017 | CN |
206120763 | Apr 2017 | CN |
206167409 | May 2017 | CN |
206198317 | May 2017 | CN |
206213740 | Jun 2017 | CN |
206252255 | Jun 2017 | CN |
206285271 | Jun 2017 | CN |
206295458 | Jul 2017 | CN |
206355335 | Jul 2017 | CN |
106998957 | Aug 2017 | CN |
206391214 | Aug 2017 | CN |
206414170 | Aug 2017 | CN |
206424319 | Aug 2017 | CN |
206508264 | Sep 2017 | CN |
206630471 | Nov 2017 | CN |
206642098 | Nov 2017 | CN |
206657256 | Nov 2017 | CN |
206660148 | Nov 2017 | CN |
206687924 | Dec 2017 | CN |
206729506 | Dec 2017 | CN |
206730161 | Dec 2017 | CN |
206730162 | Dec 2017 | CN |
104958185 | Jan 2018 | CN |
105231819 | Jan 2018 | CN |
206896527 | Jan 2018 | CN |
206934346 | Jan 2018 | CN |
206934347 | Jan 2018 | CN |
207041678 | Feb 2018 | CN |
207137055 | Mar 2018 | CN |
207137057 | Mar 2018 | CN |
207221113 | Apr 2018 | CN |
106419508 | May 2018 | CN |
207306902 | May 2018 | CN |
207445226 | Jun 2018 | CN |
207506787 | Jun 2018 | CN |
106361167 | Aug 2018 | CN |
207755561 | Aug 2018 | CN |
2 07821691 | Sep 2018 | CN |
2 07821692 | Sep 2018 | CN |
207821693 | Sep 2018 | CN |
207855570 | Sep 2018 | CN |
105395078 | Oct 2018 | CN |
207996308 | Oct 2018 | CN |
208030985 | Nov 2018 | CN |
208048624 | Nov 2018 | CN |
105943402 | Dec 2018 | CN |
208211918 | Dec 2018 | CN |
105640315 | Jan 2019 | CN |
2 08448168 | Feb 2019 | CN |
208461536 | Feb 2019 | CN |
208463661 | Feb 2019 | CN |
208481024 | Feb 2019 | CN |
208481124 | Feb 2019 | CN |
208491583 | Feb 2019 | CN |
19744526 | Apr 1999 | DE |
20108363 | Aug 2001 | DE |
20314416 | Jan 2004 | DE |
202016007747 | Mar 2017 | DE |
0332355 | Sep 1989 | EP |
0722708 | Jul 1996 | EP |
0895772 | Feb 1999 | EP |
1338230 | May 2006 | EP |
1722661 | Jan 2008 | EP |
2165243 | Mar 2010 | EP |
2001761 | Jan 2012 | EP |
2288278 | Apr 2012 | EP |
2308771 | Jun 2012 | EP |
2498653 | Jan 2015 | EP |
3159212 | Apr 2017 | EP |
3267861 | Jan 2018 | EP |
2 705 764 | Dec 1994 | FR |
2737380 | Jan 1997 | FR |
2 752 504 | Feb 1998 | FR |
2752377 | Feb 1998 | FR |
2753071 | Mar 1998 | FR |
2763463 | Nov 1998 | FR |
2808666 | Nov 2001 | FR |
2828082 | Feb 2003 | FR |
73 5 674 | Aug 1955 | GB |
2 390 798 | Jan 2004 | GB |
2414922 | Dec 2005 | GB |
2439270 | Aug 2006 | GB |
2441825 | Mar 2008 | GB |
2498338 | Feb 2017 | GB |
2541080 | Apr 2018 | GB |
02555CN2012 | May 2013 | IN |
03553MU2012 | Jun 2015 | IN |
201744034469 | Apr 2018 | IN |
U-S54-147575 | Apr 1953 | JP |
S63-249519 | Oct 1988 | JP |
06-021549 | Mar 1994 | JP |
H10-146276 | Jun 1998 | JP |
11-268777 | Oct 1999 | JP |
2000-279302 | Oct 2000 | JP |
2003-299255 | Oct 2003 | JP |
A-2004-261493 | Sep 2004 | JP |
2006-068152 | Mar 2006 | JP |
2006-102234 | Apr 2006 | JP |
2006-166522 | Jun 2006 | JP |
2006-345957 | Dec 2006 | JP |
2007-064557 | Mar 2007 | JP |
2007-312932 | Dec 2007 | JP |
2008-173464 | Jul 2008 | JP |
U-3153007 | Jul 2009 | JP |
2010-527226 | Aug 2010 | JP |
2011-171205 | Sep 2011 | JP |
5127819 | Jan 2013 | JP |
5481388 | Apr 2014 | JP |
5742514 | Jul 2015 | JP |
6223501 | Nov 2017 | JP |
2011 0080453 | Jul 2011 | KR |
WO 2004055654 | Jul 2004 | WO |
WO 2008028329 | Mar 2008 | WO |
WO 2008065175 | Jun 2008 | WO |
WO 2008137996 | Nov 2008 | WO |
WO 2008155538 | Dec 2008 | WO |
WO 2009138930 | Nov 2009 | WO |
WO 2010087560 | Aug 2010 | WO |
WO 2010087560 | Aug 2010 | WO |
WO 2012104665 | Aug 2012 | WO |
WO 2013 182520 | Dec 2013 | WO |
WO 2013 187763 | Dec 2013 | WO |
WO 2014 138771 | Sep 2014 | WO |
WO 2018122669 | Jul 2018 | WO |
Entry |
---|
Office Action dated Aug. 15, 2022, received in Chinese Patent Application No. 201980014931, in 15 pages. |
Australian Examination Report regarding Application No. 2016216669, dated Feb. 14, 2019, four pages. |
BabyBoo Feeding Bottle by Faitron AG, available before Jan. 31, 2018 https://web.archive.org/web/20170902065935/https:/www.faitron.com/babyboo/) 11 pages. |
Chinese Office Action, regarding Application No. 201510869257.5, dated Aug. 30, 2018, 9 pages. |
Decision of Rejection dated Apr. 4, 2017 in JP Application No. 2013-537797. |
European Office Action dated Sep. 28, 2017, received in European Patent Application No. 14 774 350.4, p. 5. |
European Patent Office Extended Search Report regarding Application No. EP 21208864.5, dated Feb. 4, 2022, 10 pages. |
European Patent Office Search Report dated Mar. 17, 2016 regarding Application No. 11838764.6-1804, PCT/US2011059014, 7 pages. |
European Search Report received in European Patent Application No. 15811173.2, dated Dec. 13, 2017. |
First Office Action dated Nov. 23, 2016 in CN Application No. 201480014620.9. |
International Preliminary Report on Patentability dated May 7, 2013 in PCT Application No. PCT/US2011/059014. |
International Search Report and Written Opinion dated Jul. 2015, Application No. PCT/US15/36304, 18 pages. |
International Search Report and Written Opinion dated Jan. 12, 2016 in PCT Application No. PCT/US15/36304. |
International Search Report and Written Opinion dated Dec. 9, 2014 in PCT/US2014/019130. |
International Search Report and Written Opinion dated Mar. 16, 2012 in PCT/US2011/059014. |
Non-final office action dated Aug. 2, 2016 in Japanese Patent Application No. 2013-537797. |
Notice of Reason(s) for Rejection dated Aug. 11, 2015 in JP Application No. 2013-53797. |
Office Action dated Aug. 7, 2018, received for Japanese Patent Application No. JP 2017-151497, 4 pages. |
Office Action dated Jan. 12, 2018, received in Chinese Application No. 201510869257.5. |
Office Action in related Chinese Application No. 201180063844.5, dated Dec. 29, 2014. |
Office Action received in Japanese Patent Application No. 2017-151497, dated Nov. 21, 2017, 5 pages. |
Patent Examination Report No. 1 in related Australian Application No. 2011323416, dated May 15, 2015. |
Patent Examination Report No. 2 in related Australian Application No. 2011323416, dated Oct. 20, 2015. |
PCT International Search Report and Written Opinion, regarding International Application No. PCT/US2019/015609, dated Jul. 18, 2019, 21 pages. |
PCT Invitation to Pay Additional Fees dated Apr. 10, 2019, regarding PCT/US2019/015609, 13 pages. |
Second Office Action dated Apr. 10, 2017 in CN Application No. 201510869257.5. |
Supplementary European Search Report dated Oct. 18, 2016 in European Application No. 14774350. |
Number | Date | Country | |
---|---|---|---|
20220354300 A1 | Nov 2022 | US |
Number | Date | Country | |
---|---|---|---|
62624657 | Jan 2018 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16540955 | Aug 2019 | US |
Child | 17814493 | US | |
Parent | 16260856 | Jan 2019 | US |
Child | 16540955 | US |