The disclosure relates generally to sensing, and, more particularly, to an apparatus, system, and method of monitoring content levels and indicating a need for replenishment.
It is well understood that various types of contents, such as solids and liquids, may be carried within containers designed to dispense those contents over extended time periods in discreet doses. By way of nonlimiting example, detergent for use in a washing machine is often provided in liquid form, and a large bottle, such as having a spigot or other output type to allow for the dispensing of the detergent outwardly from the bottle, enables dispensing of that dose of detergent into a load of laundry within the washer. Similarly, such as in an office environment, a large bottle is used to provide water at a “water cooler”, and the water is dispensed responsive to independent actuations of a spigot.
In general, contents ultimately placed within the container may be tracked, in bulk, prior to delivery to or purchase by the ultimate consumer. For example, bulk tracking may be performed on farmed goods as they are farmed, and as they are shipped for distribution; warehoused solids may be tracked by production date, such as by UPC code or the like, and/or such as by warehoused pallet, and so on; once the goods reach a sales center, such as a grocery store, they may be tracked, such as by UPC code or the like, from an inventory perspective; but, once the contents reach the consumer and/or are otherwise placed into a container, such as for consumption, or when the contents are consumed from a purchased container, there are no longer readily available tracking methodologies at present.
However, in embodiments such as the aforementioned, it is often the case that, for a user to monitor how much content remains in the container, the user must periodically shake, lift, or otherwise manipulate the container to allow for a qualified guess by the user as to how much content remains therein. Further, there is historically no methodology whereby proper dosing for use of the content, such as per load dosing into a washing machine, may be readily assessed. Unfortunately, in a washing machine embodiment by way of example, too little soap may cause an inadequate level of cleaning of clothes placed within the washing machine, and too much soap may cause over-sudsing, which may damage the washing machine or the laundry area. Yet further, there is presently no mechanism whereby a seller of a containers having consumable contents, such as dishwashing or laundry detergent, or water cooler bottles, can assess a consumer's need for additional contents.
Therefore, the need exists for an apparatus, system, and method of monitoring content levels within a consumable container, such as a bottle or box, and of automatically indicating (herein referred to as “autoreplenishment”), such as to at least one of a consumer and/or a seller of the contents, when the need for additional contents and/or a consumable containing the contents occurs.
The embodiments are and include at least an apparatus, system and method for providing a consumable level monitor for association with a content-filled consumable. The embodiments may include a sensing module suitable to sense the consumable level; and a communications module suitable for receiving the consumable level from the sensing module, and for communicating the consumable level to a user.
The disclosure is illustrated by way of example and not limitation in the accompanying drawings, in which like references indicate similar elements, and in which:
The figures and descriptions provided herein may have been simplified to illustrate aspects that are relevant for a clear understanding of the herein described devices, systems, and methods, while eliminating, for the purpose of clarity, other aspects that may be found in typical similar devices, systems, and methods. Those of ordinary skill may recognize that other elements and/or operations may be desirable and/or necessary to implement the devices, systems, and methods described herein. But because such elements and operations are well known in the art, and because they do not facilitate a better understanding of the present disclosure, a discussion of such elements and operations may not be provided herein. However, the present disclosure is deemed to inherently include all such elements, variations, and modifications to the described aspects that would be known to those of ordinary skill in the art.
The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. As used herein, the singular forms “a”, “an” and “the” may be intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms “comprises,” “comprising,” “including,” and “having,” are inclusive and therefore specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring their performance in the particular order discussed or illustrated, unless specifically identified as an order of performance. It is also to be understood that additional or alternative steps may be employed.
When an element or layer is referred to as being “on”, “engaged to”, “connected to” or “coupled to” another element or layer, it may be directly on, engaged, connected or coupled to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being “directly on,” “directly engaged to”, “directly connected to” or “directly coupled to” another element or layer, there may be no intervening elements or layers present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., “between” versus “directly between,” “adjacent” versus “directly adjacent,” etc.). As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
Although the terms first, second, third, etc., may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms may be only used to distinguish one element, component, region, layer or section from another element, component, region, layer or section. Terms such as “first,” “second,” and other numerical terms when used herein do not imply a sequence or order unless clearly indicated by the context. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the exemplary embodiments.
Processor-implemented modules, systems and methods of use are disclosed herein that may provide networked access to a plurality of types of digital content, including but not limited to video, image, text, audio, metadata, algorithms, interactive and document content, and which track, deliver, manipulate, transform and report the accessed content. Described embodiments of these modules, systems and methods are intended to be exemplary and not limiting. As such, it is contemplated that the herein described systems and methods may be adapted and may be extended to provide enhancements and/or additions to the exemplary modules, systems and methods described. The disclosure is thus intended to include all such extensions.
Furthermore, it will be understood that the term “module” as used herein does not limit the functionality to particular physical modules, but may include any number of tangibly-embodied software and/or hardware components having a transformative effect on at least a portion of a system. In general, a computer program product in accordance with one embodiment comprises a tangible computer usable medium (e.g., standard RAM, an optical disc, a USB drive, or the like) having computer-readable program code embodied therein, wherein the computer-readable program code is adapted to be executed by a processor (which may work in connection with an operating system) to implement one or more functions and methods as described below. In this regard, the program code may be implemented in any desired language, and may be implemented as machine code, assembly code, byte code, interpretable source code or the like (e.g., via C, C++, C#, Java, Actionscript, Objective-C, Javascript, CSS, XML, etc.).
Embodiments may include a liquid level monitoring apparatus, system, and method, as well as an auto replenishment apparatus, system, and method for liquids typically contained within a consumable, such as a bottle, for which monitoring of the level of those liquids has not historically occurred. The embodiments may include a stand-alone dispenser, such as a base having a liquid output, that is distinct from the one or more liquid consumables, and which may include one or more printed circuit boards, firmware, network communication capabilities, user interfaces and indicators, provided power, and a spigot for dispensing liquid from a consumable associated with the dispenser. The embodiments of the dispenser may be associated with one or more consumables or similar packages, such as may be formed of plastic, glass, paper, or pulp, and which may have associated there with one or more electronic labels having sensing capabilities.
Embodiments may also include a solids level monitoring apparatus, system, and method, as well as an auto replenishment apparatus, system, and method for solids typically within a container, for which monitoring of the level of those solids has not historically occurred. The embodiments may include a stand-alone base that is distinct from the one or more containers, and which may include one or more printed circuit boards, firmware, network communication capabilities, user interfaces and indicators, provided power, and/or a dispenser for dispensing solids from a container associated with the base. The embodiments of the base may be associated with one or more types of containers, such as may be formed of plastic, cardboard, or glass, and may extend upward into contact, in part or in whole, with one or more aspects of the container placed into the base, such that the container is brought into contact with aspects of the base in order that the functionality discussed herein may be provided. Of note, the container may have associated there with one or more aspects, such as electronic labels, to provide the functionality herein, either discretely or in conjunction with the encompassing and electronic aspects of the base, as described throughout.
That is, as used herein, the disclosed systems and methods may include two aspects, as discussed throughout. More particularly, the first aspect may be a “consumable”, such as the food and liquids containers discussed herein, which may include a disposable good comprised of a package which includes therein a solid or liquid for consumption by user. The consumable may be rigid or flexible, and may be or include, by way of non-limiting example, a bottle, cartridge, bag, jar, such as with a closure, a disposable dispenser, a box, such as may be formed of cardboard, or the like.
Also included within the system may be the durable aspect such as the dispensing units discussed throughout, by way of example, such as may be physically and/or communicatively associated with a consumable. The durable may, as referenced above, also include communication capabilities. Unlike the consumable, the durable aspect may have a usable life that spans the exhaustion of a plurality of consumables, such as over a predetermined time period, such as over the course of a month, a year, or the like.
Further, included in the embodiments may be: cloud based storage and communication with one or more of the dispensers; one or more smartphone apps for communication with the one or more dispensers and/or the cloud based communication site; and an analytics dashboard, which may be app and/or web-based, such as may be used by a seller of the solid or liquid contents and/or the containers thereof. As used herein, a “liquid level”, “solids level”, or “contents level” monitored in the disclosed apparatuses, systems and methods is indicative of the amount of contents remaining in a consumable associated with aspects of the embodiments; a “dose” is an amount of contents dispensed, such as from the liquid output/spigot/crank, for a given purpose; and an “auto replenishment” may occur when the contents level in the consumable reaches a point at which a reorder is required.
More particularly, a sensing microprocessor, and the requisite processing power, may be resident in the durable dispenser. Because the device must sense content levels inside a consumable, the consumable may have associated there with, either aftermarket or following manufacture, and by direct printing or in-label, a smart label having sensing, such as conductive or photosensitive strips or connective discrete sensors, covering some portion of the consumable on at least one side thereof. These conductive traces may become communicative with the sensing system upon, and only upon, installation of the consumable into the durable dispenser. Needless to say, a snug electromechanical connection with the dispenser may be provided for the consumable, and/or for variably sized consumables, via any known method. This connection may occur only upon insertion of the consumable into the dispenser, such as by a spring-loaded connector that snugs around a bottleneck, and/or by using a keying mechanism, such as a slot, associated with the consumable to ensure insertion of the consumable at a proper orientation into the dispenser to allow for an electromechanical connection, or using other like methods, by way of example.
Thereby, the embodiments may provide a sensing solution that “wakes up” only when the consumable is plugged into a durable, permanent or semi-permanent, dispenser. Moreover, the embodiments allow for enhanced convenience and control by the user, such as by communicatively associating with the circuitry referenced herein of one or more apps having resident therein settings that may be adjusted by a user, such as for dosing of the contents within the consumable. Further, the communication capabilities disclosed herein may allow for enhanced value to sellers, such as by increasing brand loyalty, reorder frequency, and by providing experiential use data, by way of non-limiting example. In turn, it will be understood in light of the disclosed embodiments that the value to a user may be further enhanced, such as by providing for the offering of discounts from a brand monitoring usage levels to a high-volume user, or the like.
The consumable disclosed in the embodiments may be of any suitable type to allow for reception by the durable dispenser. For example, the consumable may hold between 1 and 3 L, and/or between 1 and 5 gallons, of liquid, and may have a substantially or semi-cylindrical, rectangular, or like shape. The consumable may be of any color or composition that will allow for the sensing discussed herein. The consumable may have associated therewith printed traces or sensors that may extend substantially along the length/height of the consumable to allow for sensing, such as capacitive or photoresistive sensing, by way of non-limiting example. The labels may be also pressure sensitive and/or adhesive, or of a polymer composition suitable for in-mold labeling, and may be applied aftermarket or during the manufacturing and labeling process. These traces may electrically associate with electrodes in the dispenser in order to provide a signal or signals indicative of the requisite contents level sensing.
The dispenser may include a dispenser, such as a spout, crank, spigot, pump, or the like, for the dispensing of the contents from a consumable received into the dispenser. The dispenser may be, by way of non-limiting example, plastic in composition, and may be substantially injection molded, such as with one or more actuation elements, such as a handle, switch, crank, button, or the like. The dispenser may include the aforementioned electrodes for associating with the sensor strips on the label physically present on the consumable associated with the dispenser. The dispenser may include one or more printed circuit boards having a connector to the electrodes suitable for receiving signals from the sensors on the consumable label; a sensor module; one or more indicator LEDs to indicate dosage, level and/or auto replenishment; one or more network communication capable modules, such as for communicating with a smart phone, local area network, cellular network, or the like; one or more power modules to provide power to the dispenser modules and the consumable sensor circuit, and which may include batteries that may be permanent/semipermanent (i.e., rechargeable) or replaceable; and or other optional elements, such as one or more audio alarms to support or replace the LED indicators of correct dosage or auto replenishment.
Further included may be firmware and software to provide the functionality discussed throughout. For example, firmware may sense the contents level based on the intercommunication of the sensing chip and the conductive traces, and may use this information to indicate dosing or auto replenishment. Likewise, dosing, and perhaps auto replenishment, may be information provided remotely from cloud-based algorithms to the firmware of the dispenser.
The disclosed communication capabilities may include communication with one or more smartphone apps having user information associated therewith, and which may receive user feedback regarding content levels, dosing, auto replenishments, and so on. Such a smart phone app may communicate with the dispenser via, for example, WiFi, Bluetooth, BLE, or cellular communication methodologies, and further, the firmware of the dispenser may be suitable to batch information and data and/or otherwise piggyback to a smart phone having resident thereon the referenced app.
Further, a cloud-based backend may store and serve received data to and from the aforementioned app, and to or from one or more web-based or app-based dashboards. Some or all of the additional processing discussed throughout may be performed at the cloud based backend, such as alerts or email confirmations in the circumstances of auto replenishment, such as instead of drawing on the limited resources of the dispenser's firmware or processors.
The aforementioned dashboard may be associated with one or more sellers or brands of the referenced contents within the consumable. In such circumstances, an analytics dashboard may be available to the brand for user and use data indicative of certain geography use, global use, use at times of the day, use by demographic area, or the like. This and additional information provided at the dashboard may allow for a brand to target or otherwise send special offers, discount codes, or the like to particular users, such as high-volume users.
Various of the disclosed embodiments may have associated therewith one or more functional needs. By way of non-limiting example, mechanical and electromechanical functionality may include: dispensing of the contents when the spout or similar output is held in the open position, without leaking in the open or closed position; placement of the content output to enable dispensing of contents “below level”, such as into a pitcher or other large container; in the event replaceable, rather than rechargeable or permanent batteries are used, a battery compartment may be included to allow for periodic changing of the batteries, such as without special tools or the risk of breakage (for example, the battery compartment may open using a simple flat or Phillips' head screwdriver).
Of course, a key electro-mechanical functionality may include detection of the contents level within the consumable. This may be done using the aforementioned photoresistive or capacitive sensing, such as via electrodes in the dispenser associated with a sensor, such as a flexible and/or printed circuit on the consumable. Similarly, a pressure sensitive label, having printed electrodes associated therewith, may be employed. In each such case, the sensing processor may preferably be included within the dispenser and connectively associated with the sensor elements of the consumable's label.
Further, the firmware of the dispenser may indicate when an adequate dose of contents for a particular circumstance has been dispensed, i.e., a proper “dosage event”. For example, the firmware of the printed circuit board may blink one or more LEDs for a proper dosage timeframe, or may audibly indicate, such as using a low-level buzzer, for the length of the dose or when a dose should be stopped. Dose size may be set up using the app or a web-based application, such as in small, medium, and large, increments, and those increments may be particularly associated, such as by a manufacturer's specifications, with a particular machine, such as a particular washing machine brand and model. Alternatively, dosing may be hard coded into the firmware, such as for a given consumable size typically received by the dispenser, such as a 32 ounce consumable.
Moreover, the firmware, such as absent intercommunication with the cloud or in association with cloud communication, may indicate and/or otherwise trigger an autoreplenishment event. This auto replenishment may be automatic or semi-automatic—a semi-automatic autoreplenishment event may show a confirmation dialogue or other alert to the user, such as in the app, which may allow for the user to cancel or confirm the order; or, the auto replenishment order may be fully automated. An autoreplenishment event may be communicated to the referenced cloud backend, such as subject to an additional confirmation, such as by an app alert or an email, to the ordering consumer. Further, such an auto replenishment event may contribute to the data that may be provided to a brand, such as on the brand dashboard. Data associated with an autoreplenishment may include date, time, location, and/or user ID of the app associated with the auto replenishment, percent content level (which may be automatic as an autoreplenishment threshold, or which may be set by the user), product SKU, or the like.
Functionality for the cloud may include storage of content level updates, dosage events, and auto replenishment events. Further, cloud functionality may include user activity data, interactivity, reset capability, and the like. Decisions, such as the reaching of thresholds for discounts, may optionally occur in the cloud, and the brand dashboard may be enabled to approve such discounts to send, such as for receipt by the consumer app, discount codes and/or other targeted advertising to select consumers. Select consumers may be particular consumers meeting certain data thresholds, classes of consumers, app profile information, or the like.
Auto replenishment events available in the dashboard may be provided in list, mapped, or threshold formats, by way of non-limiting example. Accessing an auto replenishment event may open a particular consumer profile, and may make available to the dashboard all data associated with that profile. Such data, which may be in a map form as referenced above, may include latitude, longitude, location, distance from nearest seller of the brand, use date, use time, percent contents level, machine used with, and the like. Also included in the brand dashboard data may be typical frequency of use, recent frequency of use, time since last use, and so on.
In accordance with the foregoing, there may be numerous mechanical aspects of certain of the disclosed embodiments. For example, one mechanical aspect may include the consumable. The consumable may be associated with a custom, electronically functional, pressure sensitive, photosensitive, and/or capacitive label, by way of example. The label may include printed conductive traces that are suitable for electrical connection to the printed circuit board in the dispenser. The label and/or the bottleneck may additionally include one or more insertion mechanisms to allow for insertion of the consumable having the label thereon into the dispenser, such as positional guides, latches, keys, or the like.
Mechanical aspects of the dispenser may include one or more outputs, such as a crank or spigot. The dispenser may be substantially closed so as to avoid leakage, spill or shock, and may allow for the dispenser output to hang over the edge of a level surface to enable filling of larger containers. Further, the dispenser may be suitable to receive the consumable when the consumable is inverted and placed within, such as top-side down or bottom side open, into the dispenser. As such and in certain embodiments, the consumable may have associated therewith features to simplify interaction with the dispenser. For example, the consumable may be provided with a plastic top cap over the opening of the consumable, and/or a foil seal under the plastic top cap over the opening. Thereby, the plastic cap may be removed and the consumable inverted and placed into the dispenser, and the dispenser may include an element to pierce a seal, such as the foil seal, to allow the contents to be released into the dispenser.
Also relevant to the embodiments may be several electrical aspects. For example, the conductive traces of the consumable label are associated with the electronics in the dispenser, as referenced throughout. This may occur, for example, by the inclusion of a tab along the neck of the consumable, wherein the conductive traces are associated with the tab and the tab inserts into a slot within the dispenser when the consumable is inverted and placed onto the dispenser. Further included within the dispenser is the referenced sensor module that interacts with the label.
Also associated with the dispenser and/or with one or more printed circuit boards therein may be a communication chip or module, such as a BLE or Bluetooth chip/module. This communication module may have associated there with an antenna, such as a printed circuit board trace antenna, to enable network communication from the dispenser. The dispenser may additionally include one or more processors, which may include or be in addition to the network communications chipset and/or the capacitive sensing chipset/module. Also included within the dispenser may be power for the foregoing, such as one or more replaceable batteries, such as coin batteries, AA batteries, or AAA batteries, by way of non-limiting example.
The electrical aspects of the dispenser may include, as referenced throughout, one or more printed circuit boards. Such printed circuit boards may be or include a two-sided board having a 1.6 mm thickness, 1 ounce copper, and Nickel-Gold ENIG finish, by way of non-limiting example. The printed circuit board may have, electrically associated therewith, one or more indicators, such as one or more LED and/or one or more audible indicators.
Firmware aspects of certain of the embodiments may include level sensing algorithms. Further, the level sensing may include interference avoidance techniques to maintain sensing accuracy, such that even if a user touches the conductive traces of the label or the dispenser. Further included within the firmware may be the ability to define and communicate this level sensing. For example, network communications, such as BLE communications, may be included in, or otherwise controlled by, the firmware. As such, the dispenser may be discoverable by a smart phone app, and pairing between the dispenser and the smartphone app may occur. Thereby, level sensed updates may be communicated from the dispenser to the smart phone at appropriate or requested intervals.
The firmware may additionally exchange messages regarding dosing events. For example, the firmware may receive a dosing event indication from the user, the smartphone, or a sensor, and may accordingly blink an LED or activate a buzzer to indicate proper dosing. This dosing may comprise a message uploaded to the firmware, such as wherein the dosing is defined either in the cloud or in the app settings by a user. Yet further, autoreplenishment indications to be generated from the firmware may comprise intelligence within the user app or within the cloud backend. Accordingly, network communications may be triggered by changes in liquid level (such as continuously or periodically), the need for auto replenishment, or the like, and hence communications may occur on fixed time intervals, continuously, or at intervals of variable frequency.
In accordance with the foregoing, the user app may additionally include various aspects. For example, the smart phone at may be enabled to discover and pair with the firmware of the dispenser, such as when the dispenser is activated or on, as mentioned above. The smart phone app may display autoreplenishment requests or confirmation, such as in a user dialogue format. Further, the smart phone app may display a current product level, and the frequency of updates for the product level. Also indicated may be proper dosing and the ability for the user to request dosing.
The app may additionally include the capability to receive discounts and targeted advertising, such as from the brand dashboard. These may be in the form of a push notification or a user dialogue that provides an app alert to accept and/or apply the discount code, such as wherein the discount code may be saved for the next order or applied to a current order. Of course, the app may include the ability to change any one or more of the foregoing settings or any additional settings, such as autoreplenishment settings, such as wherein the liquid level percentage threshold may be varied for an autoreplenishment indication. The app may also allow for changes in dosage settings, machine type, such as washing machine brand and model, liquid dispensing models and machine types, and the receipt of or application of discount codes, and so on. The foregoing may be available from a drop-down or similar menu, a pop-up window, or via any known user interaction, by way of example.
The dashboard referenced herein may additionally include particular aspects. For example, the dashboard may include autoreplenishment event data, particular user information, location-based information, and the like. Further, the dashboard may integrate third-party data, such as weather data, to allow for data fusion between sensed data and publicly available data sources, such as in order to optimize sales.
The dashboard may also include one or more search capabilities. That is, a dashboard user may search for particular data across one or more users, such as “frequent users”, “fading users” (i.e., a list of users whose frequency of use has fallen relative to long-term usage), certain geographic searches, usage associated with certain events (such as snowstorms), and the like. Responsive to the search, and otherwise available from within the dashboard, may be a consumer data display. That is, dashboard events, such as autoreplenishment events, may include drill down capabilities to obtain more detail on particular consumers. The drill down may include basic information, such as delivery address or locale, and more particular information, such as dosing events or liquid levels over time.
The dashboard requirements may additionally include an ability to design marketing campaigns and/or discount codes. For example, discount codes may be provided based on the meeting of certain thresholds by certain data of consumers. Thereby, the discount codes may be automatically generated upon the trigger event for one or more consumers, or may be “hard entered” by a person controlling the dashboard. Moreover, the foregoing aspects may overlap, such as wherein discount codes are readily executed, such as responsive to a single click, to all consumers that have been returned responsive to an entered search within the dashboard.
Additional functional requirements may include those of the cloud based backend. The cloud based backend may store data, including autoreplenishment events, dosing events, and product level events, by way of example, and may be suitable to serve that data back to the smart phone app and/or to the dashboard as needed. Further, certain of the decision-making algorithms discussed herein throughout may also reside at the cloud based backend, such as rather than residing in a smart phone app or in association with the dashboard.
Also as shown, the neck and/or cap portion 116 of the consumable 102 may pass through a leak seal 120 upon association with the dispenser 104, such that liquid within the consumable cannot spill out and overflow the sides of the receiving portion of the dispenser. The leak seal 120 may take the form of an o-ring within the dispenser receiving portion, by way of non-limiting example. Further illustrated in
Also illustrated in association with the dispenser is a liquid output 128, such as a spigot. Of note, the spigot shown is in fluid communication with a fluid pathway 130 that begins on the side of the o-ring/leak preventer 120 opposite the body of the consumable 102, and that terminates on the input side of the spigot. Of note and as will be evident from the illustration of
Figures at 7A and 7B illustrate an exemplary sensing label 106 as may be associated with the label of a consumable 102.
By way of nonlimiting example,
The solids sensing employed herein may be any one or more types of sensing suitable for sensing the contents of the box or doses dispensed from the box. By way of example, the sensing may be one or more photo conductive material sensors, which may be printed around at least a portion of the label of the container. Thereby, as portions of the label are uncovered, i.e., as the amount of solids within the container decreases, the photo conductive material senses the additional light that now hits the photo conductive label sensor. Thereby, the level of solids is sensed as indicated by the light received by the photo conductive label.
Of course, a variety of other sensing methodologies may be employed, such as, but not limited to, infrared, ultrasound, proximity sensing, other types of light sensing, derivative sensing, weight sensing, sound sensing, or resistance/conductance sensing, by way of non-limiting example. Needless to say, one or more of the foregoing sensing methodologies may vary in the uniformity of the sensing output, such as in accordance with the type of bulk solid 1102 item or liquid placed within the container. Therefore, adjustments may be necessary in the type of sensing used, and/or in the processing of the sensor output, in order to properly sense different types of items.
In accordance with the foregoing, the sensor output may be active or passive, as discussed. By way of non-limiting example, a photoconductive strip may measure ambient light (passive) or light emitted by an LED powered by the system (active). In either case, the output of the sensor must be provided to a processing system 1110. This may be done by any of a variety of methods. For example, a highly simplistic processor may be included on the container in association with the sensor. In such cases, the processor may include some wireless communication capabilities, such as RF, infrared, Bluetooth, Wi Fi, or the like, or communication with the processing chip may occur based on an active external interrogation of the processing chip. Alternatively, the one or more processors may be off-container as discussed throughout, and hence may form part of a system that actively interrogates the container to obtain the requisite sensing output, as is also discussed further hereinbelow with respect to
In the embodiment of
As referenced with respect to
The dispensing base may include a dispenser 1293, such as a crank, spout with spigot, or the like, for the dispensing of the solids from the container received into the base. The dispenser base and the dispenser may be, by way of non-limiting example, plastic in composition, and/or may be substantially injection molded, such as with one or more actuation elements, such as a handle, switch, button, or the like.
The base may include one or more indicator LEDs 1295 to indicate dosage and auto replenishment; one or more network communication capable modules, such as for communicating with a smart phone, local area network, cellular network, or the like; one or more power modules to provide power to the base modules, and which may include batteries that may be permanent/semipermanent (i.e., rechargeable) or replaceable; and or other optional elements, such as one or more audio alarms to support or replace the LED indicators of correct dosage or auto replenishment.
Further included may be firmware and software to provide the functionality discussed throughout. For example, firmware may sense the solids level based on the intercommunication of the sensing and the processing, and may use this information to indicate dosing or auto replenishment. Likewise, dosing, and/or auto replenishment, may be information provided remotely from cloud-based algorithms, such as to the firmware of the base.
As referenced, the disclosed communication capabilities may include communication with one or more smartphone apps 1297 having user information associated therewith, and which may receive user feedback regarding levels, dosing, auto replenishments, and so on. Such a smart phone app may communicate with the base via, for example, WiFi, Bluetooth, BLE, or cellular communication methodologies, and further, the firmware of the base may be suitable to batch information and data and/or otherwise piggyback to a smart phone having resident thereon the referenced app.
Further, a cloud-based backend 1299 may store and serve received data to and from the aforementioned app, and to or from one or more web-based or app-based dashboards. Some or all of the additional processing discussed throughout may be performed at the cloud based backend, such as alerts or email confirmations in the circumstances of auto replenishment, such as instead of drawing on the limited resources of the dispensing base's firmware or processors.
As discussed throughout, the automatic reordering envisioned herein may reflect a need to reorder not only a consumable, but additionally a durable aspect of the disclosed system. By way of non-limiting example, durable and consumable pairs may include: razors and razor blades; a soap dispenser and a soap or shampoo bottle; a hand soap dispenser and a refill soap bag; a cereal box and a turning crank cereal dispenser; a printer and an ink cartridge; a disposable detergent bottle and an ergonomic spigot dispenser; a spice rack and a spice bottle; a centrifuge and a vial of bodily fluid; and a coffee machine and coffee, tea, or other beverage pods.
In prior efforts, the smart label of a consumable has been read by a durable with which the consumable is paired solely in order to identify the consumable. That is, a consumable may typically be associated with and RFID or NFC Tag, a Q.R. code, a barcode, a UPC code, or the like, which, when read by a paired durable, serves merely to identify the consumable. In contrast, the proposed embodiments may, embed semi-smart and smart labels on or in the consumables such that a wealth of information beyond identification may be sensed or otherwise conveyed to and by the paired durable, such as exclusively and only upon pairing of the consumable with the durable. That is, the durable may include a plurality of conventional electronics designed to sense/read the detailed consumable information provided by the semi-smart label of the consumable. Accordingly, the disclosed embodiments may provide functionality beyond mere identification, and may provide significant cost advantages over RFID, NFC, or optical reading methods previously provided for the consumable and durable pair.
Such functionality may be provided, such as only upon pairing of the consumable with the durable, by any of a variety of methods that will be understood to the skilled artisan in light of the discussion herein. For example, discussed throughout are capacitive proximity sensing, light sensing (such as using photo resistive sensors), and conductivity or resistivity sensing (wherein electrically unconnected portions of the system are subsequently connected to indicate a content level) to provide content identification for consumable items.
By way of non-limiting example,
Additionally, and alternatively,
In the illustration of
More particularly,
It will be appreciated that the foregoing embodiments may also work for liquids having a certain opacity, and for uniformly sized items that need to be counted, as well as for bulk solids sensing discussed throughout. In fact, the same “universal container” could be filled with any of several substances without substantially affecting its ability to sense product level. That is, provided herein is an inexpensive method to continuously detect change in product level by sensing a change in resistance for solids or liquids.
It will be understood that the durable discussed throughout may be generic or proprietary. That is, a proprietary durable may be operable only with a particular brand of consumables, and hence other brands of the same type of consumable will not operate with the proprietary durable. Modification of the aspects discussed herein, such as customization in aspects of a printed photo resistive label, may make it difficult to genericize a proprietary durable. Thereby, a proprietary durable may enhance brand loyalty for certain categories of consumables.
More particularly,
The durable 1606 may then have slots 1608 connectively associated with power 1610 and the input-output of one or more analog to digital convertors 1612 associated with a microprocessor 1614, such as to identify the different resistance values of the resistive trace 1604 associated with a consumable placed within the slot 1608. Thereby, if multiple consumable items may be used in a single durable, the resistive sensing identifies which consumable was used. If multiple consumables may be simultaneously placed within the durable at multiple slots at the same time, the disclosed embodiment may identify which consumable is in which slot. It will be appreciated that the variations in resistance of the resistive trace may be provided by any known methods, such as variations in the shape, length, thickness, or type, such as the material composition, of the trace used.
In relation to the proprietary or non-proprietary nature of the durables as discussed above, the aforementioned dashboard may be associated with one or more sellers or brands of the referenced solids. In such circumstances, an analytics dashboard may be available to the brand for user and use data indicative of certain geography use, global use, use at times of the day, use by demographic area, or the like. This and additional information provided at the dashboard may allow for a brand to target or otherwise send special offers, discount codes, or the like to particular users, such as high-volume users.
In the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the embodiments require more features than are expressly recited herein.
This continuation application claims priority to U.S. application Ser. No. 17/052,773, filed Nov. 3, 2020, entitled: APPARATUS, SYSTEM, AND METHOD OF PROVIDING A CONTENT LEVEL MONITOR, which is a national stage application of International Patent Application No. PCT/US2019/030592, filed May 3, 2019, entitled: APPARATUS, SYSTEM, AND METHOD OF PROVIDING A CONTENT LEVEL MONITOR, which claims the benefit of priority to U.S. Provisional Application No. 62/666,608, filed May 3, 2018, entitled APPARATUS, SYSTEM, AND METHOD OF PROVIDING A CONTENT LEVEL MONITOR, the entirety of which is incorporated herein by reference as if set forth in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
1078214 | Patnaude | Nov 1913 | A |
3553471 | Maigret | Jan 1971 | A |
4874023 | Ulm | Oct 1989 | A |
4991635 | Ulm | Feb 1991 | A |
5005407 | Koon | Apr 1991 | A |
5213597 | Campbell | May 1993 | A |
5277337 | Ford | Jan 1994 | A |
5368197 | Sutera | Nov 1994 | A |
5383574 | Raphael | Jan 1995 | A |
5544770 | Travisano | Aug 1996 | A |
5636762 | Juhola | Jun 1997 | A |
5641006 | Autrey | Jun 1997 | A |
6095370 | Rhine | Aug 2000 | A |
6554382 | Sleger | Apr 2003 | B1 |
6741180 | Lassota | May 2004 | B2 |
6820772 | Bennett, Jr. | Nov 2004 | B1 |
7000468 | Doorhy | Feb 2006 | B2 |
7107838 | Chai | Sep 2006 | B2 |
7258005 | Nyce | Aug 2007 | B2 |
7331487 | Macler, II | Feb 2008 | B2 |
7401513 | Szela | Jul 2008 | B2 |
7506576 | Lassota | Mar 2009 | B1 |
7562571 | Raffalt | Jul 2009 | B2 |
7654421 | Chan | Feb 2010 | B2 |
7661307 | Milone | Feb 2010 | B1 |
7712364 | Radhakrishnan | May 2010 | B2 |
7798373 | Wroblewski | Sep 2010 | B1 |
8014789 | Breed | Sep 2011 | B2 |
8159660 | Mimeault | Apr 2012 | B2 |
8177096 | Macler | May 2012 | B2 |
8382913 | Classen | Feb 2013 | B2 |
8387455 | Kaminski | Mar 2013 | B1 |
8429965 | Radhakrishnan | Apr 2013 | B2 |
8464584 | Lassota | Jun 2013 | B2 |
8464906 | Macler | Jun 2013 | B2 |
8469050 | King | Jun 2013 | B2 |
8931340 | Wiederkind-Klein | Jan 2015 | B2 |
8966973 | Milone | Mar 2015 | B1 |
8980014 | Classen | Mar 2015 | B2 |
9052227 | Lassota | Jun 2015 | B1 |
9138091 | Zhao | Sep 2015 | B2 |
9153119 | Stapleford | Oct 2015 | B2 |
9212042 | Veltrop | Dec 2015 | B2 |
9261395 | Shearer | Feb 2016 | B2 |
9311806 | Hazen | Apr 2016 | B2 |
9417635 | Hampton | Aug 2016 | B2 |
9459132 | Fehrenbach | Oct 2016 | B2 |
9476752 | Vilag | Oct 2016 | B2 |
9488513 | Kumar | Nov 2016 | B2 |
9510727 | Classen | Dec 2016 | B2 |
9610001 | Classen | Apr 2017 | B2 |
9658095 | Winkens | May 2017 | B2 |
9911306 | Tshilombo | Mar 2018 | B2 |
9952082 | Schwartz | Apr 2018 | B2 |
10114139 | Mirisharif | Oct 2018 | B1 |
11280042 | Williams | Mar 2022 | B2 |
20020020449 | Imai | Feb 2002 | A1 |
20020145527 | Lassota | Oct 2002 | A1 |
20020161652 | Paullin | Oct 2002 | A1 |
20040199131 | Kitamura | Oct 2004 | A1 |
20050067434 | Yu | Mar 2005 | A1 |
20050162277 | Teplitxky | Jul 2005 | A1 |
20050172712 | Nyce | Aug 2005 | A1 |
20060033630 | Lyall, III | Feb 2006 | A1 |
20080036615 | Lyall, III | Feb 2008 | A1 |
20080277414 | Macler | Nov 2008 | A1 |
20090031798 | Radhakrishnan | Feb 2009 | A1 |
20090158841 | Winkens | Jun 2009 | A1 |
20090187357 | Ho | Jul 2009 | A1 |
20090212069 | Lassota | Aug 2009 | A1 |
20090294469 | Poulain | Dec 2009 | A1 |
20100209313 | Davis | Aug 2010 | A1 |
20110166699 | Palmquist | Jul 2011 | A1 |
20110265562 | Li | Nov 2011 | A1 |
20110314907 | Wiedekind-Klein | Dec 2011 | A1 |
20120067920 | Veltrop | Mar 2012 | A1 |
20120193373 | Macler | Aug 2012 | A1 |
20120218106 | Zaima | Aug 2012 | A1 |
20120305605 | Vassaux | Dec 2012 | A1 |
20130036815 | Bernhardsgruetter | Feb 2013 | A1 |
20130206011 | Ozanne | Aug 2013 | A1 |
20130269832 | Gengerke | Oct 2013 | A1 |
20130276533 | Wilder | Oct 2013 | A1 |
20130285681 | Wilson | Oct 2013 | A1 |
20130334214 | Yogev | Dec 2013 | A1 |
20130344206 | Yoakim | Dec 2013 | A1 |
20140014684 | Classen | Jan 2014 | A1 |
20140152323 | Kumar | Jun 2014 | A1 |
20140354438 | Hazen | Dec 2014 | A1 |
20150021360 | Veltrop | Jan 2015 | A1 |
20150090625 | Bauss | Apr 2015 | A1 |
20150122015 | Leppard | May 2015 | A1 |
20150129039 | Mulvaney | May 2015 | A1 |
20150329347 | Veldhi | Nov 2015 | A1 |
20150366411 | Yang | Dec 2015 | A1 |
20160003615 | Biswas | Jan 2016 | A1 |
20160007798 | Jimenez | Jan 2016 | A1 |
20160047683 | Winkens | Feb 2016 | A1 |
20160146659 | Saltzgiver | May 2016 | A1 |
20160230625 | Bradford | Aug 2016 | A1 |
20160257554 | Manwani | Sep 2016 | A1 |
20160286993 | Pau | Oct 2016 | A1 |
20170135530 | MacLeod | May 2017 | A1 |
20170161676 | Aji | Jun 2017 | A1 |
20170228519 | Chu | Aug 2017 | A1 |
20170278059 | Aji | Sep 2017 | A1 |
20170299416 | Rondano | Oct 2017 | A1 |
20170299417 | Otagaki | Oct 2017 | A1 |
20170328761 | Schwartz | Nov 2017 | A1 |
20180080807 | Singh | Mar 2018 | A1 |
20180099850 | Lyons | Apr 2018 | A1 |
20180100754 | Kumar | Apr 2018 | A1 |
20180111145 | Ophardt | Apr 2018 | A1 |
20180132643 | Shklar | May 2018 | A1 |
20180228977 | Schabbach | Aug 2018 | A1 |
20180266866 | Biswas | Sep 2018 | A1 |
20180266873 | Goodier | Sep 2018 | A1 |
20180303271 | Glucksman | Oct 2018 | A1 |
20180321072 | Williams | Nov 2018 | A1 |
20180326661 | Johnson | Nov 2018 | A1 |
20180344070 | Perrelli | Dec 2018 | A1 |
20190021529 | Schucker | Jan 2019 | A1 |
Number | Date | Country |
---|---|---|
1121700 | May 1996 | CN |
1259090 | Jul 2000 | CN |
1452107 | Oct 2003 | CN |
1508738 | Jun 2004 | CN |
1784354 | Jun 2006 | CN |
101573063 | Nov 2009 | CN |
202126296 | Jan 2012 | CN |
102421697 | Apr 2012 | CN |
202915989 | May 2013 | CN |
103251310 | Aug 2013 | CN |
105203185 | Dec 2015 | CN |
105813519 | Jul 2016 | CN |
105939643 | Sep 2016 | CN |
106017637 | Oct 2016 | CN |
205642549 | Oct 2016 | CN |
206252346 | Jun 2017 | CN |
107040260 | Aug 2017 | CN |
107634885 | Jan 2018 | CN |
102012200949 | Jul 2013 | DE |
1270501 | Jan 2003 | EP |
2180299 | Apr 2010 | EP |
2282184 | Feb 2011 | EP |
3244175 | Nov 2017 | EP |
3263000 | Jan 2018 | EP |
2059596 | Apr 1981 | GB |
2099791 | Nov 1984 | GB |
0200167 | Feb 2002 | GB |
2383845 | Jul 2003 | GB |
1211782 | May 2016 | HK |
H09174039 | Jul 1997 | JP |
2002039838 | Feb 2002 | JP |
2012101796 | May 2012 | JP |
20010082146 | Aug 2001 | KR |
20100009743 | Jan 2010 | KR |
20120050987 | May 2012 | KR |
9965818 | Dec 1999 | WO |
2005092012 | Oct 2005 | WO |
2006044782 | Apr 2006 | WO |
2011127334 | Oct 2011 | WO |
2014096405 | Jun 2014 | WO |
2018204720 | Nov 2018 | WO |
Entry |
---|
Chinese Office Action issued in App. No. CN202210122381, dated Sep. 23, 2023, 4 pages. |
International Preliminary Report on Patentability, dated Nov. 5, 2019 for PCT/US2018/030987. |
International Search Report and Written Opinion dated Aug. 27, 2018 in PCT/US2018/030987. |
Parashar, Mohita et al., “Water Level Monitoring System in Water Dispensers using IoT”, IRJET, (20180400), vol. 05, ISSN 2395-0056, pp. 1217-1220, XP055756965. |
Chinese Office Action issued in App. No. CN20198037470, dated Oct. 11, 2023, 9 pages. |
Chinese Office Action issued in App. No. CN20198037889, dated Oct. 10, 2023, 8 pages. |
EPO Communication pursuant to Article 94(3) issued in App. No. EP19796780, dated Dec. 13, 2023, 5 pages. |
Number | Date | Country | |
---|---|---|---|
20230083415 A1 | Mar 2023 | US |
Number | Date | Country | |
---|---|---|---|
62666608 | May 2018 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17052773 | US | |
Child | 17952010 | US |