Smart Scent Container Tag Tracking

A scent dispensing apparatus may include a scent container retaining apparatus configured to receive and securely retain a scent container, wherein the scent container includes a smart vial tag, a smart vial sensor directionally positioned to have a direct line of sight with the smart vial tag to read the smart vial tag when the scent container is securely retained in the scent retaining apparatus, and a fragrance management application that receives an identity of the smart vial tag from the smart vial sensor and generates a unique container profile for the scent container.

BACKGROUND

The present disclosure relates to tracking of smart container tags on scent containers in a scent dispenser used for scent dispensation.

Existing solutions for dispensing scents within a location, such as a home, include conventional scented candles, incense stocks, hanging air fresheners, and electric fragrance diffusers, such as those that plug into an outlet socket and include a heating element to heat a fragrant substance. In some cases, a porous substrate is saturated with the fragrant substance and then placed adjacent to a heat source, which heats up the fragrant substance to diffuse it within a predetermined space.

While functional, these solutions are limited. For example, it is often difficult to tell when a fragrance dispenser has run out of fragrance, as the dispenser typically lacks any sort of indicator and one is left to smell the dispenser manually to determine how much fragrance is actually left, which is ineffective as the dispenser itself may still smell like the diffuse fragrance up close that may have little effect in the area that is to be perfumed. In addition, if the users wishes to change a fragrance, the user has to manually open the dispenser to replace the cartridge in the dispenser, or in the case of hanging dispensers, replace it with a fresh version and the scent dispenser has no way of knowing what types of cartridges or containers are being replaced.

SUMMARY

In some aspects, the techniques described herein relate to a scent dispensing apparatus, including: a scent container retaining apparatus configured to receive and securely retain a scent container, wherein the scent container includes a smart vial tag; a smart vial sensor directionally positioned to have a direct line of sight with the smart vial tag to read the smart vial tag when the scent container is securely retained in the scent retaining apparatus; and a fragrance management application that receives an identity of the smart vial tag from the smart vial sensor and generates a unique container profile for the scent container.

In some aspects, the techniques described herein relate to a scent dispensing apparatus, wherein the smart vial sensor is an optical sensor and the smart vial tag is a QR code detectable by the smart vial sensor.

In some aspects, the techniques described herein relate to a scent dispensing apparatus, wherein the smart vial sensor is a radio receiver and the smart vial tag is an RFID tag that can be read by the radio receiver.

In some aspects, the techniques described herein relate to a scent dispensing apparatus, wherein the radio receiver is a directional antenna positioned within a threshold distance of the RFID tag when the scent container retaining apparatus retains the scent container.

In some aspects, the techniques described herein relate to a scent dispensing apparatus, wherein the unique container profile includes one or more of an identity of a scent solution, settings of a scent solution, states of the scent container, a fill-level of the scent container, and a location of the scent container.

In some aspects, the techniques described herein relate to a scent dispensing apparatus, wherein the scent container includes a scent solution that can be emitted from the scent container.

In some aspects, the techniques described herein relate to a scent dispensing apparatus, wherein the smart vial tag further includes smart container data that can be read from the smart vial tag.

In some aspects, the techniques described herein relate to a scent dispensing apparatus, wherein the smart vial tag is located on a bottom surface of the scent container.

In some aspects, the techniques described herein relate to a scent dispensing apparatus, wherein the unique container profile includes historical data of the scent container.

In some aspects, the techniques described herein relate to a method of using a scent dispensing apparatus, including: detecting, using a smart container sensor of a scent dispensing apparatus, that a scent container with a smart container tag positioned on a surface of the scent container has been positioned in a slot of the scent dispensing apparatus; receiving, using the smart container sensor, smart container data from the smart container tag; determining, using a processor of the scent dispensing apparatus, an identity of the scent container using the smart container data; determining, using the processor of the scent dispensing apparatus, current usage data of the scent container; and updating, using the processor of the scent dispensing apparatus, the smart container data to include the current usage data by having the smart container sensor provide current usage data to the smart container tag of the smart container.

In some aspects, the techniques described herein relate to a method, wherein the smart container sensor is a radio sensor and the smart container tag is a RFID tag that can be read by the radio sensor when the RFID tag is within a threshold distance of the radio sensor.

In some aspects, the techniques described herein relate to a method, wherein the RFID tag is positioned on a bottom surface of the scent container and the radio sensor is positioned below where the scent container is positioned in the scent dispensing apparatus.

In some aspects, the techniques described herein relate to a method, wherein the radio sensor is a directional antenna and wherein when the scent container is positioned in the scent dispensing apparatus, the radio sensor has a direct line of sight with the RFID tag.

In some aspects, the techniques described herein relate to a method, wherein the smart container data includes a unique identifier that represents the identity of the scent container.

In some aspects, the techniques described herein relate to a method, wherein the smart container sensor is an optical sensor and the smart container tag is a QR code that is detectable by the optical sensor.

In some aspects, the techniques described herein relate to a method, wherein the smart container sensor includes electrical sensor contacts configured to engage with electrical tag contacts on the smart container tag.

In some aspects, the techniques described herein relate to a method, wherein the scent container includes a scent solution that can be emitted from the scent container.

In some aspects, the techniques described herein relate to a method, wherein the current usage data includes one or more of an identity of a scent solution, settings of a scent solution, states of the scent container, a fill-level of the scent container, and a location of the scent container.

In some aspects, the techniques described herein relate to a method, wherein updating the smart container data to include the current usage data further includes: tracking the smart container tag during a manufacturing process to include first tracking data; tracking the smart container tag during a shipping process to include second tracking data; and updating the smart container data to include the first tracking data and the second tracking data.

In some aspects, the techniques described herein relate to a smart container tag tracking method including: installing a smart container tag with a unique identifier on a scent container during manufacturing; tracking the smart container tag during a manufacturing process; tracking the smart container tag during a shipping process; automatically connecting the smart container tag to a scent dispenser using a smart container sensor; updating a scent container lifetime based on the tracking of the smart container tag; applying a timestamp at removal of the scent container; and updating the smart container tag with the timestamp.

Further innovative aspects include corresponding systems, methods, apparatus, and computer program products. These systems, methods, apparatus, computer program products, and other aspects, are particularly advantageous in a number of respects. For example, the technology enables users to remotely control scent dispensers, switch between scents remotely, and receive notifications when a scent solution is running/has run out, automatically switches the scent solution(s) to diffuse based on user location, allows users to schedule scent diffusion for different locations, etc. In addition, the technology can collect data about scent solution usage and user habits when using scent dispensers, and then analyze that data to produce analytics to inform producers about characteristics of the users, the scents being consumed, etc. Numerous additional features are also possible and contemplated, many of which are discussed herein.

However, this list of features and advantages is not all-inclusive and many additional features and advantages are within the scope of the present disclosure. Moreover, it should be noted that the language used in the present disclosure has been principally selected for readability and instructional purposes, and not to limit the scope of the subject matter disclosed herein.

DETAILED DESCRIPTION

The technology described in this disclosure relates to detecting scent containers using a smart container detection system for dispensing scent within the premises using remotely controllable scent dispensers. As an example, the technology allows the user to install a scent container into a scent dispenser and the scent dispenser is able to automatically detect an identity of the scent container and/or various settings and/or states of the scent container, such as a fill-level of the scent container after the scent container is installed in the scent dispenser without requiring any additional data input from the user.

FIG.1Ais a block diagram illustrating an example system100for smart container detection and scent dispensation. The system100may include one or more scent dispenser installations158. In a typical implementation, a multiplicity of users112may install scent dispenser on their respective premises140in which they wish to dispense various scents. A scent dispenser installation158may include any number of scent dispensers132a. . .132n. In the depicted implementation, scent dispensers132aand132n(individually or collectively also referred to as simply132) are plugged into electrical sockets146aand146n. The scent dispensers132may be located in the same room or in different rooms (e.g.,142aand142n).

As shown, the illustrated system100further includes client device(s)106and a dispenser management server150, which are electronically communicatively coupled via a network102for interaction with one another, access point(s)120, and the scent dispenser(s)132, etc., using standard networking protocols, as reflected by signal lines104,138, and152. In a typical installation, the scent dispenser(s)132are coupled for electronic communication with the access point(s)120(e.g., a modem, router, etc., coupled to the network102) as reflected by the signal line138. In further embodiments, the scent dispenser(s)132may be coupled directly to the network102, such as via a wireless wide area network (e.g., WWAN) or other suitable network. For clarity, reference to the term network102includes the local networks of the installations (e.g., provided by access point(s)120, etc.), unless otherwise specified.

The scent dispenser132includes a communication-enabled diffusion device that diffuses scent solution(s) from scent container(s) installed in the scent dispenser132. The scent dispenser132may include wireless transceivers configured to communicate with other devices within range, such as other scent dispenser(s)132and/or access point(s)120. In some embodiments, the diffusion device nebulizes the scent solution into the air of the surrounding environment to diffuse the scent. In some implementations, the diffusion device may nebulize the scent solution into the air using diffusion elements such as heating elements, fan elements, or other elements that can cause a scent solution or scent gel capsule to be emitted as a scent as shown by the emitted scent lines130a-130n. The structure, acts, and/or functionality of the scent dispenser132is discussed further below. In some implementations, the scent dispenser132may include a smart container detection system for detection of scent container(s) being installed in the scent dispenser132.

In some implementations, the access point120connects to the set of scent dispensers132installed on the premises140, as shown by the signal lines134a. . .134n, and exchanges data sent between the scent dispensers132and the mobile device(s)106and/or the dispenser management server150(e.g., via the signal line138). In further implementations, the scent dispensers132may be connected directly to the network102without needing the access point120.

The dispenser management application160operable by the dispenser management server150can receive operational data from the scent dispensers132in association with the premises140, room142, user(s)112, and/or scent containers with which they are associated. The dispenser management application160can receive management requests and geolocation data from mobile devices of the user(s)112in association with the scent dispenser(s)132that are registered to the user(s) in the system100. The management requests may include registration data requesting to register a scent dispenser132with a user's112account, a particular premises140, and/or a room142within the premises140; scheduling data requesting to schedule dispensation of scent(s), from scent dispenser132or a set of two or more scent dispenser(s)132, for particular timeframe(s) within a particular room142of a premises140; operational data instructing to activate or deactivate a scent dispenser132and/or specifying which scent solution to activate and/or deactivate; geolocation data indicating a current location of a user112, etc. The scheduling data may include a reoccurring schedule that repeats on certain days and/or times of day, and may specify which scent solution(s) should be dispensed at which times.

In some embodiments, the dispenser management application160may maintain the device states, scent allocations, users, and schedules of the scent dispensers132. The dispenser management application160may make device function calls to command/control the scent dispensers132(e.g., by sending state settings), and may receive and log published events (heartbeat, alerts, data, etc.) received from the scent dispensers132in the data store170.

The dispenser management server150includes a data store170storing various types of data used by the dispenser management application160. Example data types include dispenser data172, user data174, fragrance data176, usage data178, premises data180, analytics data182, and/or smart container data183. The dispenser data172may include entries for the scent dispensers132in the system100. A given entry may include a unique identifier of the corresponding scent dispenser, a firmware version, an operational status indicator (e.g., on, off, etc.), a schedule including which day(s) of the week and/or times of day the scent dispenser should be operating, which scent solution(s) should be dispensed during the scheduled timeframe(s), whether/which color light should be illuminated, the user identifier(s) with which the scent dispenser is registered, etc.

The user data174may include entries for the users112of the system100. A given entry may include a unique identifier for the user, contact information for the user (e.g., address, phone number, electronic address (e.g., email)), payment information, scent subscription information specifying which reoccurring scent containers should be shipped to the user, historical scent container purchase information, etc.

The fragrance data176may include entries for the different scent solutions that are supported by the system100. An example entry may include a unique identifier for a given scent, a scent name, a scent description, a list of ingredients that comprise the scent's composition, an indication of the strength of a scent, room types for which to suggest the scent, etc.

The usage data178may include logged usage statistics received from the scent dispensers132deployed in the system100. Example usage statistics may include hours of operation, which scent solutions were dispensed during those hours of operation, thus reflecting the time of day scent solutions were utilized, the amount of scent solutions that were dispensed as measured by container sensors included in the scent dispensers132, the rate at which the scent solutions were dispensed, etc. The usage statistics for a given scent dispenser132may be specifically associated with the user112associated with the usage and/or a room142of a premises140in which the scent dispenser132is installed.

Further, the fragrance data176may include container data including unique identifiers for each scent container produced and registered for use in the system100. The container data may reflect the installation status of a container, the unique identifier of the scent solution contained by the container, and the fill level of the container, an eligibility status, etc. For instance, the container data for a particular container may indicate whether the container is new and has not yet been installed, that the container is currently installed but has not yet been depleted of its solution, that the container was depleted of its solution and is no longer eligible for use, and/or that the container has been refilled and is available for future use or to be shipped back out to customers.

The premises data180may include entries for different premises140in which scents dispensers132are installed. The premises data180may include different rooms142for the premises140, and may indicate in which specific rooms142the scent dispensers132are installed. Example premises data may include unique identifiers for each of the premises, room names for each of the rooms of a given premises (e.g., which may be customized by the user), the dimensions of the rooms of the premises (which may provided by users112or automatically determined based on estimated room dimensions, blueprints, etc.), an indication of which scent dispensers132are installed in which rooms of a given premises, for example, using the unique identifiers of the scent dispensers132, etc., an indication of which unique user identifiers are associated with which unique premises identifiers, etc.

The analytics data182may include data produced by the dispenser management application160the data stored in the data store170. For instance, data from the scent dispensers belonging to users112may be aggregated by the server in the data store170and then analyzed to generate analytics. These analytics can be used by the manufacturer to improve the product, the user to evaluate his/her usage, and the scent solution producers to learn more about their users, the users' habits and preferences, their products, etc.

Example analytics data may reflect scent preferences, such as which scents consumers use most often (e.g., based on the usage data178determined by a container sensor), scent preferences by room142type of the premises140(e.g. floral for bathrooms, edible scents for kitchens, etc.) (e.g., based on the correlation between the fragrance data176and the premises data180), which scents consumers are repurchasing the most (based on user data174), whether or not consumers are mixing scents in specific rooms (e.g., based on the correlation between the fragrance data176, the usage data178, and the premises data180), scent preferences by season (based on time/data coded usage data178), preferences for strength of a scent (light vs. strong fragrance) and does that differ by room (e.g., based on the correlation between the fragrance data176, the usage data178, and the premises data180), whether consumer scent preferences evolve over time (e.g., based on the usage data178), preference for classic vs. novelty scents (e.g., based on the usage data178and the fragrance data176that tags each scent as classic or novelty), etc.

Example analytics data may reflect scent dispensation behaviors, such as how often users use their scent dispensers132(e.g., based on the usage data178), is the use continuous or as needed (e.g., based on the usage data178), how long is the continuous use (e.g., several hours, e.g., several days, etc., based on the usage data178), how long does it take for consumers to change out a scent solution/cartridge/refill (e.g., usage data reflects an empty container stayed in the scent diffuser132for a certain timeframe, which can be averaged over many, or all users (e.g., generally, for that fragrance type, etc.)), how often are consumers purchasing refills (e.g., based on the user data174reflecting purchase history), preferred rooms142for using scent dispenser132(e.g., based on the correlation between the usage data178and the premises data180), use of scent dispensers132when users112are in vs. out of the premises140(e.g., based on the correlation between the users'112user data174and the usage data178), etc.

Example demographics data may reflect behaviors and preferences by different demographic groups. User data may reflect a user's gender, age, income, race/ethnicity, number of children in the home, number of pets in the home, region, settlement-type (urban, rural, suburban, etc.), premises type (single family home, apartment, condo, townhouse, small business, large business, hotel, bed and breakfast, warehouse, restaurant, etc.), personal or business, etc. Using the user data, any of the other data or combinations thereof may be segmented to determine which groups may be more or less predisposed to scent dispensation, and how different factors affect the level of scent dispensation by a particular group. In some implementations, the demographic data may be used to provide recommendations to users112based on various data. In further implementations, the recommendations may be determined using artificial intelligence and/or machine learning to analyze the demographic data and identify various trends for recommendations.

The smart container data183may include entries for different scent containers installed in scents dispensers132that are identified by the smart container detection system. The smart container data183may include one or more of identities of each of the smart containers, fill levels of the smart containers, persistent scent settings for each scent container, refill status of each scent container, historical data of each scent container, ages of each scent container, etc. In some implementations, the smart container tag197may include a unique identifier that is associated with smart container data183stored on the dispenser management server150and the smart container data183may be updated based on changes in the settings or details associated with the smart container and based on the unique identifier of the smart container tag197. In some implementations, the smart container data183may be further stored on the smart container tag197(seeFIG.1B) and may travel with the scent container250rather than being stored on the dispenser management server150.

The data stored by the data store170may be correlated using various common keys, such as unique identifiers (e.g., user identifiers, room identifiers, fragrance identifiers, scent dispenser identifiers, container identifiers, room identifiers, premises identifiers, smart container tag197identifiers, etc.), which allow the dispenser management application160to generate and provide rich analytics.

The container sensors of the scent dispensers132can detect the changes in the fluid levels of the containers as the solutions from the containers are diffused into the air of the respective premises140. The controllers of the scent dispensers132receive the data reflecting the changing fluid levels and transmit that data to the dispenser management server150, which in turn stores the data as usage data178in the data store170in association with the scent/fragrance ID to which the data corresponds. As a result, the usage data178reflects the amount of each scent solution that is consumed over time for each scent dispenser132relative to the user ID, the premises ID, the room ID, scent dispenser132ID, the container ID associated with that particular scent solution (e.g. which is identifiable as discussed elsewhere herein).

FIG.1Bis a block diagram illustrating an example scent dispenser, which is depicted as including a power supply (PS)184, a set of sensors186, a controller188, an interface190, output device(s)192, dispenser firmware194, heating element(s)196, smart container sensor(s)199, and any number of containers250a. . .250n(individually or collectively also referred to as simply205) that may each include a smart container tag197. The components184,186,188,190,192,196, and199are communicatively coupled via a communications bus198. The controller188may include a non-transitory memory device, or may be coupled to a non-transitory memory device also coupled for communication via the bus198. The non-transitory memory device may store software that specially configures the controller, such as the dispenser firmware194. The PS184may be any AC and/or DC power supply for powering the scent dispenser132. The controller188may be a microchip that controls the constituent electronics (e.g., sensor(s)186, output device(s)192, interface190, heating element(s)196, etc.) of the scent dispenser132.

The set of sensor(s)186may include temperature sensors (e.g., thermocouples, etc.) for sensing the temperature of the heating element(s)196, ambient light sensor to detect a light level in a surrounding environment (e.g., room), and/or a motion sensor to detect motion in the surrounding environment, etc.

In some embodiments, the sensors186may include a temperature bay sensor for each heating element196(e.g., that may measure temperatures ranging from (−50 to 200 degrees Celsius), the container sensor300(e.g., seeFIG.3A), an ambient light sensor, etc.). The heating element196may be configured to heat to any suitable temperature sufficient to diffuse a scent solution contained in a corresponding container250, a non-limiting example of which may be 65 degrees Celsius, and the temperature bay sensor may be mounted on or adjacent to, or embedded in, the heating element196to measure the temperature of the heating element196and provide feedback to the controller188, which may cyclically heat the heating element196based on the feedback to maintain a constant or substantially constant temperature during diffusion (as set in the state settings).

The sensors186include a transceiver having a wireless interface configured to communicate with the devices coupled to the network102, such as the access point120, the dispenser management server150, and/or other components of the network102using standard communication protocols, such as Internet protocols. Further, the transceiver may be configured to wirelessly transmit data via a meshwork network made up of a plurality of scent dispensers132and/or other devices, such as the access point120or a mobile device106. By way of further example, the transceiver may transmit data to the access point120to which it is linked using a protocol compliant with IEEE 802.15, such as Zigbee®, Z-Wave®, Bluetooth®, or another suitable standard. Additionally or alternatively, one or more of the scent dispenser(s)132and/or the access point120of an installation158may be wired for direct communication and the wired components may exchange data using wired data communication protocols. Further embodiments are also possible and contemplated. In some embodiments, the transceiver may be embedded in the controller188or may be a component distinct from the controller and coupled to the controller188via the bus198.

The smart container sensor(s)199may include one or more of an optical sensor for detecting a specific smart container tag197of a scent container250that has an unique image or pattern (such as a QR code) detectable by the optical sensor, a container sensor for sensing the fill level of the container(s)250installed in the scent dispenser132, a radio antenna that can detect a smart container tag197, such as an RFID tag, or any other sensor that can detect a smart container tag197in proximity to the smart container sensor(s)199. In some implementations, the smart container sensor(s)199may be referred to as a reader and may be configured to read wireless electrical signals, such as from an RFID or other similar transmitting device.

The output device(s)192may include light sources and/or audio reproduction devices, although further suitable output devices are also contemplated and applicable. The light sources and/or audio reproduction devices may be controlled to produce output consistent with a scent being emitted by the scent dispenser (e.g., a low, soothing light and music may be output in conjunction with a relaxing scent being emitted).

Returning toFIG.1A, the client device(s)106(also referred to individually and collectively as106) are computing devices having data processing and communication capabilities. In some embodiments, a client device106may include a processor (e.g., virtual, physical, etc.), a memory, a power source, a network interface, and/or other software and/or hardware components, such as a display, graphics processor, wireless transceivers, keyboard, camera, sensors, firmware, operating systems, drivers, various physical connection interfaces (e.g., USB, HDMI, etc.).

The client devices106may couple to and communicate with one another and the other entities of the system100via the network102using a wireless and/or wired connection. Examples of client devices106may include, but are not limited to, mobile phones (e.g., feature phones, smart phones, etc.), tablets, smartwatches or other smart wearables, laptops, desktops, netbooks, server appliances, servers, virtual machines, TVs, set-top boxes, media streaming devices, portable media players, navigation devices, personal digital assistants, etc. In addition, while a single client device106is depicted inFIG.1A, it should be understood that any number of client devices106may be included.

As shown, the client device106may include a scent application108, which allows the user to set scent dispenser132settings, turn scent dispensers132on and off, purchase containers for the scent dispenser132, set up a scent dispenser132, register an account, set up a premises and the rooms of the premises, associate a scent dispenser132with a particular room of the premises, view analytics reflecting the user's historical use of his/her scent dispenser(s)132, enable user profiles to use and setup scent profiles for the scent dispenser(s) installed in the premises, set a profile hierarchy (e.g., set which user profile(s) is/are the dominant user profile), etc.

The client device106may store the scent application108in non-transitory memory, retrieve the scent application108from memory, and execute instructions comprising the scent application108. The scent application108, when executed by a processor of the client device106, configures the processor of the client device106to carry out the acts and functionality described herein. In some embodiments, the scent application108may render and display various interfaces for carrying out the functionality described herein.

Returning toFIG.1A, the dispenser management server150may include one or more computing devices having data processing, storing, and communication capabilities. For example, the server150may include one or more hardware servers, virtual servers, server arrays, storage devices and/or systems, etc., and/or may be centralized or distributed/cloud-based. In some embodiments, the server150may include one or more virtual servers, which operate in a host server environment and access the physical hardware of the host server including, for example, a processor, memory, storage, network interfaces, etc., via an abstraction layer (e.g., a virtual machine manager).

While not depicted, the server150may include a (physical, virtual, etc.) processor, a non-transitory memory, a network interface, and a data store170, which may be communicatively coupled by a communications bus. Similarly, the client device106may include a physical processor, a non-transitory memory, a network interface, a display, an input device, a sensor, and a capture device. It should be understood that the server and the client device may take other forms and include additional or fewer components without departing from the scope of the present disclosure.

Software operating on the server150(e.g., the dispenser management application160, an operating system, device drivers, etc.) may cooperate and communicate via a software communication mechanism implemented in association with a server bus. The software communication mechanism can include and/or facilitate, for example, inter-process communication, local function or procedure calls, remote procedure calls, an object broker (e.g., CORBA), direct socket communication (e.g., TCP/IP sockets) among software modules, UDP broadcasts and receipts, HTTP connections, etc. Further, any or all of the communication could be secure (e.g., SSH, HTTPS, etc.).

As shown, the server150may include a dispenser management application160embodying a remotely accessible scent service. The dispenser management application160may send data to and receive data from the other entities of the system including the controllers188and/or328, the mobile device(s)106, etc. The dispenser management application160may be configured to store and retrieve data from one or more information sources, such as the data store170. In addition, while a single server150is depicted inFIG.1A, it should be understood that one or more servers150may be included.

In some embodiments, the dispenser firmware194, the scent application108, the dispenser management application160, etc., may require users to be registered to access the acts and/or functionality provided by them. For example, to access various acts and/or functionality provided by the scent application108, dispenser management application160, and/or scent dispensers132, these components may require a user to authenticate his/her identity (e.g., by confirming a valid electronic address). In some instances, these entities108,132,150, etc., may interact with a federated identity server (not shown) to register/authenticate users. Once registered, these entities108,132,150, etc., may require a user seeking access to authenticate by inputting credentials in an associated user interface.

FIG.1Bincludes one or more scent containers250a-250n. although it should be understood that the container250may take a variety of different forms beyond what is described with respect toFIGS.2-4and have different dimensions. The scent containers250may include a scent solution that may include chemical(s) that are processed by the scent diffuser132to diffuse or nebulize it within the room in which the scent dispenser132is placed. The solution in some embodiments may be a liquid perfume, an essential oil, a scented gel, or other suitable solutions. In some alternative, the perfume or essential oil may be caked and the caked substrate may be heated to diffuse the scent. The scent container250may be made of any suitable material, such as plastic, metal, ceramic material, glass, etc.

In some embodiments as described with respect toFIGS.2-4, a container250(e.g., a first container, second container, etc.) may include a first side, one or more sidewalls, and a second side, such as to form a rectangular shape with a cavity in the center in which a scent solution may be held. In other embodiments, the container250may be cylindrical in shape with a hollow center that may hold the scent solution. In an example, a container250having a tubular sidewall may be a continuous around a circumference. In another example, a container250having a square, triangular, rectangular, etc., cross-section (e.g., halfway between the second side and the first side) at a middle of the sidewall, may have a plurality of sidewalls that are joined along at the corners of the cross-section. It should be understood that the container250may have any shape and is not limited to the shapes and configurations described herein. The one or more sidewalls connecting the first side to the second side. The first side, the one or more sidewalls, and the second side collectively form an inner cavity in which a scent solution is stored. The first side may include an opening through which a solution containable in the inner cavity can be dispensed from the container250. In some embodiments, the first side may include a neck forming the opening, and the sidewall(s) and second side form a hollow body. The hollow body may form a cavity containing the scented solution. In some implementations, a wick or other dispersal element may extend from the cavity through the opening of the neck.

In some embodiments, the container250may include a stopper and a wick. The stopper may insert into an opening of the container250and forms a seal against an inner surface of the neck or other surface of the body of the container250in order to keep scent solution from leaking other than through the dispersal element. The stopper includes a through-hole extending through a center portion of the stopper from an outer surface of the stopper to an inner surface of the stopper. The through-hole/opening is formed in the stopper to allow a wick inserted into the cavity of the container to extend outwardly from the through-hole, and thus the opening of the first side.

In some implementations, as shown with respect toFIGS.2-4, the container250may include a retaining mechanism and the retaining mechanism of the container250couples with a corresponding retaining mechanism included in a slot of the scent dispenser132. In some implementations, the retaining mechanism may be a protrusion extending outwardly from a surface of the container, such as the neck or the body of the container. In the specific example depicted, the protrusion extends around the circumference of the neck of the container250, and the retaining mechanism includes one or more coupling devices that engage with the retaining mechanism. In some embodiments, the coupling devices may comprise one or more fasteners formed to detachably engage with the neck of the container, while in other embodiments, the container250may sit within the container250without being held by a retaining mechanism.

It should be understood that other variations for the retaining mechanism are also possible and contemplated. For instance, the protrusion may engage with corresponding channels formed in a surface of the retaining mechanism into which protrusion slides into an opposing side(s). In another example, the neck includes a grove and the retaining mechanism includes corresponding protrusions or rails that mate with the grove. Numerous other variations are also possible and contemplated.

As illustrated inFIG.1Bthe scent dispenser132may include a heating element(s)196to heat the solution from the container(s)250installed in the scent dispenser132. In some embodiments, the wick passes a scented solution to the heating element196. The heating element196diffuses the scented solution by heating the scented solution to the temperature level regulated by the controller188.

An example heating element196may include a ceramic material (e.g., ceramic resistor, such as a wire wound ceramic heating element). Heating the solution received from the container250accelerates diffusion of the solution into the surrounding air. The housing (not shown) may include one or more ports in the lid to allow the diffused air to pass into the surrounding environment. The more heat applied by the diffusion device, the stronger the evaporative rate and thus the stronger the smell that may be produced.

In some embodiments, a scent solution of a container250may require a certain heating range to be diffused effectively, and the controller188may receive specific state settings for that scent solution from the dispenser management application160, which in some implementations may be provided by the identity of the scent container250found on the smart container tag197and use those settings to control the temperature of the corresponding heating element196.

FIG.2Ais an example scent dispenser132. As shown inFIG.2A, the scent dispenser132may have a removable outer housing (not shown) and the internal components may be configured for a scent container250to be installed in the scent dispenser132. As shown, in some implementations, a two scent container configured scent dispenser132may include a first slot280aand a second slot280bto allow for multiple different scent containers250a-250nto be installed. It should be understood that while two slots280are shown inFIG.2A, any number of slots280to allow for any number of scent containers250are contemplated, such as a single scent container slot or a multi-scent container scent dispenser132, with two scent container positions, three scent container positions, four scent container positions, etc. to allow multiple scent containers250to be positioned within the multi-container scent dispenser132. In some implementations, the slots280are formed out of a sidewall282on one side and a partition member284on the other side. In some instances, the partition member284may separate or divide the different slots280, while in other implementations, a partition member284may not be present and each slot280is an area in which a scent container250can be positioned without the partition member284. In some implementations, when a scent container250is positioned within the slot280, the partition member284may apply pressure against the side of the scent container250in order to cause the scent container250to be retained within the slot280. It should also be understood that in a single scent container250implementation, the partition member284may be absent and both sidewalls282may form the slot280in which the scent container250may be positioned.

As shown inFIG.2A, the scent dispenser132may include one or more smart container sensors199aand199b. The position of these smart container sensor(s)199a-199ballows the smart container sensor(s)199a-199bto be to be positioned proximate to scent container(s)250such that the smart container tag(s)197of each of the scent container(s)250may be readable by the smart container sensor(s)199a-199b, such as by being electrically connected to the smart container sensor(s)199a-199b. In this example, the smart container sensor(s)199a-199bmay be electrical contacts configured to interact with corresponding electrical contacts on the smart container tag197aas shown. The corresponding electrical contacts of the smart container tag197may be part of a circuit forming the smart container tag197. The circuit of the smart container tag197may store various smart container data183directly on the circuit, such as an identity of the scent solution in the scent container250, a fill level of the scent container250, usage data of the scent container250, previous locations of the scent container250, refill data of the scent container250, order/purchase data of the scent container250, etc.

As shown inFIG.2B, as the scent container250is inserted into the slot280aand contact is made between the respective contacts of the smart container sensors199aand the smart container tag197(not shown as the left side of the scent container is not visible in the front vial as shown), the controller of the apparatus can detect the smart container data183, such as an identity of the smart container250, an identity/type of the sent solution, ingredients of the scent solution, etc. based on signals from the vial circuit and the smart container tag197. The controller188of the scent device132can read information from the smart container tag197, such as an identity of the scent container250, the amount of scent that the scent container contains, etc. based on signals from the smart container tag197. For example, the scent container tag197may be configured to store smart container data183identifying the scent solution (e.g., a unique identifier associated with the scent solution), ingredients of the scent solution, an identifier of the scent container250, etc. and the controller188may access a lookup table or other similar functionality to determine which scent it is. The circuit of the smart container tag197may also store information about when the scent solution/container was manufactured, and how long the container has been used (such as how long a scent has been dispensed from the scent container250). For example, the controller188can write to the circuit (a memory thereof) of the smart container tag197usage data reflecting how long the scent container250has been used. If a user112removes a scent container250and then replaces it later, the controller188can detect how much solution is left/available for dispensation (2 hours have been used, 30 are left, and so forth) based on information provided by the scent container tag197. In further implementations, rather than storing the smart container data183on the circuit, the smart container data183can be stored on the server150and the smart container tag197includes the unique identifier that the smart container data183associated with that smart container tag197unique identifier is associated with that smart container data183stored and read on the server150.

FIG.3Ais another example scent dispenser132. As shown inFIG.3A, the scent dispenser132may have a removable outer housing (not shown) and the internal components may be configured for a scent container250to be installed. As shown, the scent dispenser132may include a first slot280aand a second slot280bto allow for multiple different scent containers250a-250nto be installed. It should be understood that while two slots280are shown inFIG.3A, any number of slots280may be included to allow for any number of scent containers250that may be contemplated as described elsewhere herein. Such as a single slot280for a single scent container250or multi-container scent dispensing devices132, etc. In some implementations, the slots280are formed out of a sidewall282on one side and a partition member284on the other side. In some instances, the partition member284may separate the different slots280. It should also be understood that in a single scent container250implementation or in other implementations where a partition member284is not present, the partition member284may be absent and both sidewalls282may form the slots280in which the scent containers250may be positioned.

As shown inFIG.3A, the scent dispenser132may include one or more smart container sensors199cand199d. In this example, the smart container sensor(s)199c-199dmay be radio transmitters/receivers that can be configured to read a smart container tag197bin the form of a radio transponder that can broadcast a unique scent container identifier. In some implementations, the position of these smart container sensor(s)199c-199dallows the smart container sensor(s)199c-199dto be to be positioned directionally proximate to scent container(s)250such that the smart container tag197bof the scent container(s)250may be proximate to the smart container sensor(s)199c-199dwithout touching the smart container sensor(s)199c-199din order to allow wireless signals to pass from the smart container tag197bto the smart container sensor199cand provide smart container data183to the smart container sensor(s)199c-199d. As shown inFIG.3A, the smart container tag197bmay be a form of antenna connected to a circuit that can read/write smart container data183wirelessly to and from the smart container sensor199c. In other implementations, the smart container tag197may read the smart container data183, such as a unique identifier of the scent container250, wirelessly and then may store additional smart container data183on the server150and the smart container data183may be stored as being associated with the unique identifier of the smart container tag197.

The smart container tag197bin some implementations may be positioned on a bottom surface of a scent container250. When positioned on a bottom surface of the scent container250, a user112may not have to position the scent container250in a specific orientation in the slot280, but instead may merely install the scent container250into the slot280independent of the direction the scent container250is rotated, the smart container tag197bcan be read by the smart container sensor199c. This allows for a user to install the scent container250and the smart container tag197ccan be read independent of how the user rotates the scent container250when positioned in the slot280. In further implementations, the smart container tag197can be positioned at other points along the scent container250and the smart container sensor can be correspondingly positioned in the scent dispenser132to read/write the smart sensor tag197.

In some implementations, when multiple scent containers250are positioned, the smart container sensors199c-199dmay each directional point towards their respective smart container tags197on their associated smart containers250without picking up interference from the other smart container tags197positioned within the scent dispenser132. This directionality of the smart container sensors199allows for interference to be reduced between the smart container sensors199and reduces the chances of interference interrupting the process of reading the smart container tag197by the smart container sensor199. In further implementations, interference shielding, may be positioned between the different smart container sensors199to further reduce the chances of interference between the smart container sensors199.

As shown inFIG.3B, as the scent container250is positioned into the slot280aand the scent container tag197bcomes within a threshold distance for reading/writing the smart container tag197bby the smart container sensor199c, the smart container tag197bcan begin sharing the smart container data183with the controller188. For example, the scent container tag197bmay be configured to store smart container data183identifying the scent solution (e.g., a unique identifier associated with the scent solution), and the controller188may access a lookup table or other similar functionality to determine which scent it is. In another example, the controller188can write to the circuit (a memory thereof) of the smart container tag197busage data reflecting how long the scent container250has been used. If a user112removes a scent container250and then replaces it later, the controller188can detect how much solution is left/available for dispensation based on information provided by the scent container tag197.

FIG.4Adepicts another example view of a portion of a scent dispenser132. As shown, the scent dispenser132may include one or more scent containers250a-250bpositioned within respective slots280a-280b. As shown, a slot housing402may separate the space forming the slots280from other components of the scent dispenser132(not shown , as they are hidden by the slot housing402). In some implementations, the slot housing402may include one or more holes404or access point through which the smart container sensor(s)199may pass wireless signals (such as radio frequency signals) to and from the smart container tag197(not shown, but located on a bottom portion of the scent container150as shown inFIG.4A). As shown in this example, the smart container sensor199c(depicted in broken lines as it is hidden behind the slot housing402) may be positioned directionally, such as at an angle below the hole404asuch that it can read the smart container tag197(not shown) positioned on a surface, such as a bottom surface, of the scent container250awhen the scent container250ais positioned within the slot280a. The hole404aor access point allows for wireless signals to pass without interference and in some implementations, where the distance between the smart container tag197and the smart container sensor199cis small enough that the smart container tag197and the smart container sensor199care almost adjacent, the slot housing404can act as a shield to direct the signals towards the smart container tag197and prohibit and unwanted signals or interference from another source from affecting what is being provided to the smart container sensor199c. This allows the slot housing404to protect the smart container sensor199from interference.

FIG.4Bdepicts another example of the smart container sensor199creading/writing smart container data183to and from the smart container tag197b. As shown in this example, the smart container tag197band the smart container sensor199care not touching, but are proximate to each other. In some implementations, the smart container sensor199cmay include a directional antenna that allows signals to be passed directionally towards the smart container tag197band not pass signals in other direction to avoid interference or other unwanted data. This directionality of the antenna allows for multiple scent containers250with smart container tags197to be positioned adjacent to each other without the smart container sensor(s)199providing interference with each other. In some implementations, the smart container sensor199may be directionally positioned to have a direct line of sight with the smart container tag197bto read the smart container tag197bwhen the scent container250is securely retained in the scent retaining apparatus of the scent dispenser132.

In some implementations, the scent dispenser132may include output devices192in the form of a ring of LEDs (e.g., light pipe) that are programmable to change based on a scent dispensation program. Changes may include different intensities, colors, patterns, and so forth. In some embodiments, the light patterns may reflect the state of the scent dispenser132(error state, instructions, low scent, change scent container, etc.). For example, if the scent container250on the left side is low or out, the lights on the left side may light up in red to reflect such (or if both are out both sides would illuminate in red, and so forth).

The ring of lights may be distributed equally around the front of the apparatus or in other suitable ways. On a backside of the front cover, the cover may include contacts that connect to contacts on the front of the front of the inside body of the apparatus when the cover is attached (e.g., magnetically or via other fasteners) to the inside body. As such, the contacts between the cover and the inside body decouple when the cover is removed, automatically turning the LEDs off (if on), or back on when the cover is replaced.

FIG.5is a flowchart of an example method for smart container detection. At step510, a smart container sensor199detects that a scent container250with a smart container tag197included, such as on a surface of the scent container250, has been positioned in a slot280of a scent dispenser132. The smart container sensor199may detect that the scent container250is positioned in the first slot by detecting the smart container tag197, such as by electrically coupling or wireless signals as described elsewhere herein. At step520, the smart container sensor199may receive smart container data183from the smart container tag197. At step130, a controller188may receive the smart container data183from the smart container sensor199and determine an identity of the scent container250using the smart container data. In some implementations, the controller may determine the identity of the scent container250by identifying a unique identifier included in the smart container data183and may use the unique identifier to access additional smart container data183stored on the server150that includes the identity of the scent container250based on the unique identifier.

At step540, the controller188may determine current usage data of the scent container250, such as based on scent diffusion seatings, the heating element usage, etc. The current usage data may include data captured by the scent dispenser132that includes run-time for different scent containers250, schedules of different scent containers250, installations/refill of different scent containers250, fill levels of different scent containers250, etc. The current usage data may also include analytics data that is captured and/or generated by the dispenser management application160and stored on the server150, which may then provide the current usage data to the controller188as needed. At step550, the controller188may update the smart container data183to include the current usage data by having the smart container sensor199provide the current usage data to the smart container tag197. In further implementations, the controller188may update the smart container data183to include the current usage data by providing the current usage data to the smart container data183stored on the server150and having the dispenser management application160update the stored smart container data183. In some implementations, the dispenser management application160may retrieve and/or update the stored smart container data183based on the unique identifier detected on the smart container tag197. Each of the smart container data183stored on the server150may be associated with different unique identifiers that are readable from smart container tags197on different scent containers250.

FIG.6is a block diagram of an example smart container tracking system. As described elsewhere herein, using a smart container tag197allows a scent container250to be tracked throughout the lifetime of the scent container250. As the smart container250is manufactured through the end of use of the scent container250, the smart container tag197can store various data related to the scent container250. For example, as shown at602, a supplier can prepare a smart container tag197for attaching to a scent container250during manufacturing. By preparing a smart container tag197that is unique for each scent container250, the supplier can provide protection against fraudulent vials and ensure that the correct scent containers250are being used based on the unique identifier of each smart container tag197. As each smart container tag197stores the data locally, such as on the circuit of the smart container tag197, the data for the scent container250is tracked starting from the initial setup of the smart container tag197.

At block604, a manufacturer can build and assemble various scent containers250and affix them with a smart container tag197, such as an NFC antenna. By affixing a unique smart container tag197to each scent container250, the scent container functionality and compatibility with various devices can be easily tracked. Additionally, batch data and manufacturing environment information can be stored on the smart container tag197to assist in recalls or other situations, such as where a batch overperforms and the data can be accessed to identify any outliers that provide explanations.

At block606, the copacker during manufacturing can fill each scent container250with fragrance and finalize the finished product. Using the smart container tag197, each scent container250can connect unique product data directly to their unique smart container tag197. This ensures additional data validity and/or provides ability to track expiration of fragrances by each scent container250. For example, a batch of scent containers250can be packaged and then each scent container250includes their own packaged expiration data on each smart container tag197that automatically will provide updates and/or notifications when connected with a smart container sensor199. At block608, the third party logistics can package orders and send them out to customers. Using a smart container tag197, each scent container250can be scanned and tracked by a separate smart container sensor199to update information and track various aspects of the scent containers250. By tracking the smart container tag197, the third party logistics can connect shipping location data to each unique smart container tag197and ensure data validity. By attaching the data to the smart container tag197, that data is persistent with the scent container250, not just the packaging or some other conventional tracking mechanism. This allows for tracking, under privacy considerations, to monitor customer behaviors, such as gifting, vial swapping, stealing of scent containers250, retail conversion, etc.

At608, a user112can install a scent container250and automatically have the smart container tag197read for relevant data. This allows a user112to order a product, unbox it, and install the vial without having to do any tracking or entering of serial numbers for registration, etc. The smart container tag197automatically connects and streamlines the user experience. Additionally, as the user112enjoys a scent experiences and plans for a lifetime of the scent container250, the scent container250is able to monitor and track the relevant data related to usage settings and remaining scent, and store that locally on the scent container250. This allows for that data to be persistent, even if the scent container250is moved to a different scent dispenser132, regifted to a separate user112, unplugged and unused for a period of time before being reinstalled, etc. This data remains with the scent container250and can quickly by used to provide updates to a user112as needed. The smart container tag197provides a connected time stamp when a scent container250is installed in a scent dispenser132. It provides the ability for accurate remaining scent calculations using the various timestamps and automatically updates any scent container250changes, such as swapping a scent without the user112having to manually enter any information. Additionally, as the scent container250is used, all of the data is persistent and provides accurate messaging throughout the scent container250lifespan.

At610, when a scent container250is removed, the time stamp of removal can be captured and stored on the smart container tag197. This can be used to track when scent containers250are disposed of/refilled/replaced. A user does not have to do any manually entering of information when scent containers250are removed or switched out. Additionally, in some implementations, at612, a recycling option can be used, where when a vial is empty or removed a supplier can automatically ship out a return box for a user to place the removed scent container250into. The scent container250is then tracked as it is returned and refilled for future use. In some implementations, the persistent data on the smart container tag197is preserved after being refilled for a full lifetime dataset of the scent container250. While in further implementations, the smart container tag197is replaced when the scent container250is repurposed. By using a scent container250with a smart container tag197that automatically provides tracking data when installed, a user experience can be further streamlined and a more accurate data set of the use of the scent container250can be preserved for the scent container250. In some implementations, the data set of the use of the scent container250based on the smart container tag197can be used with artificial intelligence and/or machine learning to generate additional analytics about the use of the scent container250and potential customer insights based on the generated additional analytics.

The foregoing description, for purpose of explanation, has been described with reference to various embodiments and examples. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The various embodiments and examples were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to utilize the innovative technology with various modifications as may be suited to the particular use contemplated. For instance, it should be understood that the technology described herein can be practiced without these specific details in some cases. Further, various systems, devices, and structures are shown in block diagram form in order to avoid obscuring the description. For instance, various implementations are described as having particular hardware, software, and user interfaces. However, the present disclosure applies to any type of computing device that can receive data and commands, and to any peripheral devices providing services.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout this disclosure, discussions utilizing terms such as “processing,” “computing,” “calculating,” “determining,” “displaying,” or the like, refer to the action and methods of a computer system that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.

A data processing system suitable for storing and/or executing program code, such as the computing system and/or devices discussed herein, may include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories that provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution. Input or I/O devices can be coupled to the system either directly or through intervening I/O controllers. The data processing system may include an apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer.

The foregoing description has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the specification to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the disclosure be limited not by this detailed description, but rather by the claims of this application. As will be understood by those familiar with the art, the specification may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Likewise, the particular naming and division of the modules, routines, features, attributes, methodologies and other aspects may not be mandatory or significant, and the mechanisms that implement the specification or its features may have different names, divisions, and/or formats.

Furthermore, the modules, routines, features, attributes, methodologies and other aspects of the disclosure can be implemented as software, hardware, firmware, or any combination of the foregoing. The technology can also take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. Wherever a component, an example of which is a module or engine, of the specification is implemented as software, the component can be implemented as a standalone program, as part of a larger program, as a plurality of separate programs, as a statically or dynamically linked library, as a kernel loadable module, as firmware, as resident software, as microcode, as a device driver, and/or in every and any other way known now or in the future. Additionally, the disclosure is in no way limited to implementation in any specific programming language, or for any specific operating system or environment. Accordingly, the disclosure is intended to be illustrative, but not limiting, of the scope of the subject matter set forth in the following claims.