Patent Grant
10329061
The present invention relates generally to a container management system, embodiments of which are configured to communicate with or include a computer system.
Consumers often use containers to store food, beverages, other consumable products, cleaning products, and other non-consumable products. Basic containers permit the consumer only to store a product, but typically provide little information about the current status or historical status of the product.
For example, a basic beverage container may be configured to store a beverage. However, to obtain information about the current status of the beverage or its container, the consumer typically must physically manipulate the beverage container. As an example, to test the temperature of the beverage in the container, the consumer might touch the outside of the container, drink some of the beverage, pour a small amount of the beverage onto their hand, or dip a finger into the beverage. If the beverage is too hot, such “testing” methods might cause a burn. Also, such testing methods may be unsanitary or otherwise contaminate the beverage.
Some more advanced containers may include a thermometer positioned within the container so that the consumer can assess the temperature without risking a burn or contaminating the beverage. However, even such advanced containers generally permit the consumer to view the temperature reading only from the thermometer itself or an integrated thermometer output display. Such containers generally lack the ability to track the temperature readings over time or permit the consumer to ascertain the temperature of the beverage from a remote location (e.g., while container is in a car and consumer is running errands).
Another disadvantage of known beverage containers is the possibility of spilling or otherwise inadvertently releasing some of the beverage from the container. Certain types of lids are designed to minimize spilling. For example, such lids may include a removable barrier positionable over a pour spout or drinking opening. However, such lids do not effectively minimize spillage if the barrier is not in place when the container tips over.
Clearly, there is a need for a container management system configured to permit detecting, tracking, recording, and communicating information about the container or its contents, such information which may include temperature of the container contents or instructions to automatically cover a lid opening. Certain embodiments of the present invention satisfy this need.
Certain embodiments of a container management system and related methods include a container system having a lid or a retainer, either of which may be configured to communicate with or include a computer system. The container management system also may be comprised of various sensors, action elements, computer elements, and additional components, which are described in more detail below.
For purposes of this application, a “retainer” is any item configured to generally hold in place a consumable product or a non-consumable product. A retainer may contain not only products, but also other contents, e.g., ambient air, vacuum space, etc. Examples of a retainer include a bottle, cup, mug, tumbler, flask, pitcher, carafe, pump pot, coffeepot, teapot, canteen, decanter, cup-holder, jar, can, drum, vial, syringe, box, cooler, lunch kit, or bag.
A retainer may include a retainer body configured to receive a product. More specifically, a retainer body may be sized and shaped to define a retainer space. The retainer body may be made from any suitable material, including a generally rigid material, a generally flexible material, a generally insulated material, or a generally non-insulated material. Examples of retainer body materials include metal (e.g., stainless steel), glass, rubber, silicone, plastic (e.g., food grade plastic), or any combination thereof. An insulated material may include a double-wall vacuum insulated construction or foam insulation.
The retainer body may terminate at a retainer edge, which generally defines a retainer opening. A retainer opening may be sized and shaped to permit inserting or pouring a product into the retainer space.
For purposes of this application, a “lid” is any item configured to partially or completely cover a retainer opening and, together with the retainer, generally create an enclosed retainer space. The components of the lid may be made from any suitable material. Examples of lid materials include metal (e.g., stainless steel), glass, rubber, silicone, plastic (e.g., food grade plastic), or any combination thereof. The lid and the retainer may be made from the same material or different materials relative to one another.
Certain embodiments of a lid may be configured to removably connect to a retainer, usually near the retainer edge. Examples of removable connections between a lid and a retainer include complementary threads, snap engagement, or a frictional configuration.
A lid may be configured to permit dispensing or releasing the product out of the retainer space without removing the lid from the retainer. Such lids may have a first lid edge defining a first lid opening configured as a dispensing aperture. The dispensing aperture may include a pour aperture, pour spout, drink aperture, drink spout, faucet spout, spray spout, straw, push-pull cap, nozzle, other aperture, to name a few examples. Certain embodiments of a lid may have additional lid edges defining additional lid openings such as a vent aperture, or system output aperture such as a display element aperture, lid input element aperture, or a computer element aperture. Any aperture configured to receive another element may be sized and shaped such that an appropriate sealing element may be positioned to generally seal (or minimize leakage in) the space between the lid edge and the other element.
In certain embodiments, the lid includes a lid body having a single unit construction, while in other embodiments the lid body has multiple components. A multi-component lid body may include a lid shell element, a lid handle element, and a lid support element. A lid shell element may form the uppermost or outermost part of the lid. A lid handle element is a component configured to permit a user to easily grip or lift the container system. A lid support element may be configured to provide a frame for certain other elements of the system, if present, such as the lid shell, any sensors, action elements, or computer elements.
Certain embodiments of a retainer or lid include a vent aperture configured to release pressure from the retainer space. Each vent aperture may include a valve configured to minimize spilling of the beverage from the container system. Also a vent aperture may be positioned to minimize spilling of the beverage from the container system.
The system and methods of the present invention may include one or more sensors, each configured to detect a characteristic or event related to the retainer, lid, or contents of the retainer. Each sensor may be disposed in or on a lid or a retainer or may be suspended from a lid or retainer. Each sensor may be configurable to detect some condition at certain regular or irregular time intervals, upon response to detecting a first condition (e.g., upon detecting change in orientation, detecting a certain volume; upon detecting a change in GPS location; detecting a certain temperature; etc.), upon receiving a request for information, upon response to user instructions provided via user input, or some combination of these or other circumstances.
Examples of a sensor include a temperature sensor, orientation sensor, capacity sensor, volume sensor, location sensor, pressure sensor, image sensor, thermal image sensor, float sensor, lid removal sensor, strain gauge or force sensor, optical recognition sensor, pH sensor, evaporative gas sensor, inductive sensor, Hall effect sensor or switch, resistive sensor, or other type of sensor known in the art. Certain sensor embodiments are discussed in more detail below.
More specifically, a temperature sensor may be disposed to detect, for example, the temperature of the product in the retainer, the temperature of the retainer, the temperature of the lid, or the temperature of ambient air in the retainer space. Examples of a temperature sensor include a thermocouple, thermistor, resistance temperature detector, platinum resistance thermometer, organic-liquid-filled thermometer, or other type of thermometer.
An orientation sensor may be disposed to detect, for example, the orientation of the container system or the contents therein. Examples of an orientation sensor include an accelerometer, gyroscope, piezoelectric sensor, tilt sensor, or tilt switch.
A volume sensor may be disposed to detect, for example, how much product is present in the retainer. A volume sensor may include a sensor configured to measure the distance between the sensor itself and a top surface of a product. For example, ultrasonic waves may be emitted from a wave initiator and a wave receiver may measure how long it takes for such waves to bounce back. Another type of volume sensor may use capacitive sensing in which a first capacitance element creates an electrostatic field that interacts with a surface of the product. Then, a field analyzing element measures the field after such interaction and such measurement can be used to calculate the distance between the volume sensor and a surface of the product.
In other embodiments, multiple volume sensors may be positioned along the inside of the retainer or a descending portion of the lid, such that if a certain volume sensor is in contact with the product, the retainer is at least as full as the height of the volume sensor. Embodiments of such sensing may be termed “point level measurement”.
In still additional embodiments, a volume sensor may be sized and shaped to be disposed along the entire or partial length or height of a retainer to sense whether the product is present or not, and if so, how much is present. When the product is a liquid or other conductive substance, a volume sensor may employ continuous capacitance or parasitic capacitance. Such a capacitance volume sensor may use indirect capacitance such that the sensor does not need to be directly in contact with the liquid, and instead, the sensor is protected by some layer of material or protection element.
A location sensor may be configured to detect the geographic location of the container system. Examples of a location sensor include a global positioning system (GPS), other satellite navigation system, other triangulation systems, compass, or magnetic field sensor. A location sensor also may be used, in combination with map information, by the system to ascertain and alert the user if they are close to a beverage vendor, other restaurant, vending machine, drinking fountain, or other location related to a product. The location sensor also may be used to indicate on a display or computer system whether other container management systems are located nearby, and possibly generate a map showing the location or number of other users in a certain geographic region (e.g., in a park, building, neighborhood, city, etc.) The users shown in the map may be those previously identified as friends via some social network or other users regardless of whether they are known to the user. Also, in certain embodiments, a user may export the map or other indicator showing their own location to a social network.
A pressure sensor may be configured to detect and possibly cause a release in pressure when the pressure reaches a certain threshold or range. For example, if a soup or beverage is spoiling and causing release of gasses, thereby causing a build-up of pressure, the pressure sensor could detect this build up, and, possibly open a vent cover or vent valve to permit release of excess gas.
Any of the sensors may generate a sensor output, which includes detected information in digital or analog format. (If some detected information is in analog format, the system may include an analog to digital converter to facilitate such conversion.) The sensors, or another component in the system, may send the detected information to one or more of the computer elements. The sensors may communicate with the computer elements via any wired or wireless communication system known in the art. Some examples of a wireless communication system may include a system configured to implement Wi-Fi, Bluetooth, Zigbee, Near Field Communication, Infrared, ANT+, Wireless USB, Z-wave, IEEE Standard 802.15.4, IEEE Standard 802.22, RFID, or other short-range wireless communication technology, or long-range wireless communication technology.
The computer elements may convert the sensor output into a system output such as visual output (e.g., representations or light) to be displayed in a display element, audio output (e.g., sounds including tones, beeps, music, songs, words, etc.) to be produced by an audio output element, or tactile output (e.g., vibration) to be caused by a tactile output element. Also, one or more of the computer elements may send instructions back to the sensor, possibly regarding when to start or stop detecting information, when to send detector information to a computer element, instruction to turn on or off, or other information.
The container management system also may be configured to receive, store, or analyze non-detected information such as information input from an external source. Examples of such external source information include weather in the location near the user (as determined by the location sensor or user input of location); map information including vehicle/walking navigation information, site information for restaurants, water fountains, beverage vendors, retailers of container systems/container managements systems, and other places related to a product which may be used in or with the container system, and other system user location information (e.g., locate other users of the same type/brand of container system via a map display); restaurant information including a menu or price information (in addition to restaurant location information identified above); or standards information such as the standard temperature at which people usually wish to consume a beverage, standard temperature at which a beverage is too hot or too cold for safe consumption, standard time after which a beverage or other product is considered stale or otherwise no longer desirable, standard amount of beverage (e.g., water) considered as healthy or hydrated, standard amount of disposable water bottles used by consumers, standard cost of coffee at restaurant or coffee shop; standard amount of cardboard used in typical to-go coffee/tea cup, etc.
The system and methods of the present invention also may include certain action elements configured to cause some physical or chemical change to the retainer, lid, product, or other contents of the retainer. Action elements may be disposed in or on the retainer, lid, or both. Certain embodiments of an action element may be configured to be activated automatically, manually, or both. Examples of an action element include an open/close lid opening assembly, a lid removal assembly, a heating element, a cooling element, a stirring element, an inner compartment door element, a treatment element, or other.
An open/close lid opening assembly may be configured to block or unblock a lid opening according to whether the lid opening is open (unblocked) or closed (blocked). Certain embodiments of the open/close lid opening assembly are configurable to automatically open or close the lid opening in response information detected by one or more sensors or in response to a user input. Such “automatic” embodiments of an open/close lid opening assembly may include a motor configured to rotate a crank, which is in mechanical communication with an actuator element. The actuator element may be disposed to directly block or unblock the lid opening or may be configured to cause movement of a lever arm assembly, which is disposed to block or unblock the lid opening. Automatic embodiments of an open/close lid opening assembly may include a lid input element such as a touchscreen, touch surface (e.g., push button, capacitive surface), roller-ball, keyboard key, switch, or other element configured to permit a user to input information, such as settings of the automatic embodiments, into the system.
Other embodiments of the open/close lid opening assembly may be configured to permit opening or closing the lid opening manually. For example, such embodiments may include a push button, which, when depressed, is disposed to physically change the position of a lid opening obstruction element.
Overall, many configurations of an open/close lid opening assembly are possible and within the scope of the present invention.
Additional types of action elements are described below.
A lid removal assembly may be one or more components configured to automatically or manually disconnect the lid (either partially or completely) from the retainer or removably connect the lid to the retainer. As an example, in certain embodiments, a lid removal assembly may be configured to cause a lid hinged to a retainer to disengage from the retainer at all points except the hinge and may removably reconnect the lid and retainer as well. In another example, a lid removal assembly may be configured to completely remove a threadably connectable lid from a retainer.
A heating element may be a resistive heater, heating wire or coil, thermoelectric heater, or other type of heater configured to increase the temperature of the retainer, lid, product, or other contents of the retainer.
A cooling element may be a refrigerant, ice unit, fan, or other cooling mechanism configured to decrease the temperature of the retainer, lid, product, or other contents of the retainer.
A stirring element may be configured and disposed to mix a product or move around a product within the retainer. Examples of a stirring element include a stirring rod, a straw, a magnetic stirrer, a vibration unit, or other.
An inner compartment door element may be a wall section or flap configured to divide the retainer or lid into one or more separate compartments. Upon activation, the wall section or flap may be configured to automatically or manually change position to provide access or prohibit access to the compartment.
A treatment element may include a filtering element, ultraviolet element, other purifying element, flavor emitting element, fragrance emitting element, liquid conditioning element, cleaning element, or other treatment of the lid, retainer, product, or other contents of the retainer.
Certain embodiments of the system and methods of the present invention include one or more computer elements. Examples of computer elements include a processor, system memory, cache, system bus, chasses, fan, power source, basic input/output system (BIOS), hard disk drive, optical disk drive, non-transitory computer-readable medium, and USB or serial port.
Computer elements disposed in or on the lid or retainer are termed “internal computer elements,” and computer elements that are generally separate from the lid and retainer are termed “external computer elements” for purposes of this application. A group of internal computer elements or a group of external computer elements may form an internal computer system or an external computer system, respectively, or “computer systems” generally. The system and methods of the present invention may include any type of computer system.
Examples of an external computer system include a desktop computer, laptop computer, netbook computer, personal digital assistant, tablet, smartphone, certain other types of cellular telephone, MP3 player, wearable computer unit (e.g., head-mounted unit such as a Google Glass® unit, computerized wristwatch, computerized glove, computerized shoe, e-textiles, etc.), or other handheld or personal computing device. Also, two or more external computer systems may be networked to form a cloud computing system.
Certain embodiments of the present invention may include additional components. For example, embodiments of the present invention may include a power source, such as a battery, capacitor, flywheel, RFID circuit, solar cell, generator (e.g., micro generator, thermoelectric generator, inductive generator, piezoelectric generator, etc.), or power plug (e.g., two prong, three prong, European standard). Embodiments of the present invention also may include a power distributor such as a lithium-ion power distributor.
Also, embodiments of the present invention may include a system output element, such as a lid output element configured to be physically integrated in the lid, a retainer output element configured to be physically integrated in the retainer, or an external computer output element, not configured to be physically integrated with the lid or retainer, but possibly configured to be physically integrated with or connected to certain external computer elements.
Examples of a system output element include a display element, an audio output element, or a tactile output element. A display element may be a touchscreen, non-touch display screen (e.g., LCD screen or LED screen), analog display element, projector, or a single or small group of light emitting diodes. (A user may access a user interface via a display element.) An audio output element may be any kind of speaker. A tactile output element may be a vibration element or other component configured to cause motion or tactile response of some other component.
Method embodiments of the present invention may include using a sensor to detect information (e.g., location, fill volume, access status of lid opening, etc.) about the lid, retainer, or contents of the retainer. Once certain information is detected, that detected information may be used, sometimes in conjunction with externally sourced information, to calculate or compile second level information—termed “calculated information”—that generally cannot be or was not measured directly by the sensors. Calculated information includes computed information and statistical information, each of which is described in more detail below. Sometimes, before or after a sensor is used to detect information, the sensor may be calibrated to a zero reading to promote accuracy.
Additional method embodiments of the present invention may include detecting a condition using a sensor and then, possibly, repeating the detecting step several times in a short period of time (e.g., a burst of multiple detection events in a short period of time such as a fraction of a second or a second). The sensor may send the information to an internal processor located in the container system, where the internal processor determines whether there is a significant difference between the readings received from the burst of detection events and calculates which reading (or mean or median of the readings) to send to an external processor (e.g., located in a smartphone). Alternatively, the one or more sensors may take a number of readings and an internal processor may receive multiple readings separated by a meaningful period of time (e.g., a fraction of a minute, 1 minute, 3 minutes, 5 minutes, 10 minutes, an hour, etc.). The internal processor may calculate the difference between the time-separated readings. The computed information may be sent to the external computer elements via wired communication system (e.g., USB cord) or wireless communication system (e.g., Wi-Fi, Bluetooth, Zigbee, Near Field Communication, Infrared, ANT+, Wireless USB, Z-wave, IEEE Standard 802.15.4, IEEE Standard 802.22, RFID, or other short-range wireless communication technology, or long-range wireless communication technology). The computed information may be sent to the external computer elements upon completion of the computation by the internal processor, at certain time periods, after a certain amount of information is gathered, or only if the computed information is different relative to the most recently generated computed information.
In certain embodiments, the internal computer elements send detected information that has not been processed (e.g., is raw), rather than computed information, directly to certain external computer elements.
Whether the transmitted information is processed or raw, the external computer elements may include an application software, a database, a system memory, or a whole computer system. (For purposes of this patent application, the term “application software” means a set of one or more programs executed by a processor designed to carry out operations for a specific purpose.)
Examples of information that may be detected or calculated by the container management system includes: total value or average of how much product has been consumed or otherwise dispensed from the retainer over a certain period of time (e.g., an hour, a day, time since user started a timer, time since container system first used, a current time period, an earlier time period); how long the product is within certain temperature ranges and related averages; current status (e.g., temperature or volume) of product in retainer; current status or historical status of lid opening (e.g., open or closed); current status or historical status of retainer (e.g., tipped over or upright); number of times retainer has been refilled; current or historical geographic location of retainer or lid; how often, for how long, and where the container system is used; resources (e.g., paper, plastic, money) saved by using container system compared to using a disposable water bottle or disposable restaurant to-go cup; how strong a signal is received from an external computer system or external computer element; etc.
The detected information and/or calculated information may be stored in an external computer element (e.g., system memory possibly part of a smartphone or an application software) or an internal computer element (e.g., internal system memory possibly part of the container system) or other system location.
In addition, the detected information or computed information (which may include volume information, temperature information, and container system use information, any of which may also include the respective times of detection) may be further analyzed to provide additional statistical information. For example, a user (e.g., restaurant owner or franchise owner) may aggregate the detected information to generate statistics on how long after brewing coffee is typically served, how much coffee is served during optimal period after brewing, how long after brewing coffee is typically discarded, how much coffee is brewed and then discarded, whether and how often franchisee complies with certain guidelines for beverage service, or what times (in a day, month, or year) is coffee or water consumed and in what quantities. A user also may cross reference the volume information or volume/time information with its sales information to see whether the dispensed amounts and rates match the sales amounts and rates. Any statistical information may be organized and displayed by a selected time period, a pre-set time period such as an individual shift (e.g., 9 am to 3 pm, 3 pm to 11 pm) or business quarter, or tied to an entity such as an individual employee or manager, restaurant, franchisee, or an entire franchise. Clearly, certain embodiments may be adapted to permit a restaurant manager or franchisor to quickly obtain, calculate, and manage certain information about volume, temperature, and time measurements related to beverage dispensing or consumption.
Also, the detected information, calculated information, or statistical information also may be sent from a first external computer element such as the application software to, for example, a second external computer element such as a second application software. In one example, the detected information may be the volume of liquid in a retainer measured at a number of time points. The calculated information may be the amount of liquid that a user presumably consumed based on the detected volume measurements. The statistical information may be a comparison of the liquid consumed over a time period vs. a recommendation or goal for consumption of liquids or that liquid (e.g., water consumed vs. doctor recommended water intake or water consumption goal). Any of this information may be sent from a sensor or internal computer elements to a first application software (e.g., an application software executed by processor and configured specifically for communication with the internal computer elements), which then may be sent to a second application software (e.g., an application software configured to collect or store general health-related information from multiple sources).
The system also may permit the user to view the detected information, calculated information, or statistical information from an external computer system that may be in a remote location. (For purposes of this application, the term “remote” means spaced apart, not physically touching, but does not require any specific distance.) For example, if a user wishes to identify the temperature of contents in a retainer, the user could access their smartphone and obtain a reading via the user interface. If desired, the user could send instructions for the container management system to close the lid opening to maximize hot temperature retention or open the lid opening to permit cooling.
Detected information also may be illustrated as a representation in the display element via the user interface (the user interface is possibly part of an application software). In certain embodiments, the representation illustrates the current status (e.g., the most recently detected information), which is updated generally in real-time or as close to real-time as possible. In other embodiments, the representation is updated only at certain time intervals or illustrates a set of detected information gathered over time. A representation may illustrate information obtained from a single sensor, multiple sensors of the same type, multiple different kinds of sensors, or one or more sensors combined with one or more external data sources. Examples of a representation include a stylized numeric value of detected information, written description of detected information, or symbol or code (e.g., drawing of fire to indicate “hot” status or ice/snow to indicate “cold” status; diagram showing lid removed from retainer or lid opening as closed; picture showing relative amount of product in retainer; skull to indicate dangerous condition; clock to show time of event or current time; visual depiction of retainer or type of retainer, color coding for temperature, content type, or volume information), graph (e.g., bar graph, pie graph, line graph, etc.), or infographic (e.g., group of drawings possibly with text). Two or more representations may be created to show two or more sets of detected information.
In addition, if the detected information includes some notice-triggering information, the user interface may provide a notification such as a push notification, email, text message, alert, alarm, change in representation on display element, or other message configured to communicate that notice-triggering information to the user. Examples of notice-triggering information may include that the temperature of the retainer or retainer contents have reached a certain temperature (for example, the temperature at which the contents may have less appeal (e.g., tea or coffee is too cold) or have more appeal (e.g., tea or coffee is cool enough to minimize burn hazard); certain period of time has passed (e.g., coffee in coffeepot has sat out too long and become too bitter or over-oxidized; tea bag should be removed after ideal steeping time; replace filter element after so many refills).
The user interface also may be configured to permit the user to enter, track, or predict information related to a container system or its likely contents. For example, a user interface may permit entry of goals about hydration (e.g., drink certain number of ounces of water per day) or caffeine reduction (e.g., limit amount of coffee/tea consumed per day). A user interface may also be configured to permit entry of goal-determining information (e.g., age, weight, sex, weight loss plans, diet, lifestyle activity level, exercise activity level, home location, altitude, weather, current hydration level), which may permit the system to estimate an appropriate goal (e.g., hydration goal) for the user. Also, a user interface may be configured to permit the user to track consumption of beverages or food for dieting, hydration, blood sugar regulation, insulin regulation, or other purposes, or, for example, tracking consumption of medication, calories, or carbohydrates.
In addition, a user interface may be configurable to display predictions of when a beverage will reach a certain temperature if certain actions are taken (e.g., lid remains on retainer with drink opening closed, lid used in line with typical user use, container system put in a specific temperature environment such as outdoors or refrigeration unit).
A user interface also may include a rewards element. A rewards element may permit delivery of rewards (e.g., points or coupons) after a user has logged or the system detects certain reward-worthy-events. Examples of reward-worthy-events include achieving a certain number of refills, a certain volume of liquid consumed or otherwise dispensed, a certain number of visits to a gym, or a certain goal is achieved once or multiple times.
Embodiments of the user interface (and computer system) also may be configured to permit the user to export information to a secondary format such as a word processing document, a spreadsheet, a facsimile, an email, a text message, a social media post (e.g., Facebook post, Twitter post, Instagram post, Tumblr post, LinkedIn post), or other secondary format known in the art.
A user interface also may include a manufacturer or retail element configured to permit a user to easily contact (e.g., via email, system message, text message, webpage, etc.) a retailer or manufacturer of a container system or container management system.
Certain embodiments of the system and methods are configured to permit a user to monitor and manage one or more than one container system. Such embodiments may permit assigning a name or title to each container system in the user interface. Also, embodiments of the present invention may be configured for personal use (e.g., one user manages their personal water bottle and personal insulated mug), for family use (e.g., one user manages personal mug, spouse's tumbler, plus kids' water bottles), for restaurant or business use (e.g., one or more users manage multiple coffee pitchers/pump pots at a restaurant or business location), or for franchise use (e.g., franchise owner can track and review coffeepot volume/refill/temperature/cleaning information at various locations).
One object of certain embodiments of the present invention is to permit a user to manage one or more container systems or components thereof.
Another object of certain embodiments of the present invention is to automatically close a lid opening upon detecting certain sensor detected information. For example, certain embodiments of the present invention may be configured to automatically close a lid opening upon detecting certain spilling conditions such as the associated retainer is falling over or otherwise is in a spilling orientation. As another example, certain embodiments of the present invention may be configured to automatically close a lid opening upon detecting a temperature is above or below a certain threshold temperature or within a certain undesirable temperature range (e.g., threshold temperature or temperature range may be set by user or by manufacturer).
Another object of certain embodiments of the present invention is to automatically open a lid opening upon detecting certain sensor detected information. For example, certain embodiments of the present invention may be configured to automatically open a lid opening upon detecting certain “drinking” conditions such as the associated retainer is in a drinking orientation, the user's lips are touching a lid surface, or the temperature is within a certain temperature range or above or below a certain threshold temperature. Drinking conditions may be identified by detecting the orientation, the speed with which the orientation was reached, the speed of travel, whether the orientation is typical for drinking (e.g., if the drinking opening is off-center the user would typically orient the beverage container in such a manner that the beverage travels the least distance to reach the user's mouth), whether the a person's lip is touching a lid surface, the temperature of the beverage, other information detected by the sensors, a combination of information gathered by the sensors, or user input information.
Another object of certain embodiments of the present invention is to permit a user to identify the geographic location of a container system (for example, to facilitate finding a lost container system).
Another object of certain embodiments of the present invention is to permit a user to detect, track, record, review, and communicate information about a container system or its contents.
The present invention and its attributes and advantages will be further understood and appreciated with reference to the detailed description below of presently contemplated embodiments, taken in conjunction with the accompanying drawings.
The preferred embodiments of the invention will be described in conjunction with the appended drawings provided to illustrate and not to the limit the invention, where like designations denote like elements, and in which:
For purposes of this application, certain embodiments of the present invention described and illustrated herein are directed to container systems configured specifically to contain beverages, but the discussion is merely exemplary. The present invention is applicable to any type of container system known in the art.
Also for purposes of this application, any terms that describe relative position (e.g., “upper”, “middle” “lower”, “outer”, “inner”, “above”, “below”, “bottom”, “top”, etc.) refer to an embodiment of the invention as illustrated, but those terms do not limit the orientation in which the embodiments can be used.
The lid 300 is configured to permit dispensing or releasing the product out of the retainer space 208 without removing the lid 300 from the retainer 200. The lid 300 includes a lid body 302 having a lid shell element 304 and a lid support element 306. (An embodiment of a lid support element is shown in
The lid shell element 304 generally forms the uppermost or outermost part of the lid 300. A lid shell element 304 may include a lid side wall 314, a lid rim wall 316, and a lid top wall 318. The lid side wall 314 may include a lid input element 308 configured as a touch surface. The lid top wall 318 may have a generally frustoconical shape or a funnel shape in which the lid opening 303 is off-center and generally at the bottom of the funnel shape.
As shown in
In the illustrated embodiment, the upper inner frame element 322A is configured to support one or more components of an open/close lid opening assembly 315. The illustrated embodiment of an open/close lid opening assembly 315 (also shown apart from the upper inner frame element 322A in
To unblock the drink aperture (or other lid opening), the motor 326 is activated (e.g., by a lid input element, push button, or computer system) to rotate the crank 328, causing the actuator element 330 to move, for example, upward. The upward movement of the actuator element 330 causes the actuated side 334 of the lever arm assembly to also move upward. When the actuated side 334 moves upward, the aperture blocking side 338 is lowered such that it is no longer physically blocking the drink aperture or the entrance to the product tube 350 leading to the drink aperture. In addition, the body of the illustrated actuator element 330 is sized and shaped, possibly with a vent indentation 333, such that when the actuator element 330 is positioned to unblock the drink aperture, a vent path is open to permit release of pressure from the retainer space during drinking or pouring.
In certain embodiments, the crank 328 includes one or more crank magnets 329 shown in
In certain embodiments, the open/close lid opening assembly 315 may be configured to partially block the lid opening such that the flow rate of the beverage may be controlled or to completely block the lid opening such that beverage is generally completely impeded from passing through the lid opening.
As shown in
Also, adjacent to or affixed to the integrated circuit board 342 is a user input receiver 344, which is disposed to sense any input from the lid input element 308 on the lid side wall 314. In the illustrated embodiment, the user input receiver 344 is an upper portion of a flexible printed circuit board. In addition, a light pipe element 345 may be disposed to enclose or position a display element such as an LED such that the user can see, for example, whether the LED is on or off or a certain color from outside of the lid 300. The color or on/off/blinking status of an LED may indicate: whether the container management system is on or off; whether the lid opening is blocked or unblocked; whether any information is being detected by a sensor; whether certain information has been detected by a sensor (e.g., low volume of liquid in retainer or temperature is out of the comfort/safety zone for consumption); whether the open/close lid opening assembly is locked (e.g., cannot change position) or unlocked (e.g., can change position automatically upon detecting spill conditions or drinking conditions); whether there is a notification present (e.g., near a water fountain, met or near meeting a goal, reminder to refill or consume more/less); whether there is a warning (e.g., too hot to consume, bad weather approaching); whether the container system is has sufficient power or low battery; whether the container system is connected to an external computer system; or some other information.
The lower inner frame element 322B supports a lower portion of the flexible printed circuit board which may be configured to operate as a volume sensor 346. The lower inner frame element 322B and the volume sensor 346 are sized and shaped such that when the lid 300 is connected to the retainer 200, at least some portion of the volume sensor 346 extends into the retainer space 208. In certain embodiments, the volume sensor 346, lower inner frame element 322B and lower outer frame element 324B may be configured to extend into the bottommost portion of the retainer space 208 or may be configured to extend only into the middle or upper portions of the retainer space 208. More specifically, the lower inner frame element 322B or lower outer frame element 324B may be configured to extend through one quarter, one half, three-quarters, five-sixths, or the entire retainer space 208 by height.
In the illustrated embodiment, the interior lid compartment 348 is generally formed by two pieces secured together, but in other embodiments, an interior lid compartment may be formed by a single piece construction (which may possibly include a closeable opening to permit items to be inserted into the interior lid compartment, but the compartment still sealed or generally water-tight); a three-piece construction or alternative construction. Alternatively, a retainer may include an interior retainer compartment (not shown) configured to store internal computer elements, a sensor, or other components and possibly may be configured to be water-tight.
Also shown in
As shown in
The system and methods of the present invention may include one or more additional sensors, each configured to detect a characteristic or event related to the retainer, lid, or contents of the retainer. For example, an orientation sensor, such as an accelerometer, may be incorporated in or by the flexible printed circuit board or the integrated circuit board 342.
The container management system 50 also may include a location sensor configured to detect the geographic location of the container system. Examples of a location sensor include a global positioning system (GPS), other satellite navigation system, other triangulation systems, compass, or magnetic field sensor. In certain embodiments such location sensor may be a system application run by the computer system 500 rather than a separable component. A location sensor may permit the system 50 to detect (and alert the user) if and when the container system 100 is being carried away or left behind relative to a computer system 500 (e.g., a smartphone). A location sensor also may permit a user to identify a location of their container system 100 possibly via a map element in the user interface.
Certain embodiments of the system and methods of the present invention include one or more computer elements 502 that may or may not form a full computer system 500. An example of a computer system 500 according to the present invention is illustrated in
The system bus 590 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, a switched fabric, point-to-point connections, and a local bus using any of a variety of bus architectures. The system memory 520 may also be referred to as simply the memory, and includes read only memory (ROM) and random access memory (RAM). A basic input/output system (BIOS) 572, which may contain basic routines that help to transfer information between elements within the computer system 500 such as during start-up may be stored in ROM. The computer system 500 may include a hard disk drive 520A for reading from and writing to a persistent memory such as a hard disk (not shown) and an optical disk drive 530 for reading from or writing to a removable optical disk such as a CD ROM, DVD, or other optical medium.
The hard disk drive 520A and optical disk drive 530 are connected to the system bus 590. The drives and their associated computer-readable medium provide nonvolatile storage of computer-readable instructions, data structures, program engines, and other data for the computer system 500. It should be appreciated by those skilled in the art that any type of transitory and non-transitory computer-readable medium, which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, random access memories (RAMs), read only memories (ROMs), and the like, may be used in the example operating environment. In various embodiments, the system memory 520 or hard drive disk 520A store threshold data for various parameters, states, or conditions of the container system 100. By way of example, the threshold data may relate to the pressure, temperature, angle of rotation, and position, among others, of the container system 100 and any contents therein. The threshold data may be retrieved and/or modified by one or more processor(s) 510 of the computer system 500.
The computer system 500 also may include a network interface element 550 such that it can send and receive information via Wi-Fi, Bluetooth, Infrared, ZigBee, Near Field Communication, ANT+, Wireless USB, Z-wave, IEEE Standard 802.15.4, IEEE Standard 802.22, RFID), local area networks, wide area networks, intranets, or other short-range wireless communication technology or long-range wireless communication technology. More specifically, a network interface 550 may provide a two-way data communication coupling via a network link. For example, a network interface 550 may be an integrated services digital network (ISDN) card or a modem, a local area network (LAN) card, or a cable modem or wireless interface. In any such implementation, the network interface 550 sends and receives electrical, electromagnetic, or optical signals which carry digital data streams representing various types of information.
A number of program engines may be stored on the hard disk, optical disk, or elsewhere, including an operating system 582, a system application 584, and one or more other application program modules 586. A user may enter commands and information into the computer system 500 through input devices such as a keyboard and pointing device (e.g., mouse, mini-mouse, mole, trackball, touchpad, trackpoint, touchscreen, stylus, dance pad, remote controller, etc.), any of which may be connected to the USB or Serial Port 540 or may be communicate wirelessly. These and other input devices are often connected to the processor 510 through the USB or serial port interface 540 that is coupled to the system bus 590, but may be connected by other interfaces, such as a parallel port. A monitor, touchscreen, LED device, or other type of display element may also be connected to the system bus 590 via an interface (not shown). In addition to the monitor, computers may include other peripheral output devices (not shown), such as speakers, printers, facsimile machines, game controller (e.g., joystick, wand, etc.), microphone, web camera, other type of camera, etc.
The display element may be configured to show or display one or more user interfaces 700, an example of which is illustrated in
Certain of the illustrations in
The user interface 700 also may include a system identification symbol 706. The system identification symbol 706 may include a temperature reading element 706A, an “ounces dispensed or consumed” element 706B, or other elements. The system identification symbol 706 also may be configured as a volume representation 704J, such that the fill line 705A represents the relative amount of liquid in the retainer.
As illustrated in
A lid shell element 304 may include a lid side wall 314, a lid base cover receiving wall 380, and a lid top wall 318. The lid side wall 314 may include an indented section 382 configured to protect the USB port 309. The lid top wall 318 may have a generally linear shape.
The lid shell element 304 may include a hinged lid base cover 370 and a lid base 372. Such embodiments may include a pivot element 371 configured to pass through a cover pivot element 371A of the hinged base cover 370 and a base pivot element 371B of the lid base 372. A pivot element 371 may be, for example, a pin. The hinge also may include a cover biasing element, such as an o-ring, configured to bias the lid base cover toward an open position if it is not latched to the lid base 372. In addition, the hinge also may be the axis connection for a handle 373.
The hinged lid base cover 370 may be configured to be released into an open position or latched into a closed position by a mechanical push button assembly 360. As shown in
The mechanical push button assembly 360 optionally may include a button lock 365 configured to prohibit the button 368 from releasing the lid base cover 370 from the lid base 372 when in the engaged position as shown in
As shown in
The inner frame element 322 may support a lower portion of the flexible printed circuit board which may be configured to operate as a volume sensor (not shown). The inner frame element 322 and the volume sensor 346 are sized and shaped such that when the lid 300 is connected to the retainer 200, at least some portion of the volume sensor extends into the retainer space 208. In certain embodiments, the volume sensor 346 may be configured to extend into the bottommost portion of the retainer space 208 or may be configured to extend only into the middle or upper portions of the retainer space 208.
The upper outer frame element 324A may be generally disc shaped as shown in
Certain embodiments of the lid base cover 370 may include a sealing element opening configured to receive an aperture sealing element 392 shaped like a mushroom and positioned to completely or partially seal the drink aperture when the lid base cover 370 is latched to the lid base 372. The aperture sealing element 392 may be suspended from a sealing element opening of the lid base cover 370.
Certain embodiments of the present invention may be configured to quickly signal the user about the contents of the retainer. For example, a certain representation may be displayed or a certain component may be different (e.g., different color or shape) to designate whether the retainer is carrying decaffeinated or caffeinated coffee.
While the disclosure is susceptible to various modifications and alternative forms, specific exemplary embodiments of the present invention have been shown by way of example in the drawings and have been described in detail. It should be understood, however, that there is no intent to limit the disclosure to the particular embodiments disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the scope of the disclosure as defined by the appended claims.
This application claims the benefit of U.S. Provisional Application No. 61/901,133 filed Nov. 7, 2013, U.S. Design application No. 29/486,557 filed Mar. 31, 2014, U.S. Design application No. 29/486,563 filed Mar. 31, 2014, U.S. Provisional Application No. 61/974,230 filed Apr. 2, 2014, U.S. Provisional Application No. 62/003,409 filed May 27, 2014, and U.S. Design application Ser. No. 29/499,405 filed Aug. 14, 2014, each of which is incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| D987597 | Habig | Jan 1911 | |
| 2187558 | Kushima | Jan 1940 | A |
| 2746265 | Mills | May 1956 | A |
| D213292 | Arsenault et al. | Feb 1969 | S |
| D246600 | Kurata | Dec 1977 | S |
| D281581 | MacEwen | Dec 1985 | S |
| 5318197 | Martindale et al. | Jun 1994 | A |
| 5379916 | Martindale et al. | Jan 1995 | A |
| 5495793 | Muis et al. | Mar 1996 | A |
| D374399 | Neveras et al. | Oct 1996 | S |
| 5678925 | Garmaise et al. | Oct 1997 | A |
| D403964 | Jansen | Jan 1999 | S |
| 5881868 | Soyak et al. | Mar 1999 | A |
| 6036055 | Mogadam et al. | Mar 2000 | A |
| D425618 | Niermann et al. | May 2000 | S |
| 6119888 | Goto et al. | Sep 2000 | A |
| D441288 | Pillers et al. | May 2001 | S |
| D448294 | Alscher et al. | Sep 2001 | S |
| D451023 | Kitamura et al. | Nov 2001 | S |
| 6857755 | Lewis | Feb 2005 | B1 |
| 6859745 | Carr et al. | Feb 2005 | B2 |
| 6903874 | Karterman | Jun 2005 | B1 |
| 7017807 | Kipp et al. | Mar 2006 | B2 |
| 71048179 | Claessens et al. | May 2006 | |
| 7061382 | Claessens et al. | Jun 2006 | B2 |
| 7088258 | Morrison | Aug 2006 | B2 |
| D528862 | Li | Sep 2006 | S |
| 7109863 | Morrison | Sep 2006 | B2 |
| 7126479 | Claessens et al. | Oct 2006 | B2 |
| 7183936 | Ritson | Feb 2007 | B2 |
| 75189134 | Nugent et al. | Mar 2007 | |
| 7267250 | Rudduck et al. | Sep 2007 | B2 |
| 7336194 | Hillman et al. | Feb 2008 | B2 |
| 7364089 | Claessens et al. | Apr 2008 | B2 |
| D573017 | Henderson | Jul 2008 | S |
| D574507 | Muir et al. | Aug 2008 | S |
| 7417417 | Williams et al. | Aug 2008 | B2 |
| D587581 | DeMarco et al. | Mar 2009 | S |
| 7501933 | Rousso et al. | Mar 2009 | B2 |
| D596440 | Rothberg et al. | Jul 2009 | S |
| D596460 | Nezu | Jul 2009 | S |
| D596944 | Mueller et al. | Jul 2009 | S |
| D597838 | Stuart | Aug 2009 | S |
| 7573395 | Morrison et al. | Aug 2009 | B2 |
| 7613431 | Brand | Nov 2009 | B2 |
| D608640 | Carreno | Jan 2010 | S |
| 7712364 | Radhakrishnan et al. | May 2010 | B2 |
| 7740368 | Chiang | Jun 2010 | B2 |
| RE41605 | Karterman | Aug 2010 | E |
| 7766545 | Salkeld | Aug 2010 | B2 |
| D623473 | Chen | Sep 2010 | S |
| 7798373 | Wroblewski et al. | Sep 2010 | B1 |
| 7888898 | Wilkerson | Feb 2011 | B2 |
| 7933733 | Ashrafzadeh et al. | Apr 2011 | B2 |
| D640505 | George | Jun 2011 | S |
| 7954711 | Adstedt et al. | Jun 2011 | B2 |
| D641591 | Tsukida | Jul 2011 | S |
| 8011816 | Janda | Sep 2011 | B1 |
| D655134 | Gilbert | Mar 2012 | S |
| D655580 | Kotani | Mar 2012 | S |
| D655983 | Cozzolino et al. | Mar 2012 | S |
| D658443 | Chiu et al. | May 2012 | S |
| D660081 | Gilbert | May 2012 | S |
| 8172454 | Choi | May 2012 | B2 |
| D666490 | Leon | Sep 2012 | S |
| D668116 | Eyal | Oct 2012 | S |
| 8286821 | Mejia et al. | Oct 2012 | B2 |
| 8336665 | Saunders | Dec 2012 | B1 |
| D675059 | Carreno | Jan 2013 | S |
| 8357846 | Strobel et al. | Jan 2013 | B2 |
| D675865 | Wahl | Feb 2013 | S |
| 8368539 | Adstedt et al. | Feb 2013 | B2 |
| 8378830 | Moran | Feb 2013 | B2 |
| 8429965 | Radhakrishnan et al. | Apr 2013 | B2 |
| 8432249 | Bailey-VanKuren et al. | Apr 2013 | B2 |
| 8453878 | Palmquist | Jun 2013 | B2 |
| 8477029 | Ashrafzadeh et al. | Jul 2013 | B2 |
| 8550288 | Briar et al. | Oct 2013 | B2 |
| 8560403 | Adstedt et al. | Oct 2013 | B2 |
| 8590743 | Beland et al. | Nov 2013 | B2 |
| 8608026 | Temko et al. | Dec 2013 | B1 |
| 8618448 | Alexander | Dec 2013 | B2 |
| D700513 | Carsrud et al. | Mar 2014 | S |
| D704053 | Kim | May 2014 | S |
| D707557 | Corradini et al. | Jun 2014 | S |
| D707558 | Corradini et al. | Jun 2014 | S |
| D715143 | Hewitt et al. | Oct 2014 | S |
| D718626 | Lane | Dec 2014 | S |
| D720574 | Boroski | Jan 2015 | S |
| D721920 | Coon et al. | Feb 2015 | S |
| D731240 | Bell et al. | Jun 2015 | S |
| 20010036124 | Rubenstein | Nov 2001 | A1 |
| 20040123620 | Porter | Jul 2004 | A1 |
| 20050035011 | McRobbie | Feb 2005 | A1 |
| 20050121431 | Yuen | Jun 2005 | A1 |
| 20050194402 | Morrison | Sep 2005 | A1 |
| 20060139928 | Griffiths et al. | Jun 2006 | A1 |
| 20070125162 | Ghazi et al. | Jun 2007 | A1 |
| 20070181585 | Lane | Aug 2007 | A1 |
| 20080195251 | Milner | Aug 2008 | A1 |
| 20080296191 | Ransch | Dec 2008 | A1 |
| 20090045959 | Adstedt et al. | Feb 2009 | A1 |
| 20090139324 | Morimoto et al. | Jun 2009 | A1 |
| 20090159552 | Cano-Pey et al. | Jun 2009 | A1 |
| 20100025267 | Brand | Feb 2010 | A1 |
| 20100045705 | Vertegaal et al. | Feb 2010 | A1 |
| 20100101317 | Ashrafzadeh et al. | Apr 2010 | A1 |
| 20100102930 | McCoy | Apr 2010 | A1 |
| 20100102967 | Lee et al. | Apr 2010 | A1 |
| 20100106515 | McCoy | Apr 2010 | A1 |
| 20100106521 | Ashrafzadeh et al. | Apr 2010 | A1 |
| 20100106624 | Ashrafzadeh et al. | Apr 2010 | A1 |
| 20100106625 | McCoy | Apr 2010 | A1 |
| 20100106626 | Ashrafzadeh et al. | Apr 2010 | A1 |
| 20100156614 | Adstedt et al. | Jun 2010 | A1 |
| 20100182518 | Kirmse et al. | Jul 2010 | A1 |
| 20100200602 | Chan | Aug 2010 | A1 |
| 20110050431 | Hood et al. | Mar 2011 | A1 |
| 20110053283 | Hood et al. | Mar 2011 | A1 |
| 20110108570 | Jarisch | May 2011 | A1 |
| 20110153398 | Tjhai et al. | Jun 2011 | A1 |
| 20110180563 | Fitchett et al. | Jul 2011 | A1 |
| 20110253715 | Phaneuf et al. | Oct 2011 | A1 |
| 20110298582 | August et al. | Dec 2011 | A1 |
| 20120074154 | Ming Ki Gordon et al. | Mar 2012 | A1 |
| 20120103562 | Alexander | May 2012 | A1 |
| 20120187075 | El-Saden | Jul 2012 | A1 |
| 20120217244 | Phaneuf et al. | Aug 2012 | A1 |
| 20120222339 | Dubinski | Sep 2012 | A1 |
| 20120228388 | Kuo et al. | Sep 2012 | A1 |
| 20120293332 | Rosenfeld | Nov 2012 | A1 |
| 20130062232 | Saunders | Mar 2013 | A1 |
| 20130105434 | Levy | May 2013 | A1 |
| 20130115343 | Reyhanloo | May 2013 | A1 |
| 20130127748 | Vertegaal et al. | May 2013 | A1 |
| 20130145324 | Kelly et al. | Jun 2013 | A1 |
| 20130228584 | Khatchaturian | Sep 2013 | A1 |
| 20130273843 | Shimota et al. | Oct 2013 | A1 |
| 20130307683 | Greenberg et al. | Nov 2013 | A1 |
| 20130319966 | Lane | Dec 2013 | A1 |
| 20130342316 | Ghaffari et al. | Dec 2013 | A1 |
| 20130346169 | Tjhai et al. | Dec 2013 | A1 |
| 20140008443 | Chang et al. | Jan 2014 | A1 |
| 20140042178 | Brannock | Feb 2014 | A1 |
| 20140042183 | Beland et al. | Feb 2014 | A1 |
| 20140053944 | Wang | Feb 2014 | A1 |
| 20140059133 | Wang | Feb 2014 | A1 |
| 20140059581 | Wang | Feb 2014 | A1 |
| 20140059621 | Wang | Feb 2014 | A1 |
| 20140152323 | Kumar et al. | Jun 2014 | A1 |
| 20140303790 | Huang et al. | Oct 2014 | A1 |
| 20140311239 | Marjanovic et al. | Oct 2014 | A1 |
| 20140332433 | Lyall, III et al. | Nov 2014 | A1 |
| 20150024349 | Bischoff et al. | Jan 2015 | A1 |
| 20150309611 | Vertegaal et al. | Oct 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 2005276947 | Mar 2006 | AU |
| 2002259233 | Dec 2007 | AU |
| 2002234439 | Jun 2008 | AU |
| 2009235936 | Oct 2009 | AU |
| 2003217045 AA | Jan 2010 | AU |
| 2009273375 | Apr 2010 | AU |
| 2010271093 | Jan 2011 | AU |
| 2008251929 | Sep 2012 | AU |
| 2012265589 | Mar 2013 | AU |
| 2 568 627 | Nov 2006 | CA |
| 2 583 744 | Apr 2007 | CA |
| 2 440 089 | Nov 2008 | CA |
| 2 440 089 | Nov 2008 | CA |
| 2 686 553 | Nov 2009 | CA |
| 2 731 423 | Jan 2010 | CA |
| 2 440 728 | May 2011 | CA |
| 2 787 831 | Aug 2011 | CA |
| 2800615 | Oct 2011 | CA |
| 2 836 544 | Nov 2012 | CA |
| 2 767 741 | Jan 2013 | CA |
| 2 788 161 | Mar 2013 | CA |
| 2 816 690 | Apr 2013 | CA |
| 2 542 043 | May 2013 | CA |
| 2613150 | Apr 2004 | CN |
| 200963087 | Oct 2007 | CN |
| 102238891 | Nov 2011 | CN |
| 103445617 | Dec 2013 | CN |
| 0 627 186 | Dec 1997 | EP |
| 1 373 084 | Jan 2004 | EP |
| 1 487 713 | Dec 2004 | EP |
| 1 591 371 | Nov 2005 | EP |
| 1 636 111 | Mar 2006 | EP |
| 1 665 135 | Jun 2006 | EP |
| 1 738 336 | Jan 2007 | EP |
| 1 825 233 | Aug 2007 | EP |
| 1 388 20 | Oct 2011 | EP |
| 2 511 857 | Oct 2012 | EP |
| 2 558 381 | Feb 2013 | EP |
| 2 306 872 | May 2013 | EP |
| 2 599 732 | Jun 2013 | EP |
| 2 659 808 | Jun 2013 | EP |
| 2 619 529 | Jul 2013 | EP |
| 2 645 298 | Oct 2013 | EP |
| 2 662 304 | Nov 2013 | EP |
| S62298687 | Dec 1987 | JP |
| 2012-501278 | Jan 2012 | JP |
| 2013-071745 | Apr 2013 | JP |
| 2013-107679 | Jun 2013 | JP |
| 2008140732 | Nov 2008 | WO |
| 2010009975 | Jan 2010 | WO |
| 2012040461 | Mar 2012 | WO |
| 2012061527 | May 2012 | WO |
| 2012102759 | Aug 2012 | WO |
| 2012162059 | Nov 2012 | WO |
| 2012175693 | Dec 2012 | WO |
| 2013059454 | Apr 2013 | WO |
| 2013079141 | Jun 2013 | WO |
| 2013085865 | Jun 2013 | WO |
| 2013138412 | Sep 2013 | WO |
| 2013143923 | Oct 2013 | WO |
| 2013164110 | Nov 2013 | WO |
| Entry |
|---|
| PCT/US14/64374 International Search Report and Written Opinion dated Mar. 26, 2015 (14 pages). |
| Bootic. Thermos. Oct. 29, 2013 [online], [site visited Feb. 5, 2015]. Available from Internet, <URL:http://www.bootic.com/thermos/home-and-garden/kitchen-and-dining/tableware/drinkware/thermos-nissan-16-ounce-stainless-steel-backpack-bottle>. |
| YouTube. Themos Nissan 16-Ounce Stainless-Steel Backpack Bottle Review. Feb. 23, 2013 [online], [site visited Feb. 5, 2015]. Available from Internet, <URL:https://www.youtube.com/watch?v=8PnmUihk_uQ>. |
| CN 2014800612958-1 Office Action with translation; Jun. 2, 2017 (28 pages). |
| CN 2014800612958-1 Office Action with translation; Jan 23, 2018 (23 pages). |
| SG 11201603605X Written Opinion; Feb. 14, 2014; (6 pages). |
| CL 201601087 Office Action; 2016-05-056; (15 pages). |
| AU 2014346731 Examination Report; Jun. 30, 2017; (4 pages). |
| CA 2928946 Examination Report; Oct. 18, 2017; (4 pages). |
| EP 14860224.6 Extended Search Report; Aug. 1, 2017; (8 pages). |
| EP 14860224.6 Invitation Pursuant To Rule 62a(1)EPC; Mar. 15, 2017; (2 pages). |
| You Tube. Thermos Nissan 16-Ounce Stainless-Steel Backpack Bottle Reivew; Feb 23, 2013 [online]; [site visited Feb. 5, 2015]; https://www.youtube.com/watch?v=8PnmUihk_uQ>. |
| U.S. Appl. No. 29/536,881 Office Action; dated May 20, 2016; (13 pages). |
| “Brian's Thermos”—STL Solidworks—3D CAD model; found online Aug. 10, 2015 at grabcad.com; page dated Jan. 25, 2012; retrieved from https://grabcad.com/library/brian-s-thermos. |
| Thermos Connected Hydration Water Bottle with Smart Lid; www.Target.com; 5 pages; found online May 16, 2016 at http://www.target.com/p/thermos-connected-hydration-bottle-with-smart-lid-teal/-/A-24010647. |
| CA 2928946 Office Action Issued Sep. 7, 2018; (5 pages). |
| JP 2016-528194 Office Action dated Nov. 27, 2018, with translation; (20 pages). |
| EP 14860224.6 Office Action dated Sep. 27, 2018; (4 pages). |
| KR 10-2016-7014919 Office Action dated Jul. 31, 2018, with translation; (77 pages). |
| “Thermal Freshtrac(TM) (TFT) 64 Ounce Thermal Dispensers”; Models: TFT64, TFT64D; Wilbur Curtis; accessed Sep. 4, 2014; (2 pages). |
| “Stay hydrated with the BluFit smart water bottle and app”; Steven Sande @stevensande; accessed Oct. 15, 2015; (5 pages). |
| “H2OPal Hydration Tracker”; by H2OPal; https://www.amazon.com/H20Pal-2AETMDOH20-B1-HydraTracker/dp/ B018YEAQCA/ref=sr_1_1?ie=UTF8&qid=1479412993&sr=8-1&keywords=h2Opal; accessed Nov. 17, 2016; (8 pages). |
| “Smart” water bottle startup launches crowdfunding campaign; Katharine Grayson; TECHFLASH; Jun. 1, 2015; 2:55pm CDT; accessed Jun. 4, 2015; (5 pages). |
| Hydracoach(TM) hydradation monitors; accessed Oct. 15, 2016. |
| “Meet IQhydr8;”; American Diabetes Association; http://www.iqhydr8.com/; accessed Nov. 13, 2014; (4 pages). |
| “Johnnie Walker Smart Bottle Debuts At Mobile World Congress”; Jennifer Hicks (http://www.forbes.com/sites/jenniferhicks/); TECH (/TECHNOLOGY); Mar. 2, 2015 @ 12:18 PM; accessed Jul. 13, 2015; (6 pages). |
| “Log how much water you're drinking with the Oaxis smart bottle”; Aloysius Low; Jun. 2, 2015 5:11 AM PDT; accessed Jun. 11, 2015; (4 pages). |
| Smart Design partners with Gatorade; Announcement: Jun. 12, 2014; accessed Jul. 16, 2015; (5 pages). |
| “Trago—The World's First Smart Water Bottle”; created by Jac & Davis Saltzgiver; Kickstarter; accessed Jul. 14, 2015; (26 pages). |
| Mark One Pryme Vessyl Personal Hydration Tracker; (https://www.amazon.com/Mark-One-Vessyl-Personal-Hydration/dp/B01HMU687Y); accessed Jan. 2, 2019; (7 pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20150122688 A1 | May 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61901133 | Nov 2013 | US | |
| 61974230 | Apr 2014 | US | |
| 62003409 | May 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 29486557 | Mar 2014 | US |
| Child | 14534800 | US | |
| Parent | 29486563 | Mar 2014 | US |
| Child | 29486557 | US | |
| Parent | 29499405 | Aug 2014 | US |
| Child | 29486563 | US |
