Connected evaporator unit system

Abstract

A vaporizer system may include a vaporizer device communicatively coupled to a user device, the user device configured to control functions and / or features of the vaporizer device. The vaporizer device can be used as a replacement for traditional combustible cigarettes. Accordingly, the user device can be configured to collect usage data from the vaporizer device and generate recommendations to enhance and / or accelerate the transition from traditional combustible cigarettes to the vaporizer device. For example, the user device can provide puff training to achieve a more satisfying initial experience. Alternatively and / or additionally, the user device can recommend a pod type and / or puffing pattern associated with a reduction in overall intake.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 824,725, filed on March 27, 2019, entitled “Connected Evaporator Apparatus System,” U.S. Provisional Patent Application No. 62 / 793,889, filed on January 17, 2019, entitled “Connected Evaporator Apparatus System,” U.S. Provisional Patent Application No. 62 / 760,918, filed on November 13, 2018, entitled “Connected Evaporator Apparatus System,” and U.S. Provisional Patent Application No. 62 / 690,947, filed on June 27, 2018, entitled “Connected Evaporator Apparatus System,” the disclosures of which are incorporated herein by reference in their entireties.

[0003] This application is also related to U.S. Patent Application No. 15 / 605,890, filed on May 25, 2017, and entitled “Electronic Vaporizer Control,” which claims priority to U.S. Provisional Patent Application No. 62 / 341,579, filed on May 25, 2016, and entitled “Electronic Vaporizer Control,” the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0004] The devices, systems, and methods described herein relate to vaporization devices (e.g., electronic vaporizer devices) and methods of using, controlling, manufacturing, and the like. The devices may optionally include a device having two or more parts, such as a cartridge containing a vaporizable substance and a body portion including one or more other components. The subject matter described herein also relates to methods, techniques, devices, and systems for providing guidance on how to use a vaporizer device to achieve a more satisfying experience. Methods, techniques, devices, and systems for providing inhalation or puff training for a vaporizer device are described below. Background Art

[0005] Vaporizer devices are generally intended to be, and often are, effective replacements for traditional combustible cigarettes. Traditional combustible cigarette smokers often turn to vaporizer devices as an alternative in an attempt to reduce their consumption of traditional combustible cigarettes. Smokers seeking to replace traditional combustible cigarettes with vaporizer devices need to learn how to use the vaporizer device as an effective alternative.

[0006] A vaporizer device, which may also be referred to as a vaporizer, electronic vaporizer device, or E-vaporizer device, can be used to deliver an aerosol (or "vapor") containing one or more active ingredients through inhalation of the aerosol by a user of the vaporizing device. For example, electronic nicotine delivery systems (ENDS) include a class of battery-powered vaporizer devices that can be used to simulate the experience of smoking a cigarette without burning tobacco or other substances.

[0007] Electronic vaporizer devices can be particularly portable, self-contained, and easy to use. Although many devices are recently available that can communicate wirelessly with an external controller (e.g., a smartphone), such devices can be controlled by one or more switches, buttons, etc. (controls) on the vaporizer.

[0008] Such wireless control is primarily limited to temperature settings and other features that can, and can, be more conveniently performed on the device itself. These systems may not automate or calibrate device operation based on detection of the material or material type loaded into the device. Such systems also generally may not track dosage and / or allow for device modification based on dosage information. Furthermore, the currently described systems may not provide for social interaction with other users. For example, with regard to dosage, previous attempts to determine the dosage of vapor and / or active ingredient in the vapor have been unsatisfactory. Systems that predetermine dosage by limiting the amount of material to be delivered in a treatment session often incorrectly assume that all material will be inhaled and may not be able to adjust for partial doses. Such systems may also meter the amount of material and require precise measurement of the mass and / or volume of the material delivered for vaporization, or the difference between the initial mass / volume and the mass or volume after delivery. These measurements can be difficult, require high accuracy and expense, and may result in inaccurate results. Furthermore, current dose-controlled electronic smoking devices typically control the delivered dose without being linked to or having actual knowledge of the user's actual clinical and medical needs, and may not allow the controlled dose to be adjusted based on the user's biometrics, such as weight, age, and symptoms, etc. Existing systems may also lack features that allow users to customize usage according to their habits and goals, as well as their social needs.

[0009] When using a vaporizer device, a user inhales an aerosol, often referred to as vapor, which may be generated by a heating element that vaporizes (usually referring to converting a liquid or solid at least partially into a gaseous phase) a vaporizable material, which may be a liquid, solution, solid, wax, or any other form compatible with use with a particular vaporizer device. The vaporizable material used with a vaporizer may be disposed within a cartridge (e.g., the portion of a vaporizer that contains the vaporizable material in a reservoir) that includes a mouthpiece (e.g., for the user to inhale).

[0010] To receive the inhalable aerosol generated by the vaporizer device, in some instances, a user can activate the vaporizer device by drawing a puff, by pressing a button, or by other methods. "Puffing," as the term is commonly used (and also used herein), means that the user inhales in a manner that causes a volume of air to be drawn into the vaporizer device, such that an inhalable aerosol is generated by the combination of vaporized vaporizable material and air.

[0011] A typical method by which a vaporizer device generates an inhalable aerosol from a vaporizable material involves heating the vaporizable material in a vaporization chamber (or heater chamber) to convert the vaporizable material into a gas (or vapor) phase. The vaporization chamber generally refers to the area or volume in the vaporizer device in which a heat source (e.g., conductive, convective, and / or radiative) causes heating of the vaporizable material to produce a mixture of air and vaporized vaporizable substance, thereby forming a vapor for inhalation by a user of the vaporization device.

[0012] In some embodiments of the evaporator device, the evaporable material can be drawn out of the reservoir and drawn into the evaporation chamber by a wicking element (wick). Such drawing of the evaporable material into the evaporation chamber can be at least partially due to the capillary action provided by the wick, which pulls the evaporable material along the wick toward the evaporation chamber. However, as the evaporable material is drawn out of the reservoir, the pressure inside the reservoir decreases, thereby creating a vacuum and opposing the capillary action. This reduces the efficiency of the wick in drawing the evaporable material into the evaporation chamber, thereby reducing the efficiency of the evaporation device in evaporating the required amount of evaporable material, for example, when a user draws on the evaporator device. In addition, the vacuum generated in the reservoir may ultimately result in the inability to draw all the evaporable material into the evaporation chamber, thereby wasting the evaporable material. Therefore, there is a need for an improved evaporation device and / or evaporation cartridge that improves or overcomes these problems.

[0013] As used herein, the term vaporizer device, consistent with the present subject matter, generally refers to a portable, self-contained device that is convenient for personal use. Typically, such devices are controlled by one or more switches, buttons, touch-sensitive devices, or other user input functions (generally referred to as controls) on the vaporizer, but many devices that can wirelessly communicate with external controllers (e.g., smartphones, smartwatches, other wearable electronic devices, etc.) have recently become available. As used herein, control generally refers to the ability to affect one or more of a variety of operating parameters, which may include, but are not limited to, causing the heater to turn on and / or off, adjusting operations that a user may access on the device, the minimum and / or maximum temperatures to which the heater can heat during various games or other interactive features, and / or other operations.

[0014] A variety of vaporizable materials, with various contents and ratios of such contents, can be contained in a cartridge. For example, due to regulatory requirements for certain percentages of active ingredients, certain vaporizable materials may have a smaller percentage of active ingredient relative to the total volume of the vaporizable material. Thus, a user may need to vaporize a larger amount of vaporizable material (e.g., compared to the total volume of vaporizable material that can be stored in the cartridge) to achieve a desired effect. The systems, devices, and methods described herein address at least these issues and concerns. Summary of the Invention

[0015] Systems, methods, and articles of manufacture, including apparatus and computer program products, are provided for use with connected vaporizer devices. In one aspect, a system is provided that includes at least one processor and at least one memory. The at least one memory may include program code that, when executed by the at least one processor, provides operations. The operations may include: receiving first usage data associated with a first user interacting with a first vaporizer device; and determining, based at least on the first usage data, a first recommendation for the first user interacting with the first vaporizer device and / or a second vaporizer device.

[0016] In some variations, one or more features disclosed herein, including the following features, may optionally be included in any feasible combination. The first usage data may include the flavor of the vaporizable material in the cartridge inserted into the first vaporizer device, the strength of the vaporizable material, the amount of vaporizable material remaining in the cartridge, the timing of one or more puffs on the first vaporizer device, the strength of the one or more puffs, the duration of the one or more puffs, the frequency of the one or more puffs, the total dose of active ingredient delivered by the one or more puffs, and / or the length of time between two or more consecutive puffs.

[0017] In some variations, the first usage data may further include user input indicating the smoothness of vapor puffed by one or more puffs. The user input may include motion and / or sound associated with the user coughing, tapping the vaporizer device, shaking the vaporizer device, and / or moving the vaporizer device in a particular pattern.

[0018] In some variations, the first recommendation may include a flavor and / or strength of the vaporizable material based at least on being associated with a lower frequency of puffs, a lower total dose of active ingredient delivered, and / or a longer length of time between two or more consecutive puffs than another flavor and / or strength of the vaporizable material.

[0019] In some embodiments, the first recommendation may include the timing of one or more puffs based at least on the timing of the one or more puffs being associated with a lower puff frequency, a lower total dose of active ingredient delivered, and / or a longer length of time between two or more puffs than another timing of the one or more puffs.

[0020] In some variations, a first user may be determined to be similar to a second user. A second recommendation for the second user interacting with a third vaporizer device may be determined based at least on the first usage data. The first user and the second user may be determined to be similar based at least on one or more attributes associated with each of the first user and the second user, wherein the one or more attributes include demographic information, preferences, and / or smoking cessation goals. The first user and the second user may be determined to be similar by at least applying a clustering algorithm configured to identify one or more groups of similar users based on the one or more attributes associated with each of the first user and the second user. The second recommendation may include the flavor of the vaporizable material in the cartridge inserted into the first vaporizer device, the strength of the vaporizable material, the timing of one or more puffs on the first vaporizer device, the strength of the one or more puffs, the duration of the one or more puffs, the frequency of the one or more puffs, the total dose of active ingredient delivered by the one or more puffs, and / or the length of time between two or more consecutive puffs.

[0021] In some variations, the first usage data may include a first type of data having a first sampling rate and a second type of data having a second sampling rate.

[0022] In some variations, sample aggregation may be performed to generate one or more data samples having a third sampling rate that is lower than the first sampling rate and the second sampling rate based on a first plurality of data samples including data of the first type and / or a second plurality of data samples including data of the second type. The one or more data samples having the third sampling rate may be stored in a log. The third sampling rate may be determined based at least on whether the one or more data samples include behavioral data or diagnostic data. The third sampling rate may be determined based at least on the first user having a goal of transitioning from combustible cigarettes to a vaporizer device, reducing combustible cigarette use, and / or reducing vaporizer device use.

[0023] In some variations, a large number of aggregations may be performed to generate a metric based on a first plurality of data samples including data of a first type. The metric may be generated based on the first plurality of data samples collected by a single thread. Generation of the metric may also exclude a second plurality of data samples collected by another thread. The metric may include a temperature rise time, an observed temperature, a deviation from a temperature set point, a pressure differential, a maximum pressure differential, a minimum pressure differential, and / or an average pressure differential.

[0024] In some variations, a user interface may be generated. The user interface may be configured to display the first recommendation on a user device associated with the first user.

[0025] In some variations, the first recommendation may be further generated based on a usage pattern of the combustible cigarette. The usage pattern may include a brand of combustible cigarettes, a type of combustible cigarette, and / or an amount of combustible cigarettes consumed by the first user. The first recommendation may include the strength of the vaporizer material in the cartridge inserted into the first vaporizer device, the timing of one or more puffs on the first vaporizer device, the strength of the one or more puffs, the duration of the one or more puffs, the frequency of the one or more puffs, the total dose of active ingredient delivered by the one or more puffs, and / or the length of time between two or more consecutive puffs that deliver the same amount of active ingredient to the first user as the combustible cigarettes consumed by the first user.

[0026] In some variations, the first usage data may be received from a user device coupled to the first vaporizer device.

[0027] In another aspect, a method may include receiving first usage data associated with a first user interacting with a first vaporizer device; and determining a first recommendation for the first user interacting with the first vaporizer device and / or a second vaporizer device based at least on the first usage data.

[0028] In some variations, one or more features disclosed herein, including the following features, may optionally be included in any feasible combination. The first usage data may include the flavor of the vaporizable material in the cartridge inserted into the first vaporizer device, the strength of the vaporizable material, the amount of vaporizable material remaining in the cartridge, the timing of one or more puffs on the first vaporizer device, the strength of the one or more puffs, the duration of the one or more puffs, the frequency of the one or more puffs, the total dose of active ingredient delivered by the one or more puffs, and / or the length of time between two or more consecutive puffs.

[0029] In some variations, the first usage data may further include user input indicating the smoothness of vapor puffed by one or more puffs. The user input may include motion and / or sound associated with the user coughing, tapping the vaporizer device, shaking the vaporizer device, and / or moving the vaporizer device in a particular pattern.

[0030] In some variations, the first recommendation may include a flavor and / or strength of the vaporizable material based at least on being associated with a lower frequency of puffs, a lower total dose of active ingredient delivered, and / or a longer length of time between two or more consecutive puffs than another flavor and / or strength of the vaporizable material.

[0031] In some embodiments, the first recommendation may include the timing of one or more puffs based at least on the timing of the one or more puffs being associated with a lower puff frequency, a lower total dose of active ingredient delivered, and / or a longer length of time between two or more consecutive puffs than another timing of the one or more puffs.

[0032] In some variations, the method may further include: determining that the first user is similar to the second user based on at least one or more attributes associated with each of the first user and the second user, the one or more attributes including demographic information, preferences, and / or smoking cessation goals; and determining a second recommendation for the second user to interact with the third vaporizer device based on at least the first usage data. The first user and the second user may be determined to be similar by at least applying a clustering algorithm configured to identify one or more groups of similar users based on the one or more attributes associated with each of the first user and the second user.

[0033] In some variations, the first recommendation may be further generated based on a usage pattern of the combustible cigarette. The usage pattern may include a brand of combustible cigarettes, a type of combustible cigarette, and / or an amount of combustible cigarettes consumed by the first user. The first recommendation may include the strength of the vaporizer material in the cartridge inserted into the first vaporizer device, the timing of one or more puffs on the first vaporizer device, the strength of the one or more puffs, the duration of the one or more puffs, the frequency of the one or more puffs, the total dose of active ingredient delivered by the one or more puffs, and / or the length of time between two or more consecutive puffs that deliver the same amount of active ingredient to the first user as the combustible cigarettes consumed by the first user.

[0034] In another aspect, a computer program product is provided that includes a non-transitory computer-readable medium storing instructions. The instructions may cause operations executable by at least one data processor. The operations may include receiving usage data associated with a first user interacting with a first vaporizer device; and determining, based at least on the usage data, a first recommendation for the first user interacting with the first vaporizer device and / or a second vaporizer device and / or a second recommendation for a second user interacting with a third vaporizer device.

[0035] In another aspect, a system is provided that includes a first vaporizer device, a user device communicatively coupled to the first vaporizer device, and a remote server. The remote server may include at least one processor and at least one memory. The at least one memory may include program code that, when executed by the at least one processor, provides operations. The operations may include: receiving usage data associated with a first user interacting with the first vaporizer device from the user device; and determining, based at least on the usage data, a first recommendation for the first user interacting with the first vaporizer device and / or a second vaporizer device, and / or a second recommendation for a second user interacting with a third vaporizer device.

[0036] In another aspect, a device is provided. The device may include: means for receiving, from a user device, usage data associated with a first user interacting with a first vaporizer device; and means for determining, based at least on the usage data, a first recommendation for the first user to interact with the first vaporizer device and / or a second vaporizer device and / or a second recommendation for a second user to interact with a third vaporizer device.

[0037] In another aspect, a system is provided that includes at least one processor and at least one memory. The at least one memory may include program code that, when executed by the at least one processor, provides operations. The operations may include receiving first data including one or more puff characteristics, the one or more puff characteristics determined based on at least a first puff on a vaporizer device; and determining an adjustment to the one or more puff characteristics based at least on the first data.

[0038] In some variations, one or more features disclosed herein, including the following, may optionally be included in any feasible combination: One or more puff characteristics may include the intensity of the puff, the duration of the puff, and / or the amount of time between two or more consecutive puffs.

[0039] In some variations, the one or more puff characteristics may include a mean, median, maximum, minimum, mode, and / or range of the one or more characteristics associated with the first puff and the second puff on the vaporizer device.

[0040] In some variations, the adjustment may be further determined based on a difference between one or more puff characteristics and one or more optimal puff characteristics. An indication of the difference between the one or more puff characteristics and the one or more optimal puff characteristics may be output to the user. The indication may be output to the user by at least generating a graphical user interface configured to display the indication. The indication may be output to the user using one or more light emitting diodes (LEDs), sound, and / or tactile feedback.

[0041] In some variations, one or more optimal puff characteristics may be determined based at least on the flavor, concentration, and / or amount of vaporizable material remaining in a cartridge inserted into a vaporizer device. The flavor, concentration, and / or amount of vaporizable material remaining in the cartridge may be determined by at least reading a characteristic associated with the cartridge. The characteristic may be encoded in a pattern and / or circuit.

[0042] In some variations, second data including user feedback associated with at least a first puff may be received. Adjustments to one or more puff characteristics may be further determined based on the second data. The user feedback may include user input indicating a smoothness of vapor puffed by the first puff. A user interface may be generated that is configured to receive user input from a user indicating a smoothness of vapor puffed by the first puff. The user input may include motion associated with the user coughing, tapping the vaporizer device, shaking the vaporizer device, and / or moving the vaporizer device in a particular pattern. The user input may include sounds associated with the user coughing, tapping the vaporizer device, shaking the vaporizer device, and / or moving the vaporizer device in a particular pattern.

[0043] In some variations, a user interface configured to display adjustments to one or more puff characteristics to a user may be generated.

[0044] In some variations, the first data may be received from the vaporizer device via a wireless communication link.

[0045] In another aspect, a method is provided that may include receiving first data including one or more puff characteristics determined based on at least a first puff on a vaporizer device, and determining an adjustment to the one or more puff characteristics based at least on the first data.

[0046] In some variations, one or more features disclosed herein, including the following, may optionally be included in any feasible combination: One or more puff characteristics may include the intensity of the puff, the duration of the puff, and / or the amount of time between two or more consecutive puffs.

[0047] In some variations, the one or more puff characteristics may include a mean, median, maximum, minimum, mode, and / or range of the one or more characteristics associated with the first puff and the second puff on the vaporizer device.

[0048] In some variations, the adjustment may be further determined based on a difference between the one or more puff characteristics and the one or more optimal puff characteristics. The method may also include outputting an indication of the difference between the one or more puff characteristics and the one or more optimal puff characteristics to the user. The indication may be output to the user by at least generating a graphical user interface configured to display the indication. The indication may be output to the user using one or more light emitting diodes (LEDs), sound, and / or tactile feedback.

[0049] In some variations, one or more optimal puff characteristics may be determined based at least on the flavor, concentration, and / or amount of vaporizable material remaining in a cartridge inserted into a vaporizer device. The method may also include determining the flavor, concentration, and / or amount of vaporizable material remaining in the cartridge by at least reading a characteristic associated with the cartridge. The characteristic may be encoded in a pattern and / or circuit.

[0050] In some variations, the method may further include: receiving second data comprising user feedback associated with at least the first puff; and determining an adjustment to one or more puff characteristics further based on the second data. The user feedback may include user input indicating a smoothness of vapor puffed by the first puff. The user input may include motion associated with a user coughing, tapping the vaporizer device, shaking the vaporizer device, and / or moving the vaporizer device in a particular pattern. The user input may include sounds associated with a user coughing, tapping the vaporizer device, shaking the vaporizer device, and / or moving the vaporizer device in a particular pattern.

[0051] In some variations, the method may further include generating a user interface configured to display adjustments to one or more puff characteristics to a user.

[0052] In some variations, the first data may be received from the vaporizer device via a wireless communication link.

[0053] In another aspect, a computer program product is provided that includes a non-transitory computer-readable medium storing instructions. The instructions may cause operations executable by at least one data processor. The operations may include receiving data including one or more puff characteristics determined based on at least one or more puffs on a vaporizer device; and determining an adjustment to the one or more puff characteristics based at least on the data.

[0054] In another aspect, a system is provided that includes a vaporizer device, a user device communicatively coupled to the vaporizer device, and a remote server. The remote server may include at least one processor and at least one memory. The at least one memory may include program code that, when executed by the at least one processor, provides operations. The operations may include receiving data including one or more puff characteristics, the one or more puff characteristics being determined based on at least one or more puffs on the vaporizer device; and determining an adjustment to the one or more puff characteristics based at least on the data.

[0055] In another aspect, an apparatus is provided. The apparatus may include: means for receiving data including one or more puff characteristics, the one or more puff characteristics determined based at least on at least one or more puffs on a vaporizer device; and means for determining an adjustment to the one or more puff characteristics based at least on the data.

[0056] In another aspect, a system is provided that includes at least one processor and at least one memory. The at least one memory may include program code that, when executed by the at least one processor, provides operations. The operations may include capturing a first image of a user's identification document; capturing a second image of the user; and unlocking a vaporizer device in response to a match between the first image and the second image, wherein unlocking the vaporizer device includes enabling one or more functions of the vaporizer device that are disabled when the vaporizer device is in a locked state.

[0057] In some variations, one or more features disclosed herein, including the following, may optionally be included in any feasible combination: Insertion of a cartridge may be detected at the vaporizer device. In response to the insertion of the cartridge, a user interface may be generated that is configured to display a prompt to a first user to capture a first image and / or a second image.

[0058] In some variations, a user interface may be further generated in response to determining that the cartridge contains a controlled substance. The determination that the cartridge contains a controlled substance may be made by at least reading a characteristic associated with the cartridge. The characteristic may be encoded in a pattern and / or circuit.

[0059] In some variations, a determination may be made as to whether the vaporizer device is associated with another user. The vaporizer device may further be unlocked in response to the vaporizer device not being associated with the other user. In response to the vaporizer device not being associated with the other user, the vaporizer device may be linked to the user by creating an association between at least a device characteristic of the vaporizer device and a user characteristic of the user. Data received from the vaporizer device may be anonymized by being associated with at least the device characteristic of the vaporizer device rather than the user characteristic of the user.

[0060] In some variations, it may be determined whether the user is associated with a threshold number of activated vaporizer devices.The vaporizer device may be unlocked further in response to the user not being associated with the threshold number of activated vaporizer devices.

[0061] In some variations, the first image and the second image may be received from a user device coupled to the vaporizer device. Unlocking the vaporizer device may include sending a private key for unlocking the vaporizer device to the user device.

[0062] In some variations, one or more functions of the vaporizer device may include vaporization of a vaporizable material in a cartridge inserted in the vaporizer device.

[0063] In some variations, unlocking the vaporizer device may also prevent the vaporizer device from entering a locked state when the vaporizer device and / or a user device communicating with the vaporizer device is determined to be within one or more designated areas. The one or more designated areas may be defined by the range of wireless beacons and / or geo-fences.

[0064] In some variations, a determination may be made as to whether the age indicated by the user's identification document exceeds a threshold. The vaporizer device may be unlocked in further response to the age indicated by the user's identification document exceeding the threshold. The threshold may be determined based at least on the location of the vaporizer device and / or a user device communicatively coupled to the vaporizer device.

[0065] In some variations, the matching may be performed at a remote server.Unlocking may be triggered in response to receiving an indication of a match between the first image and the second image from the remote server.

[0066] In another aspect, a method is provided. The method may include capturing a first image of an identification document of a user; capturing a second image of the user; and unlocking a vaporizer device in response to a match between the first image and the second image, wherein unlocking the vaporizer device includes enabling one or more functions of the vaporizer device that are disabled when the vaporizer device is in a locked state.

[0067] In some variations, the method may further include: detecting insertion of a cartridge at the vaporizer device; and, in response to the insertion of the cartridge, generating a user interface configured to display a prompt to the first user to capture the first image and / or the second image. The user interface may be further generated in response to determining that the cartridge contains a controlled substance. The determination that the cartridge contains a controlled substance may be made by at least reading a characteristic associated with the cartridge. The characteristic may be encoded in a pattern and / or circuit.

[0068] In some variations, the method may further include determining whether the vaporizer device is associated with another user; and further unlocking the vaporizer device in response to the vaporizer device not being associated with the other user. In response to the vaporizer device not being associated with the other user, the vaporizer device may be linked to the user by creating an association between at least a device characteristic of the vaporizer device and a user characteristic of the user. Data received from the vaporizer device may be anonymized by being associated with at least the device characteristic of the vaporizer device rather than the user characteristic of the user.

[0069] In some variations, the method may further include determining whether the user is associated with a threshold amount of activated vaporizer devices; and further in response to the user not being associated with the threshold amount of activated vaporizer devices, unlocking the vaporizer device.

[0070] In some variations, the first image and the second image may be received from a user device coupled to the vaporizer device. Unlocking the vaporizer device may include sending a private key for unlocking the vaporizer device to the user device.

[0071] In some variations, one or more functions of the vaporizer device may include vaporization of a vaporizable material in a cartridge inserted in the vaporizer device.

[0072] In some variations, unlocking the vaporizer device also prevents the vaporizer device from entering a locked state when the vaporizer device and / or a user device in communication with the vaporizer device is within one or more designated areas. The one or more designated areas may be defined by the range of wireless beacons and / or geo-fences.

[0073] In some variations, the method may further include: determining whether the age indicated by the user's identification document exceeds a threshold; and further responsive to the age indicated by the user's identification document exceeding the threshold, unlocking the vaporizer device. The threshold may be determined based at least on a location of the vaporizer device and / or a user device communicatively coupled to the vaporizer device.

[0074] In some variations, the matching may be performed at a remote server. Unlocking may be triggered in response to receiving an indication of a match between the first image and the second image from the remote server.

[0075] In another aspect, a computer program product is provided that includes a non-transitory computer-readable medium storing instructions. The instructions may cause operations executable by at least one data processor. The operations may include capturing a first image of a user's identification document; capturing a second image of the user; and unlocking a vaporizer device in response to a match between the first image and the second image, wherein unlocking the vaporizer device includes enabling one or more functions of the vaporizer device that are disabled when the vaporizer device is in a locked state.

[0076] In some variations, a system is provided that includes a vaporizer device, a remote server, and a user device communicatively coupled to the vaporizer device. The user device may include at least one processor and at least one memory. The at least one memory may include program code that, when executed by the at least one processor, provides operations. The operations may include: capturing a first image of a user's identification document; capturing a second image of the user; and, in response to receiving an indication from the remote server that the first image matches the second image, unlocking the vaporizer device, wherein unlocking the vaporizer device includes enabling one or more functions of the vaporizer device that are disabled when the vaporizer device is in a locked state.

[0077] In some variations, a device is provided. The device may include: means for capturing a first image of an identification document of a user; means for capturing a second image of the user; and means for unlocking a vaporizer device in response to a match between the first image and the second image, wherein unlocking the vaporizer device includes enabling one or more functions of the vaporizer device that are disabled when the vaporizer device is in a locked state.

[0078] In another aspect, a system is provided that includes at least one processor and at least one memory. The at least one memory may include program code that, when executed by the at least one processor, provides operations. The operations may include determining whether a vaporizer device is within communication range; and, in response to determining that the vaporizer device is within communication range, triggering one or more outputs at the vaporizer device.

[0079] In some variations, one or more features disclosed herein, including the following, may optionally be included in any feasible combination: A determination that a vaporizer device is within communication range may be made based at least on one or more beacon messages advertised by the vaporizer device.

[0080] In some variations, the one or more outputs may include an audio indicator, a visual indicator, and / or a tactile indicator.

[0081] In some variations, in response to determining that the vaporizer device is out of communication range, a user interface may be generated that displays a last location where the vaporizer device was determined to be within communication range. The user interface may display a map that includes an indication of the last location where the vaporizer device was determined to be within communication range.

[0082] In another aspect, a method is provided. The method may include determining whether a vaporizer device is within a communication range; and triggering one or more outputs at the vaporizer device in response to determining that the vaporizer device is within the communication range.

[0083] In some variations, one or more features disclosed herein, including the following, may optionally be included in any feasible combination: A determination that a vaporizer device is within communication range may be made based at least on one or more beacon messages advertised by the vaporizer device.

[0084] In some variations, the one or more outputs may include an audio indicator, a visual indicator, and / or a tactile indicator.

[0085] In some variations, the method may further include, in response to determining that the vaporizer device is out of communication range, generating a user interface that displays a last location where the vaporizer device was determined to be within communication range. The user interface may display a map that includes an indication of the last location where the vaporizer device was determined to be within communication range.

[0086] In another aspect, a computer program product is provided that includes a non-transitory computer-readable medium storing instructions. The instructions may cause operations executable by at least one data processor. The operations may include determining whether a vaporizer device is within communication range; and in response to determining that the vaporizer device is within communication range, triggering one or more outputs at the vaporizer device.

[0087] In another aspect, a system is provided that includes a vaporizer device and a user device communicatively coupled to the vaporizer device. The user device may include at least one processor and at least one memory. The at least one memory may include program code that, when executed by the at least one processor, provides operations. The operations may include determining whether the vaporizer device is within a communication range of the user device; and, in response to determining that the vaporizer device is within the communication range of the user device, triggering one or more outputs at the vaporizer device.

[0088] In another aspect, an apparatus is provided. The apparatus may include: means for determining whether a vaporizer device is within communication range; and means for responding to determining that the vaporizer device is within communication range by at least triggering one or more outputs at the vaporizer device.

[0089] In another aspect, a device is provided that may include a container configured to receive a vaporizer device, a first coupling configured to secure the vaporizer device within the container to a user device, and a second coupling configured to provide a data connection between the vaporizer device within the container and the user device.

[0090] In some variations, one or more features disclosed herein, including the following, may optionally be included in any feasible combination: A first coupling may secure the vaporizer device within the container to a perimeter, front surface, and / or rear surface of the user device.

[0091] In some variations, the first coupling may comprise a friction fit coupling, a snap fit coupling, a magnetic coupling, and / or an adhesive coupling.

[0092] In some variations, the second connection may provide access to a serial port and / or a parallel port on the user device.

[0093] In some variations, the second coupling may comprise an adapter configured to allow a first type of port on the vaporizer device to couple with a second type of port on the user device.

[0094] In some variations, the second coupling may include a pin connector and / or a Universal Serial Bus (USB) port.

[0095] In some variations, the container may include one or more retaining mechanisms configured to retain the vaporizer device within the container. The one or more retaining mechanisms may include a snap fit, a friction fit, a magnet, and / or an adhesive.

[0096] In another aspect, an apparatus is provided that may include: means for receiving a vaporizer device; means for securing the vaporizer device within the receiving device to a user device; and means for providing a data connection between the vaporizer device within the receiving device and the user device.

[0097] Various aspects of the present subject matter relate to management of operations (e.g., one or more settings or operating parameters of a vaporizer). In some aspects, a cartridge can be coupled to a vaporizer body. The cartridge can include a vaporizable material and a heater, as well as a feature, which can optionally be a cartridge memory. The vaporizer body can include a controller that can exchange data with the feature (e.g., via one-way or two-way communication). The exchange of data can optionally be performed via the same circuit through which power from a power source of the vaporizer body is delivered to the cartridge's heater.

[0098] In another aspect, the evaporator system may include a device in communication with the evaporator. The device may execute software or other instructions that result in an application program that can be used to obtain information from the evaporator, optionally via a wireless communication channel. Additionally, the application program can relay commands to a controller of the evaporator to affect one or more operations of the evaporator.

[0099] Implementations of the present subject matter may include, but are not limited to, methods consistent with the description provided herein and articles comprising tangibly embodied machine-readable media operable to cause one or more machines (e.g., computers, etc.) to cause operations that implement one or more of the above-described features. Similarly, a computer system is also described that may include one or more processors and one or more memories coupled to the one or more processors. The memory, which may include a non-transitory computer-readable storage medium or a machine-readable storage medium, may include: one or more programs that encode, store, etc., causing the one or more processors to perform one or more operations described herein. Computer-implemented methods consistent with one or more implementations of the present subject matter may be implemented by one or more data processors residing in a single computing system or multiple computing systems. Such multiple computing systems may be connected and may exchange data and / or commands or other instructions, etc., via one or more connections, including but not limited to connections via a network (e.g., the Internet, a wireless wide area network, a local area network, a wide area network, a wired network, etc.), via direct connections between one or more computing systems, etc.

[0100] In certain aspects of the present subject matter, challenges associated with the presence of liquid vaporizable materials in or near certain susceptible components of electronic vaporizer devices can be addressed by incorporating one or more of the features described herein or comparable / equivalent methods as would be appreciated by one of ordinary skill in the art. Various aspects of the present subject matter relate to methods and systems for managing airflow in vaporizer devices. In one aspect, a method of manufacturing a vaporizer cartridge is described.

[0101] In some variations, one or more of the following features may optionally be included in any feasible combination. The airflow control feature may include a fluid passage extending between the reservoir chamber and the airflow channel. The diameter of the fluid passage may be sized to allow surface tension of the vaporizable material to prevent the passage of fluid along the fluid passage when the reservoir pressure is approximately the same as a second pressure along the airflow channel. The diameter may be sized to allow surface tension to be broken when the reservoir pressure is less than the second pressure along the airflow channel, thereby allowing a certain amount of air to pass through the airflow control feature and into the reservoir.

[0102] In some embodiments of the current theme, the air flow control feature may include a check valve or a duckbill valve. The air flow control feature may include a coating comprising a ventilation material extending over the opening of the fluid passage. The coating may include a polytetrafluoroethylene (PTFE) material. The air flow control feature may include one or more of a baffle, a valve, and a pump. The air flow control feature may include a ventilation channel extending along at least one side of the core housing comprising the evaporation chamber, and the ventilation channel may extend between the reservoir and the evaporation chamber. The air flow control feature may include a ventilation channel extending through the core housing comprising the evaporation chamber, and the ventilation channel may extend between the reservoir and the evaporation chamber.

[0103] In some embodiments of the current subject matter, the cartridge can further include a pressure sensor configured to sense pressure along the airflow channel. The cartridge can further include a second channel configured to draw air through a portion of the cartridge, and the second channel can be configured to merge with the airflow channel downstream of the evaporation chamber. The cartridge can further include a pressure sensing channel extending between an outlet of the cartridge and the pressure sensor, and the pressure sensing channel can be separate from the airflow channel.

[0104] The cartridge may further include an inlet positioned along a first side of the cartridge and an outlet positioned along a second side of the cartridge. An airflow path may extend between the inlet and the outlet, and the inlet and outlet may be positioned along the first and second sides, respectively, such that when the cartridge is inserted into the evaporator device body in a first position, the inlet and outlet are open, and when the cartridge is inserted into the evaporator device body in a second position, the inlet and outlet are closed. The wicking element may include a flat configuration including at least a pair of opposing sides extending parallel to each other.

[0105] In another interrelated aspect of the present subject matter, the method includes allowing an air flow through an evaporation chamber of an evaporator device, thereby combining the air flow with an aerosol formed in the evaporation chamber. The aerosol can be formed by evaporating the evaporable material drawn from a porous wick extending between the evaporation chamber and a reservoir containing the evaporable material. The method may also include drawing the evaporable material from the reservoir to the evaporation chamber along the porous wick, thereby generating a first pressure in the reservoir that is less than a second pressure in an area outside the reservoir. In addition, the method may include destroying the surface tension of the evaporable material along a ventilation channel extending between the reservoir and the area outside the reservoir, thereby allowing a certain amount of air to enter the reservoir from the ventilation channel. In addition, the method may include increasing the first pressure in the reservoir so that the first pressure is approximately equal to the second pressure.

[0106] In some embodiments of the present subject matter, the method may further include preventing fluid from passing along the ventilation channel due to the first pressure being approximately equal to the second pressure. This prevention may be controlled by fluid tension of the evaporable fluid. The evaporable fluid may include at least one of a evaporable material and air. The airflow control feature may include a ventilation channel extending through a core housing that houses the evaporation chamber. The airflow control feature may include a fluid channel extending between the reservoir chamber and the airflow channel.

[0107] In another interrelated aspect of the present subject matter, an evaporator cartridge for coupling to an evaporator body to form an evaporator device is described. The cartridge may include: a reservoir housing defining a reservoir chamber for containing a vaporizable material; and a mouthpiece coupled to the reservoir housing. The cartridge may also include an air duct assembly, which may include a core housing portion configured to position a wicking element and a heating element in the vaporization chamber to vaporize the vaporized material in the vaporization chamber. The air duct assembly may also include a duct portion including a portion of an airflow path extending through the vaporization chamber and the mouthpiece, thereby allowing the vaporized vaporizable material to be inhaled by a user. Additionally, the cartridge may also include a filter housing portion configured to position a filter near the mouthpiece.

[0108] In some embodiments of the current subject matter, the air tube assembly can be made from a single molded part. The tube portion can be made from metal. The filter housing and core housing can be made from plastic.

[0109] The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the following description. Other features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims. Although certain features of the presently disclosed subject matter have been described for illustrative purposes in relation to electronic vaporizer devices, it should be readily understood that these features are not intended to be limiting. The claims that follow this disclosure are intended to define the scope of the protected subject matter. BRIEF DESCRIPTION OF THE DRAWINGS

[0110] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate certain aspects of the subject matter disclosed herein and, together with the description, help explain some principles associated with the disclosed embodiments. In the drawings:

[0111] Figure 1A An example of an evaporator device consistent with an embodiment of the current subject matter is shown;

[0112] Figure 1B 、 Figure 1C 、 Figure 1D and Figure 1E Example variations of vaporizer devices and cartridge assemblies consistent with embodiments of the current subject matter are shown;

[0113] Figure 2 A proportional-integral-derivative controller for an evaporator device is shown that can be adapted to detect a cartridge using a cartridge identification circuit consistent with embodiments of the current subject matter;

[0114] Figure 3 shows communications between a vaporizer device, a user device, and a server consistent with embodiments of the current subject matter;

[0115] Figure 4 illustrates a functional block diagram of a user device for implementing features consistent with the described subject matter, according to some example embodiments;

[0116] Figure 5 shows an example of a user interface for an application that may be used with a vaporizer device consistent with embodiments of the current subject matter;

[0117] Figure 6 shows an example of a user interface for an application that may be used with a vaporizer device consistent with embodiments of the current subject matter;

[0118] Figure 7 shows an example of a user interface for an application that may be used with a vaporizer device consistent with embodiments of the current subject matter;

[0119] Figure 8 shows an example of a user interface for an application that may be used with a vaporizer device consistent with embodiments of the current subject matter;

[0120] 9A to 9F An example of a user interface for use with a vaporizer or vaporizer-related application consistent with embodiments of the present subject matter is shown;

[0121] Figure 10 shows an example of a user interface for an application for use with a vaporizer, the application including a menu of commands consistent with embodiments of the present subject matter;

[0122] Figure 11 shows an example of a user interface that may be used as part of an application program interface consistent with implementations of the present subject matter;

[0123] Figure 12 An example of a user interface displaying a user information dashboard consistent with an embodiment of the present subject matter is shown;

[0124] Figure 13 shows an example of a user interface for controlling the operation of an associated vaporizer consistent with embodiments of the current subject matter;

[0125] Figure 14 shows an example of a user interface consistent with an implementation of the current subject matter;

[0126] Figure 15 An example of a user interface for customizing an application and / or vaporizer consistent with embodiments of the present subject matter is shown;

[0127] Figure 16 shows an example of a user interface consistent with an implementation of the current subject matter;

[0128] Figure 17 shows an example of a user interface that may be presented by an application consistent with implementations of the present subject matter;

[0129] Figure 18 shows an example of a user interface that may be used to guide a user through the operation of a vaporizer and / or associated application consistent with embodiments of the present subject matter;

[0130] Figure 19 An example of a user interface that may be used to guide a user in controlling a vaporizer using an application consistent with embodiments of the present subject matter is shown;

[0131] Figure 20 shows an example user interface for programming / recording a usage profile consistent with embodiments of the present subject matter;

[0132] Figure 21 An example of a user interface for using an application consistent with an embodiment of the present subject matter is shown;

[0133] Figure 22 shows an example of a user interface that may be used consistent with implementations of the current subject matter;

[0134] Figure 23 An example of a user interface for using an application consistent with an embodiment of the present subject matter is shown;

[0135] Figure 24 An example of a user interface for using an application consistent with an embodiment of the present subject matter is shown;

[0136] Figure 25 An example of a user interface for using an application consistent with an embodiment of the present subject matter is shown;

[0137] Figure 26 An example of a user interface for using an application consistent with an embodiment of the present subject matter is shown;

[0138] Figure 27 An example of a user interface for using an application consistent with an embodiment of the present subject matter is shown;

[0139] Figure 28 An example of a user interface for using an application consistent with an embodiment of the present subject matter is shown;

[0140] Figure 29 An example of a user interface for using an application consistent with an embodiment of the present subject matter is shown;

[0141] Figure 30 An example of a user interface for using an application consistent with an embodiment of the present subject matter is shown;

[0142] Figure 31 An example of a user interface for using an application consistent with an embodiment of the present subject matter is shown;

[0143] Figure 32 shows an example of a user interface consistent with an implementation of the current subject matter;

[0144] Figure 33 shows an example of a user interface consistent with an implementation of the current subject matter;

[0145] Figure 34 shows an example of a user interface consistent with an implementation of the current subject matter;

[0146] Figure 35 shows an example of a user interface consistent with an implementation of the current subject matter;

[0147] Figure 36 shows an example of a user interface consistent with an implementation of the current subject matter;

[0148] Figure 37 shows an example of a user interface consistent with an implementation of the current subject matter;

[0149] Figure 38 shows an example of a user interface consistent with an implementation of the current subject matter;

[0150] Figure 39 shows an example of a user interface consistent with an implementation of the current subject matter;

[0151] Figure 40 shows an example of a user interface consistent with an implementation of the current subject matter;

[0152] Figure 41 shows an example of a user interface consistent with an implementation of the current subject matter;

[0153] Figure 42 shows an example of a user interface consistent with an implementation of the current subject matter;

[0154] Figure 43 shows an example of a user interface consistent with an implementation of the current subject matter;

[0155] Figure 44 shows an example of a user interface consistent with an implementation of the current subject matter;

[0156] Figure 45 shows an example of a user interface consistent with an implementation of the current subject matter;

[0157] Figure 46 shows an example of a user interface consistent with an implementation of the current subject matter;

[0158] Figure 47 shows an example of a user interface consistent with an implementation of the current subject matter;

[0159] Figure 48 shows an example of a user interface consistent with an implementation of the current subject matter;

[0160] Figure 49 shows an example of a user interface consistent with an implementation of the current subject matter;

[0161] Figure 50 shows an example of a user interface consistent with an implementation of the current subject matter;

[0162] Figure 51 shows an example of a user interface consistent with an implementation of the current subject matter;

[0163] Figure 52 shows an example of a user interface consistent with an implementation of the current subject matter;

[0164] Figure 53 shows an example of a user interface consistent with an implementation of the current subject matter;

[0165] Figure 54 shows an example of a user interface consistent with an implementation of the current subject matter;

[0166] Figure 55 shows an example of a user interface consistent with an implementation of the current subject matter;

[0167] Figure 56 shows an example of a user interface consistent with an implementation of the current subject matter;

[0168] Figure 57 shows an example of a user interface consistent with an implementation of the current subject matter;

[0169] Figure 58 shows an example of a user interface consistent with an implementation of the current subject matter;

[0170] Figure 59 shows an example of a user interface consistent with an implementation of the current subject matter;

[0171] Figure 60 shows an example of a user interface consistent with an implementation of the current subject matter;

[0172] Figure 61 shows an example of a user interface consistent with an implementation of the current subject matter;

[0173] Figure 62 shows an example of a user interface consistent with an implementation of the current subject matter;

[0174] Figure 63 shows an example of a user interface consistent with an implementation of the current subject matter;

[0175] Figure 64 shows an example of a user interface consistent with an implementation of the current subject matter;

[0176] Figure 65 shows an example of a user interface consistent with an implementation of the current subject matter;

[0177] Figure 66 shows an example of a user interface consistent with an implementation of the current subject matter;

[0178] Figure 67 shows an example of a user interface consistent with an implementation of the current subject matter;

[0179] Figure 68 shows an example of a user interface consistent with an implementation of the current subject matter;

[0180] Figure 69 shows an example of a user interface consistent with an implementation of the current subject matter;

[0181] Figure 70 shows an example of a user interface consistent with an implementation of the current subject matter;

[0182] Figure 71 shows an example of a user interface consistent with an implementation of the current subject matter;

[0183] Figure 72 shows an example of a user interface consistent with an implementation of the current subject matter;

[0184] Figure 73 shows an example of a user interface consistent with an implementation of the current subject matter;

[0185] Figure 74 shows an example of a user interface consistent with an implementation of the current subject matter;

[0186] Figure 75 shows an example of a user interface consistent with an implementation of the current subject matter;

[0187] Figure 76 shows an example of a user interface consistent with an implementation of the current subject matter;

[0188] Figure 77 shows an example of a user interface consistent with an implementation of the current subject matter;

[0189] Figure 78 shows an example of a user interface consistent with an implementation of the current subject matter;

[0190] Figure 79 shows an example of a user interface consistent with an implementation of the current subject matter;

[0191] Figure 80 shows an example of a user interface consistent with an implementation of the current subject matter;

[0192] Figure 81 An exemplary method consistent with implementations of the current subject matter is shown;

[0193] Figure 82A and Figure 82B An exemplary method consistent with embodiments of the present subject matter is shown;

[0194] Figure 83 An exemplary method consistent with embodiments of the present subject matter is shown;

[0195] Figure 84 A block diagram of an activation system for an evaporator device is shown;

[0196] Figure 85 A process flow diagram illustrating aspects of a method having one or more features consistent with embodiments of the present subject matter is shown;

[0197] Figures 86A to 86C An example of a docking station consistent with an embodiment of the current subject matter is shown;

[0198] Figures 87A to 87C Another example of a docking station consistent with an embodiment of the current subject matter is shown;

[0199] Figures 88A to 88D An example of an activation system consistent with an embodiment of the current subject matter is shown;

[0200] Figures 89A to 89D An example of an activation system consistent with an embodiment of the current subject matter is shown;

[0201] Figures 90A to 90DAn example of an activation system consistent with an embodiment of the current subject matter is shown;

[0202] Figures 91A to 91D An example of an activation system consistent with an embodiment of the current subject matter is shown;

[0203] Figures 92A to 92D An example of an activation system consistent with an embodiment of the current subject matter is shown;

[0204] Figures 93A to 93D An example of an activation system consistent with an embodiment of the current subject matter is shown;

[0205] Figures 94A to 94D An example of an activation system consistent with an embodiment of the current subject matter is shown;

[0206] Figure 95 An example of a vaporizer device having a 5-pin connector consistent with embodiments of the current subject matter is shown;

[0207] Figure 96 depicts a flow chart illustrating an initial setup process for an evaporator device consistent with embodiments of the current subject matter;

[0208] Figure 97 depicts a flow chart illustrating a process for pairing a vaporizer device with a user device consistent with embodiments of the present subject matter;

[0209] Figure 98 depicts a flow chart illustrating a process for locating a retailer consistent with embodiments of the present subject matter;

[0210] Figure 99 depicts a flow chart illustrating an in-store activation process consistent with embodiments of the present subject matter;

[0211] Figure 100 depicts a flow chart illustrating a process for age-verifying a user consistent with implementations of the present subject matter;

[0212] Figure 101 depicts an example of a user interface consistent with implementations of the present subject matter;

[0213] Figure 102 depicts a table showing examples of data fields included in a pod feature consistent with implementations of the current subject matter;

[0214] Figure 103A depicts an example of a user interface consistent with implementations of the present subject matter;

[0215] Figure 103B depicts an example of a user interface consistent with implementations of the present subject matter;

[0216] Figure 103C depicts an example of a user interface consistent with implementations of the present subject matter;

[0217] Figure 103D depicts an example of a user interface consistent with implementations of the present subject matter;

[0218] Figure 103E depicts an example of a user interface consistent with implementations of the present subject matter;

[0219] Figure 103F depicts an example of a user interface consistent with implementations of the current subject matter; and

[0220] Figure 103G Depicted are examples of user interfaces consistent with implementations of the current subject matter.

[0221] Where practical, similar reference numerals indicate similar structures, features, or elements. DETAILED DESCRIPTION

[0222] Embodiments of the present subject matter include methods, apparatus, articles of manufacture, and systems relating to the vaporization of one or more materials for inhalation by a user. Example embodiments include vaporizer devices and systems including vaporizer devices. In the following description and claims, the term "vaporizer" is used generically to refer to any device, both a standalone device and a device that includes two or more separable parts (e.g., a vaporizer body including a battery and other hardware and a cartridge including a vaporizable material). As used herein, a "vaporizer system" may include one or more components, such as a device that communicates with the vaporizer (e.g., wirelessly or via a wired connection) and, optionally, the vaporizer itself. A vaporizer or one or more components of a vaporizer system consistent with embodiments of the present subject matter may be configured for user control and operation.

[0223] A vaporizer device, which may also be referred to as a vaporizer, an electronic vaporizer device, or an e-vaporizer device, can be used to deliver an aerosol (or "vapor") containing one or more active ingredients by inhalation of the aerosol by a user of the vaporizing device. For example, electronic nicotine delivery systems (ENDS) include a class of battery-powered vaporizer devices that can be used to simulate the experience of smoking a cigarette, but without burning tobacco or other substances. Typically, such vaporizers are handheld devices that heat (by convection, conduction, radiation, or some combination thereof) a vaporizable material to provide an inhalable dose of the material. The vaporizable material used with a vaporizer can be provided in a cartridge (e.g., a portion of a vaporizer that contains the vaporizable material in a reservoir) or other container that can be refilled when empty, or can be disposable in favor of a new cartridge containing other vaporizable materials of the same or different types. The vaporizer can be a vaporizer that uses a cartridge, a vaporizer without a cartridge, or a multi-purpose vaporizer that can be used with or without a cartridge. For example, a multi-purpose vaporizer may include a heating chamber (e.g., an oven) configured to receive a vaporizable material directly in the heating chamber and also receive a cartridge having a reservoir or the like for holding the vaporizable material. In various embodiments, the vaporizer may be configured for use with a liquid vaporizable material (e.g., a carrier solution in which the active and / or inactive ingredients are suspended or held in solution, or a liquid form of the vaporizable material itself) or a solid vaporizable material. The solid vaporizable material may include plant material that discharges a portion of the plant material as vaporizable material (e.g., such that after the vaporizable material is discharged to a user for inhalation, a portion of the plant material remains as waste) or alternatively may be the vaporizable material itself in solid form such that all of the solid material can ultimately be vaporized for inhalation. The liquid vaporizable material can also be completely vaporized, or may include a portion of the liquid material that remains after all of the material suitable for inhalation has been consumed.

[0224] Consistent with some embodiments of the present subject matter, a vaporizer and / or vaporizer system can be configured to identify the vaporizable material to be vaporized and adjust the operation of the vaporizer accordingly. For example, the vaporizer can be adapted to receive a cartridge or other pre-filled container holding a vaporizable material (e.g., a solution of vaporizable material, nicotine, and / or another active ingredient) and identify and / or determine information about the vaporizable material and / or the cartridge or other pre-filled container, such as one or more of the following: the type of vaporizable material, the concentration of the vaporizable material in a solution or other non-pure form of the vaporizable material contained in the cartridge's reservoir or other container, the amount of vaporizable material in the cartridge's reservoir or other container (e.g., mass and volume, etc.), the configuration of the cartridge (e.g., which specific components or types of components are present in the cartridge, such as heater power or configuration, one or more electrical properties, etc.), the batch number of the cartridge, the date the cartridge was manufactured, an expiration date after which the cartridge must not be used, the manufacturing date or fill date of the cartridge, etc.

[0225] A vaporizer consistent with embodiments of the current subject matter can be configured to connect (e.g., wirelessly or via a wired connection) to a communication device (or alternatively, a device) that communicates with the vaporizer. Such a device can be a component of a vaporizer system as described above and can include first communication hardware that can establish a wireless communication channel with second communication hardware of the vaporizer. For example, a device used as part of a vaporizer system can include a general-purpose computing device (e.g., a smartphone, tablet, personal computer, or some other portable device such as a smartwatch, etc.) that executes software to generate a user interface for enabling a user of the device to interact with the vaporizer. In other embodiments of the current subject matter, such a device used as part of a vaporizer system can be dedicated hardware, such as a remote control or other wireless or wired device with one or more physical or soft interface controls (e.g., configurable on a screen or other display device and selectable via user interaction with a touchscreen or some other input device (e.g., a mouse, pointer, trackball, cursor buttons, etc.)).

[0226] Devices as part of the above-described vaporizer systems may be used for any of one or more functions, such as controlling dosage (e.g., dosage monitoring, dosage setting, dosage limiting, user tracking, etc.), obtaining location information (e.g., the location of other users, the location of the retailer / business location, the vaporization location, the relative or absolute location of the vaporizer itself, etc.), personalizing the vaporizer (e.g., naming the vaporizer, locking / password protecting the vaporizer, adjusting one or more parental controls, associating the vaporizer with a user group, registering the vaporizer with the manufacturer or warranty maintenance organization, etc.), engaging in social activities with other users (e.g., gaming, social media communication, interacting with one or more groups, etc.), etc.

[0227] In some embodiments of the current subject matter, the vaporizer may include functionality for communicating with a cartridge containing vaporizable material. The vaporizer may also communicate with a device that is part of the vaporizer system, although this is not required. Whether under the control of or otherwise communicating with a device that is part of the vaporizer system, or as a standalone unit separate from the vaporizer system, the vaporizer may be configured such that its operation, among other things, can be modified and controlled based on one or more parameters received from the cartridge or accessed from a database or other information source based on the cartridge's identification.

[0228] For example, a vaporizer consistent with embodiments of the present subject matter can be configured to identify a cartridge and record (and in some cases transmit) or otherwise obtain information about the cartridge. In other words, a computing element, such as a controller, associated with the vaporizer body can obtain information about the cartridge via some form of data exchange. Various methods for vaporizer-to-cartridge identification are within the scope of the present subject matter, including those described in more detail below. Any of the methods described herein can be performed with or without the addition of wireless communication / connectivity, also described herein, but as will be described in more detail below, such wireless connectivity as described herein can be advantageously applied.

[0229] Implementations of the current subject matter also include methods of using vaporizers and / or vaporizer systems to perform functions such as determining and / or controlling the dosage, amount, etc., of one or more chemical species of vaporizable material or the vaporizable material itself.

[0230] Embodiments of the present subject matter include devices related to the vaporization of one or more materials for inhalation by a user. In the following description, the term "vaporizer" is used generically to refer to a vaporizer device. Examples of vaporizers consistent with embodiments of the present subject matter include electronic vaporizers, e-vaporizer devices, electronic nicotine delivery systems (ENDS), and the like. Such vaporizers are typically portable, handheld devices that heat a vaporizable material to provide an inhalable dose of the material. The vaporizable material used with the vaporizer can optionally be provided in a cartridge (e.g., a portion of a vaporizer that holds the vaporizable material in a reservoir) or other container that can be refilled when empty, or disposable in favor of a new cartridge containing other vaporizable materials of the same or different types. The vaporizer can be a cartridge-based vaporizer, a cartridge-free vaporizer, or a multi-purpose vaporizer that can be used with or without a cartridge. For example, a multi-purpose vaporizer may include a heating chamber (e.g., an oven) configured to receive a vaporizable material directly in the heating chamber and also receive a cartridge or other replaceable device having a reservoir, volume, etc. for at least partially containing a usable amount of the vaporizable material. In various embodiments, the vaporizer may be configured for use with a liquid vaporizable material (e.g., a carrier solution in which the active and / or inactive ingredients are suspended or held in solution, or the vaporizable material itself in pure liquid form) or a solid vaporizable material. The solid vaporizable material may include plant material that releases a portion of the plant material as the vaporizable material (e.g., such that after the vaporizable material is released to the user for inhalation, a portion of the plant material remains as waste), or alternatively, may be the vaporizable material itself in solid form (e.g., a "wax") such that all of the solid material can ultimately be vaporized for inhalation. The liquid vaporizable material may also be completely vaporized, or may include a portion of the liquid material remaining after all of the material suitable for inhalation has been consumed.

[0231] Reference Figure 1A As shown in a block diagram of a vaporizer device 100, the vaporizer device 100 generally includes a power source 22 (e.g., a battery, which may be a rechargeable battery) and a controller 24 (e.g., a processor, circuitry, etc., capable of executing logic) for controlling the delivery of heat to an atomizer 26 to convert a vaporizable material from a condensed form (e.g., a solid, a liquid, a solution, a suspension, a portion of at least partially unprocessed plant material, etc.) into a vapor phase. The controller 24 may be part of one or more printed circuit boards (PCBs) consistent with certain embodiments of the present subject matter. After converting the vaporizable material into the vapor phase, depending on the type of vaporizer, the physical and chemical properties of the vaporizable material, and / or other factors, at least some of the vapor-phase vaporizable material may condense to form particulate matter in at least partial local equilibrium with the vapor phase as part of an aerosol. This aerosol may form some or all of the inhalable dose provided by the vaporizer device 100 for a given puff or puffs on the vaporizer. It will be appreciated that the interaction between the gas phase and the condensed phase in the aerosol produced by the vaporizer can be complex and dynamic, as factors such as ambient temperature, relative humidity, chemical composition, flow conditions in the airflow path (both inside the vaporizer and in the airways of a human or other animal), mixing of the vaporized or aerosol-phase vaporizable material with other airflows, etc. can affect one or more physical parameters of the aerosol. In some vaporizers, particularly those used to deliver more volatile vaporizable materials, the respirable dose may be primarily present in the gas phase (i.e., the formation of condensed phase particles may be very limited).

[0232] Vaporizers for use with liquid vaporizable materials (e.g., pure liquids, suspensions, solutions, mixtures, etc.) typically include an atomizer 26 in which a wicking element (also referred to herein as a wick (not shown)) is formed. Figure 1A ), which may include any material capable of inducing fluid movement by capillary pressure) delivers a quantity of liquid vaporizable material to the atomizer including a heating element (also not shown in FIG. Figure 1A The wicking element is typically configured to draw liquid evaporable material from a reservoir configured to hold (and which can hold, in use) the liquid evaporable material so that the liquid evaporable material can be evaporated by heat delivered from the heating element. The wicking element can also optionally allow air to enter the reservoir to replace the volume of liquid removed. In other words, capillary action draws the liquid evaporable material into the wick for evaporation by the heating element (as described below), and in some embodiments of the current subject matter, air can return to the reservoir through the wick to at least partially equalize the pressure in the reservoir. Other methods of allowing air to return to the reservoir to equalize pressure are also within the scope of the current subject matter.

[0233] The heating element can be or include one or more of a conductive heater, a radiant heater, and a convection heater. One type of heating element is a resistive heating element, which can be composed of or at least include a material (e.g., a metal or alloy, such as a nickel-chromium alloy or a non-metallic resistor) that is configured to dissipate electrical energy in the form of heat when an electric current passes through one or more resistive segments of the heating element. In some embodiments of the current subject matter, the atomizer can include a heating element that includes a resistive coil or other heating element that is wrapped around a wicking element, positioned in the wicking element, integrated into the overall shape of the wicking element, pressed into thermal contact with the wicking element, or otherwise arranged to transfer heat to the wicking element so that the liquid vaporizable material drawn from the reservoir by the wicking element evaporates for subsequent inhalation by the user in the form of a gas phase and / or a condensed phase (e.g., aerosol particles or droplets). As discussed further below, other wicking element, heating element, and / or atomizer assembly configurations are also possible.

[0234] Certain vaporizers may also or alternatively be configured to produce an inhalable dose of vaporizable material in a vapor phase and / or aerosol phase via heating of a non-liquid vaporizable material, such as a solid vaporizable material (e.g., wax, etc.) or a plant material containing a vaporizable material (e.g., tobacco leaves and / or portions of tobacco leaves). In such vaporizers, the resistive heating element may be part of a wall of an oven or other heated chamber in which the non-liquid vaporizable material is placed, or otherwise incorporated into or in thermal contact with the wall. Alternatively, one or more resistive heating elements may be used to heat air passing through or over the non-liquid vaporizable material to cause convective heating of the non-liquid vaporizable material. In still other examples, one or more resistive heating elements may be positioned in close contact with the plant material such that direct conductive heating of the plant material occurs from within the mass of the plant material (e.g., as opposed to merely by conduction inward from the walls of the oven).

[0235] The heating element can be activated (e.g., a controller, which is optionally part of the vaporizer body as described below, can cause current to flow from a power source through a circuit including the resistive heating element, which is optionally part of the vaporizer cartridge as described below) in association with a user drawing (e.g., puffing, inhaling, etc.) on the vaporizer's mouthpiece 30, causing air to flow from the air inlet along an airflow path through the atomizer (e.g., wicking element and heating element), optionally through one or more condensation regions or chambers, to an air outlet in the mouthpiece. The incoming air passing along the airflow path passes through the atomizer, where it entrains vaporizable material in the vapor phase into the air. As described above, the entrained vaporizable material in the vapor phase can condense as it passes through the remainder of the airflow path, allowing a respirable dose of vaporizable material in the form of an aerosol to be delivered from the air outlet (e.g., in the mouthpiece 30 for inhalation by the user).

[0236] Activation of the heating element may be responsive to detecting user interaction with one or more input devices 33 (e.g., a button or other tactile control device of the vaporizer device 100), receiving a signal from a computing device in communication with the vaporizer, and / or via other methods for determining that a puff is occurring or about to occur based on one or more signals generated by one or more sensors 32 (e.g., one or more pressure sensors configured to detect pressure relative to ambient pressure along the airflow path (or, alternatively, to measure changes in absolute pressure), one or more motion sensors of the vaporizer, one or more flow sensors of the vaporizer, a capacitive lip sensor of the vaporizer).

[0237] As noted, a vaporizer consistent with embodiments of the current subject matter can be configured to connect (e.g., wirelessly or via a wired connection) to a computing device (or, optionally, two or more devices) that communicates with the vaporizer. To this end, the controller 24 can include communication hardware 34. The controller 24 can also include memory 36. The computing device can be a component of a vaporizer system that also includes the vaporizer device 100 and can include its own communication hardware that can establish a wireless communication channel with the communication hardware 34 of the vaporizer device 100. For example, a computing device used as part of a vaporizer system can include a general-purpose computing device (e.g., a smartphone, tablet, personal computer, some other portable device such as a smartwatch, etc.) that executes software to generate a user interface for enabling a user of the device to interact with the vaporizer. In other embodiments of the current subject matter, such a device used as part of a vaporizer system can be dedicated hardware, such as a remote control or other wireless or wired device with one or more physical or soft interface controls (e.g., configurable on a screen or other display device and selectable via user interaction with a touchscreen or some other input device such as a mouse, pointer, trackball, cursor buttons, etc.). The vaporizer may also include one or more output 38 features or devices for providing information to a user.

[0238] The computing device as part of the above-described vaporizer system can be used for any of one or more functions, such as controlling dosage (e.g., dosage monitoring, dosage setting, dosage limiting, user tracking, etc.), controlling sessions (e.g., session monitoring, session setting, session limiting, user tracking, etc.), controlling nicotine delivery (e.g., switching between nicotine and non-nicotine vaporizable materials, adjusting the amount of nicotine delivered, etc.), obtaining location information (e.g., the location of other users, the location of the retailer / business location, the vaporization location, the relative or absolute location of the vaporizer itself, etc.), personalizing the vaporizer (e.g., naming the vaporizer, locking / password protecting the vaporizer, adjusting one or more parental controls, associating the vaporizer with a user group, registering the vaporizer with the manufacturer or warranty maintenance organization, etc.), engaging in social activities with other users (e.g., gaming, social media communication, interacting with one or more groups, etc.), etc. The terms "sessioning," "session," "vaporizer session," or "vapor session" are used generically to refer to a period dedicated to the use of a vaporizer. The period may include a time period, an amount of dosage, an amount of vaporizable material, and / or the like.

[0239] In instances where a computing device provides a signal related to activation of a resistive heating element, or in other instances where a computing device is coupled to a vaporizer to implement various control or other functions, the computing device executes one or more sets of computer instructions to provide a user interface and underlying data processing. In one example, detection by the computing device of user interaction with one or more user interface elements can cause the computing device to signal the vaporizer device 100 to activate the heating element or to reach full operating temperature to produce an inhalable dose of vapor / aerosol. Other functions of the vaporizer can be controlled by user interaction with a user interface on a computing device in communication with the vaporizer.

[0240] The temperature of the resistive heating element of the vaporizer can depend on many factors, including the amount of electrical power delivered to the resistive heating element and / or the duty cycle of the delivered electrical power, conductive heat transfer to other parts of the electronic vaporizer and / or to the environment, latent heat loss due to evaporation of the vaporizable material from the wicking element and / or the atomizer as a whole, and convective heat loss due to airflow (e.g., air passing through the heating element or the atomizer as a whole when a user inhales on the electronic vaporizer). As described above, in order to reliably activate the heating element or heat the heating element to a desired temperature, in some embodiments of the current subject matter, the vaporizer can utilize a signal from a pressure sensor to determine when a user inhales. The pressure sensor can be positioned in the airflow path and / or can be connected (e.g., via a channel or other pathway) to the airflow path, which connects an inlet through which air enters the device and an outlet through which the user inhales the generated vapor and / or aerosol, such that the pressure sensor experiences a pressure change as air passes from the air inlet through the vaporizer device to the air outlet. In some embodiments of the current subject matter, the heating element can be activated in association with a user's puff, such as by automatically detecting a puff via a pressure sensor detecting a pressure change in the airflow path.

[0241] Typically, the pressure sensor (and any other sensors 32) can be positioned on the controller 24 (e.g., a printed circuit board assembly or other type of circuit board) or coupled to the controller 24 (e.g., physically or electrically or electronically connected via a wireless connection). To accurately measure and maintain the durability of the evaporator, it can be beneficial to provide a resilient seal 42 to separate the airflow path from the rest of the evaporator. The seal 42, which can be a gasket, can be configured to at least partially surround the pressure sensor so that the connection of the pressure sensor to the internal circuitry of the evaporator is separated from the portion of the pressure sensor exposed to the airflow path. In the example of a cartridge-based evaporator, the seal 42 can also separate portions of one or more electrical connections between the evaporator body 50 and the evaporator cartridge 52. The evaporator cartridge 52 can also be referred to as a compartment or compartment 52. This arrangement of the seal 42 in the evaporator device 100 can help mitigate potentially damaging effects on evaporator components due to interactions with environmental factors, such as water in vapor or liquid phase, other fluids such as vaporizable materials, and / or reduce the escape of air from the designed airflow path in the evaporator. Unwanted air, liquid, or other fluid passing through and / or coming into contact with the evaporator's electrical circuitry can cause various adverse effects, such as altering pressure readings and / or causing the accumulation of undesirable substances, such as moisture, vaporizable substances, and the like, in certain parts of the evaporator, where they can result in poor pressure signals, degradation of the pressure sensor or other components, and / or shortened evaporator life. Leaks in the seal 42 can also cause a user to inhale air that has already passed through a portion of the evaporator assembly that contains or is composed of materials that may be undesirable for inhalation.

[0242] A common type of vaporizer that has recently gained popularity includes a vaporizer body 50 that includes a controller 24, a power source 22 (e.g., a battery), one or more sensors 32, charging contacts, a seal 42, and a cartridge receptacle 54 configured to receive a vaporizer cartridge 52 for coupling to the vaporizer body via one or more of a variety of attachment structures. In some examples, the vaporizer cartridge 52 includes a reservoir 56 for holding liquid vaporizable material and a mouthpiece 30 for delivering an inhalable dose to a user. The vaporizer cartridge may include an atomizer 26 having a wicking element and a heating element, or alternatively, one or both of the wicking element and the heating element may be part of the vaporizer body. In embodiments where any portion of the atomizer 26 (e.g., the heating element and / or the wicking element) is part of the vaporizer body, the vaporizer may be configured to supply liquid vaporizer material from a reservoir in the vaporizer cartridge to an atomizer portion included in the vaporizer body.

[0243] Cartridge-based configurations for vaporizers that produce an inhalable dose of a non-liquid vaporizable material by heating the non-liquid vaporizable material are also within the scope of the present subject matter. For example, a vaporizer cartridge can include a mass of plant material that has been processed and formed to be in direct contact with portions of one or more resistive heating elements, and such a vaporizer cartridge can be configured to mechanically and electrically couple to a vaporizer body that includes a processor, a power source, and electrical contacts for connecting to corresponding cartridge contacts to complete an electrical circuit with the one or more resistive heating elements.

[0244] In an evaporator in which the power source 22 is part of the evaporator body 50 and the heating element is disposed in an evaporator cartridge 52 configured to be coupled to the evaporator body 50, the evaporator device 100 may include electrical connection features (e.g., means for completing an electrical circuit) to complete an electrical circuit including the controller 24 (e.g., a printed circuit board, a microcontroller, etc.), the power source, and the heating element. These features may include at least two contacts (referred to herein as cartridge contacts 60) on a bottom surface of the evaporator cartridge 52 and at least two contacts (referred to herein as container contacts 62) disposed near the bottom of a cartridge container of the evaporator device 100 such that the cartridge contacts 60 and the container contacts 62 make electrical connection when the evaporator cartridge 52 is inserted into and coupled to the cartridge container 54. The circuit completed by these electrical connections can allow current to be delivered to the resistive heating element and can also be used for additional functions, such as measuring the resistance of the resistive heating element for determining and / or controlling the temperature of the resistive heating element based on the thermal coefficient of the resistivity of the resistive heating element, identifying the cartridge based on one or more electrical characteristics of the resistive heating element or other circuits of the vaporizer cartridge, and the like.

[0245] In some examples of the present subject matter, the at least two cartridge contacts and the at least two container contacts can be configured to be electrically connected in any one of at least two orientations. In other words, by inserting the evaporator cartridge 52 into the cartridge container 54 in a first rotational orientation (about the axis along which the end of the evaporator cartridge 52 with the cartridge is inserted into the cartridge container 54 of the evaporator body 50), such that a first cartridge contact of the at least two cartridge contacts 60 is electrically connected to a first container contact of the at least two container contacts 62, and a second cartridge contact of the at least two cartridge contacts 60 is electrically connected to a second container contact of the at least two container contacts 62, one or more circuits required for evaporator operation can be completed. Furthermore, by inserting the evaporator cartridge 52 into the cartridge container 54 in a second rotational orientation, such that a first cartridge contact of the at least two cartridge contacts 60 is electrically connected to a second container contact of the at least two container contacts 62, and a second cartridge contact of the at least two cartridge contacts 60 is electrically connected to a first container contact of the at least two container contacts 62, one or more circuits required for evaporator operation can be completed. This feature of the evaporator cartridge 52 being reversibly insertable into the cartridge receptacle 54 of the evaporator body 50 is described further below.

[0246] In one example of an attachment structure for coupling the evaporator cartridge 52 to the evaporator body, the evaporator body 50 includes detents (e.g., dimples, protrusions, etc.) that project inwardly from the inner surface of the cartridge receptacle 54. One or more outer surfaces of the evaporator cartridge 52 may include corresponding recesses ( Figure 1A 54 ), the notch can fit and / or otherwise snap onto such a detent when one end of the evaporator cartridge 52 is inserted into the cartridge receptacle 54 on the evaporator body 50. When the evaporator cartridge 52 and the evaporator body 50 are coupled (e.g., by inserting the end of the evaporator cartridge 52 into the cartridge receptacle 54 of the evaporator body 50), the detent that enters the evaporator body 50 can fit into the notch of the evaporator cartridge 52 and / or otherwise be retained within the recess of the evaporator cartridge 52 to hold the evaporator cartridge 52 in place during assembly. Such a detent-recess assembly can provide sufficient support to hold the evaporator cartridge 52 in place, thereby ensuring good contact between the at least two cartridge contacts 60 and the at least two receptacle contacts 62, while allowing the evaporator cartridge 52 to be released from the evaporator body 50 when a user pulls on the evaporator cartridge 52 with reasonable force to disengage the evaporator cartridge 52 from the cartridge receptacle 54.

[0247] In addition to the above discussion regarding the reversible electrical connection between the evaporator cartridge and the evaporator body, enabling at least two rotational orientations of the evaporator cartridge within the cartridge container, in some evaporators, the shape of the evaporator cartridge, or at least the shape of the end of the evaporator cartridge configured for insertion into the cartridge container, can exhibit at least second-order rotational symmetry. In other words, the evaporator cartridge, or at least the insertable end of the evaporator cartridge, can be symmetrical when rotated 180° about an axis along which the evaporator cartridge is inserted into the cartridge container. In such a configuration, the evaporator's circuitry can support the same operation regardless of the symmetrical orientation of the evaporator cartridge.

[0248] In some examples, the evaporator cartridge, or at least the end of the evaporator cartridge that is configured to be inserted into the cartridge container, may have a non-circular cross-section transverse to the axis along which the evaporator cartridge is inserted into the cartridge container. For example, the non-circular cross-section may be approximately rectangular, approximately elliptical (e.g., having an approximately oval shape), non-rectangular but having two sets of parallel or approximately parallel opposite sides (e.g., having the shape of a parallelogram), or other shapes having at least second-order rotational symmetry. In the context, it is obvious that approximately having a shape means a basic similarity to the shape, but the sides of the shape in question do not have to be completely linear, nor do the vertices have to be completely sharp. In any description of a non-circular cross-section referred to herein, rounding of both or one of the edges or vertices of the cross-sectional shape is contemplated.

[0249] The at least two cartridge contacts and the at least two container contacts can take various forms. For example, one or both sets of contacts may include conductive pins, tabs, posts, receiving holes for the pins or posts, and the like. Some types of contacts may include springs or other urging members to create better physical and electrical contact between the contacts on the evaporator cartridge and the contacts on the evaporator body. The electrical contacts may optionally be gold-plated and / or may be made of other materials.

[0250] Figures 1A to 1E Example features that may be included in an evaporator consistent with embodiments of the current subject matter are shown. Figure 1A A schematic diagram showing an evaporator device 100 using a cartridge 52 is shown, and Figures 1B to 1E A view of an example evaporator device 100 having an evaporator body 50 and a cartridge 52 is shown. Figure 1B and Figure 1C Top views are shown before and after the cartridge 52 is attached to the evaporator body 50 . Figure 1D is a perspective view of an evaporator device 100, which includes an evaporator body 50 combined with a cartridge 52, Figure 1EA perspective view of a variation of a cartridge 52 holding a liquid vaporizable material is shown. Generally, when a vaporizer includes a cartridge, such as cartridge 52, the cartridge 52 can include one or more reservoirs 56 of vaporizable material. Any suitable vaporizable material can be contained within the reservoirs 56 of the cartridge 52, including solutions of nicotine or other organic materials.

[0251] For example, refer to the following Figure 2 An example of the data exchange circuit is described.

[0252] Figures 1B to 1E An example of an evaporator device 100 is shown having an evaporator body 50 and a cartridge 52. The evaporator body 50 and the cartridge 52 are Figure 1B is displayed as not connected and Figure 1C Middle connection. Figure 1D A perspective view of the combined evaporator body 50 and cartridge 52 is shown, Figure 1E A single cartridge 52 is shown. Figures 1B to 1E Examples include Figure 1A Other configurations that include some or all of the features described herein are also within the scope of the current subject matter.

[0253] The evaporator device can be configured so that the assembly of the device can be more manufacturable. For example, the device can require multiple operations to assemble the complete device. The manufacturing process can increase production by utilizing an assembly architecture that minimizes the discrete number of manual production line operations. In addition, the device can utilize co-molded parts and other mass production techniques to minimize the number of parts and reduce discrete system components. The device can also be constructed using an assembly process designed to facilitate a semi-automatic assembly method that utilizes features that make automated assembly feasible. The assembly process can utilize techniques that result in equally good or higher first-pass yields (FPY) that utilize features that increase FPY.

[0254] The evaporator device can be configured for battery assembly using a protection circuit module (PCM) attached to the raw battery cell prior to final assembly testing and packaging (FATP) to simplify device assembly. The protection circuit PCM and / or fuel gauge can be attached to the raw battery cell at the battery manufacturer or packaging assembly manufacturer to improve production line safety and efficiency.

[0255] Figure 3A schematic representation 300 of communication between a vaporizer device 100, a user device 305 in wireless communication with the vaporizer device 100, and a remote server 307, which can communicate with the vaporizer device 100 directly or through the user device 305, is shown. The user device 305 can be a handheld mobile device such as a smartphone, smartwatch, tablet, or the like, or a desktop or laptop computing device. As described above, the user device 305 can alternatively be a dedicated remote control device. In some aspects, the vaporizer device 100, the user device 305, and the remote server 307 can form a vaporizer system.

[0256] Usually, such as Figure 3 As schematically shown in FIG, any vaporizer device described herein (such as vaporizer device 100) can remotely communicate with a remote server 307 and / or a user device 305 such as a wearable electronic device (e.g., Google Glass, smartwatch, smart clothing, etc.), a smartphone, a self-service terminal, a tablet, a personal computer, etc. Therefore, any of these vaporizers 100 can include communication hardware 34, which can be implemented by a communication chip (e.g., second communication hardware) within or on the vaporizer device 100. Examples of wireless chips can include a Bluetooth chip (e.g., Parani BCD 210, Texas Instruments (TI) CC2650 Bluetooth single-chip solution, etc.), a near field communication (NFC) chip (e.g., Qualcomm's QCA1990, etc.), the near field communication (NFC) chip being configured to enable near field communication and / or enhanced Wi-Fi or Bluetooth communication, where near field communication is used for link setup. As will be described in detail below, in a configuration configured to read such as Figure 1A In the schematically shown embodiment of the cartridge 52, one or more of these wireless circuits may be used to communicate with or between cartridges 52. For example, NFC may be used to read a feature 28 on the cartridge 52 (as an RFID tag).

[0257] The wireless communication chip may include a Wi-Fi enabled chip, such as the CC3000 from TI's SimpleLink series, which can connect the device to a Wi-Fi network. In some embodiments of the current subject matter, the wireless circuitry includes an on-board Subscriber Identity Module (SIM) card, Nano SIM card, or the like (e.g., allowing for 3G / 4G cellular network communications). Alternative forms of communication may be used to establish two-way communication between the vaporizer device 100 and the user device 305.

[0258] The connection between the vaporizer device 100 and the user device 305 may be automatic (after initial setup), or may be initiated by the user through various settings, or may be initiated by shaking the vaporizer device 100 .

[0259] As described above, any vaporizer device described herein that includes a cartridge can be configured to identify and / or recognize the cartridge. One or more identification / recognition methods can be used. The vaporizer can determine information about the cartridge and / or the vaporizable material held therein, such as one or more of the following: the type of vaporizable material (e.g., nicotine, etc.), the concentration of the vaporizable material, the amount of vaporizable material, the configuration of the cartridge (e.g., heater, electrical properties, etc.), the batch number of the cartridge, the date the cartridge was manufactured, the expiration date, etc. This information can be encoded directly on the cartridge or a reference indicator can be provided so that the vaporizer (or a processor in communication with the vaporizer) can use it as an index to look up some or all of this information, or a combination of a reference number and directly encoded material can be provided.

[0260] In some embodiments of the current subject matter, the cartridge can be identified and / or distinguished by the engagement between the cartridge and the vaporizer. The cartridge can be configured to include a keyed interaction with the vaporizer. For example, the shape of the cartridge can be detected by the vaporizer. For example, the cartridge can include n pins or protrusions. When the cartridge is inserted (e.g., by completing an electrical connection), the vaporizer can detect these pins; for n pins, there are 2 n A tag combination.

[0261] The cartridge can be configured or identified based on an electrical property that the vaporizer can detect based on the electrical connection to the cartridge. For example, the vaporizer can make electrical contact with the heater via two or more electrical contacts and / or other electrical contacts and can detect a characteristic resistance, inductance, or time response (e.g., time constant, RC time constant, LC circuit resonance, etc.).

[0262] In some embodiments of the current subject matter, the cartridge can be identified and / or distinguished by markings on the cartridge that are recognized by the vaporizer. These markings can be visible or invisible to the user. For example, the cartridge can be marked with a characteristic UV, IR, or other wavelength-specific ink that can be detected by the vaporizer, and can, for example, include an emitter / detector pair specific to the marking. For example, the marking can include an infrared scannable barcode located on the cartridge. In some embodiments of the current subject matter, the marking can be a pattern indicating information about the cartridge and / or the contents of the cartridge (the vaporizable material), such as a QR code, a barcode, etc. The marking can be symbolic, including alphanumeric characters. The marking can be directly "read" or detected by the vaporizer, which can include a camera or other optical detector, or can be indirectly detected via communication with a second device having a camera or the like (e.g., a wearable device, a smartphone, etc.). For example, the markings on the cartridge can be detected by a smartphone, such as user device 305; the smartphone can use an application (e.g., software) on the smartphone to look up one or more properties in a lookup table to identify the markings, or it can communicate the markings directly to the vaporizer, which can look up the properties, and / or it can communicate with a remote server, which can look up the properties and communicate them to the vaporizer directly or through the smartphone.

[0263] In some embodiments of the present subject matter, the cartridge can be identified using RFID (radio frequency identification) technology. RFID tags have been used for inventory control in a variety of applications. Some RFID technologies use active devices that contain their own power source, while other RFID technologies use passive RFID devices that interact with another powered device, which causes data to be transmitted without relying on the passive device's power source. For example, the cartridge can include one or more RFID chips or components that can be detected and read by a reader on the vaporizer to identify and receive information about the cartridge.

[0264] In some embodiments of the current subject matter, the cartridge can be distinguished and / or identified by communicating with a memory on the cartridge (e.g., an EEPROM) via an electrical connection to the vaporizer. In embodiments where a heater is present on the cartridge, for example Figure 1AIn the example vaporizer shown in , it may be advantageous to use one or more electrical connections (e.g., contacts 60) on the cartridge to communicate with the memory, which are also used to power and / or control the heater. This may be particularly challenging when the cartridge can be engaged with the vaporizer in more than one orientation and / or the heater is controlled by the same contacts, and modulation of the electrical signals applied / received between the cartridge and the vaporizer can change the control and / or temperature determination of the heater. In addition to those electrical contacts that control the heater, one or more other electrical contacts may be used. Typically, communication between the cartridge and the vaporizer can be unidirectional (e.g., reading information about the cartridge and / or vaporizable material from the cartridge via the vaporizer) or bidirectional (e.g., reading information about the cartridge and / or vaporizable material and writing information about the operation of the device, such as the number of uses, the duration of use, the temperature setting, etc.). Information can be written to the cartridge, and this information can be used to derive other information about the cartridge, including the amount of material remaining in the cartridge.

[0265] Generally, any vaporizer described herein can estimate, measure, and / or predict the amount of vapor and / or material (including active ingredient) in the vapor that can be delivered to a user. For example, as described in detail below, the devices described herein can be used to determine and / or control the dosage of a vaporizable material.

[0266] Information about the cartridge and / or the vaporizable material held within the cartridge may be particularly helpful in determining dosage. For example, one or more of the following information may be used to accurately estimate dosage: the type of vaporizable material (e.g., nicotine, etc.), the concentration of the vaporizable material, the amount of vaporizable material, the configuration of the cartridge (e.g., heater, electrical properties, etc.), the batch number of the cartridge, the production date of the cartridge, the expiration date, the thermal properties of the vaporizable material, etc. In some embodiments of the current subject matter, dosage and / or usage information may be stored (written) on the cartridge (e.g., in a memory).

[0267] Vaporizers, vaporizer systems, and methods thereof for user customization of device settings and medication use based on activity patterns are also within the scope of the current subject matter.A vaporizer and / or vaporizer system consistent with the current description can allow a user to personalize the vaporizer and engage in social activities.

[0268] Vaporizers and / or vaporizer systems consistent with embodiments of the current subject matter can be configured to facilitate social interaction via the vaporizer. For example, the vaporizer can be configured to share usage information with others, such as third parties (e.g., healthcare providers, including doctors), to facilitate prescription and medical management. The vaporizer and / or vaporizer system can also be configured to communicate with non-medical third parties (e.g., friends, colleagues, etc.) as well as unknown third parties (making some or all of this information publicly available). In some embodiments of the current subject matter, the vaporizer described herein can identify the vaporizer and provide information about its operation, status, or user input to a public or private network, either by itself or by communicating with one or more communication devices as part of the vaporizer system. In some embodiments of the current subject matter, the vaporizer and / or vaporizer system can be configured to provide one or more interactive games for use by the user and / or multiple users of different (or the same) vaporizers, including multi-player games that can be used with multiple different vaporizers. The games can be tied to the operation of the vaporizer and / or the user's manipulation of the vaporizer (e.g., based on accelerometer output, touch or lip sensing, puff detection, etc.).

[0269] Vaporizers and / or vaporizer systems consistent with embodiments of the current subject matter may also be configured to provide location information, which may include one or more of information regarding one or more of the following nearby user locations: other users (known or unknown, designated or undesignated, etc.), retailers, specific locations (lounge, club, vaporizer-friendly locations), etc. Vaporizers and / or vaporizer systems may also be configured to facilitate ordering based on use or operation of the vaporizer and / or vaporizer system.

[0270] The vaporizer may include GPS functionality, or GPS information may be accessed from another device that is part of the vaporizer system and in communication with the vaporizer.

[0271] As will be described in greater detail herein, the vaporizer can be connected to (e.g., communicate with) an additional device (e.g., a portable, wearable, smartphone, desktop, laptop, etc.) that can implement user-programmable dosage control, real-time usage monitoring, personalized usage settings, device lockout, and social features. For example, the vaporizer and / or vaporizer system can include features related to security controls, including parental controls, user age controls / restrictions, and anti-theft controls. The vaporizer and / or vaporizer system can include anti-theft and / or authentication features that can lock or otherwise restrict the use / operation of the device if stolen and / or used with counterfeit components, and can also be configured to allow for lockout (e.g., a parental lock) to prevent use by children or otherwise prevent unauthorized third-party operation. This type of anti-counterfeiting or other locking feature can be implemented using a cartridge identifier. For example, a cartridge identifier from a verified source or supplier can include a hash or some other verification code as part of the identifier, and the vaporizer can lock out the use of the vaporizer if a cartridge lacking the necessary hash or verification code is coupled to the vaporizer body. Such a feature can be used to require user authentication to be entered at a device communicating with a vaporizer in order for the device to unlock use of the vaporizer. In one example, a cartridge can include an identifier indicating that it contains a controlled substance, and an application on the device can require the user (responsive to determining this about the cartridge via identifier information received from the cartridge) to verify his or her identity (e.g., via password entry, biometric authentication, etc.) and, for the application, to verify that the identified user is authorized to use controlled substances before being able to use the vaporizer with that cartridge coupled to the vaporizer body. In another example, a cartridge containing nicotine can require user authentication, such that the application on the device only allows use of the vaporizer if the user's identity has been verified and the user has been registered as being over a minimum age.

[0272] In some examples, security controls can be incorporated via an application executed on a device in communication with the vaporizer. For example, the application executed on the device in communication with the vaporizer can receive an identifier for the vaporizer itself, or alternatively / additionally receive an identifier for the cartridge, and can determine, based on or otherwise using the identifier, whether the user profile includes security settings or other settings related to the vaporizer or cartridge. Consistent with embodiments of the present subject matter, such functionality can be included in whole or in part within the vaporizer (and / or cartridge), or it can be distributed between the vaporizer and a user interface, which can be presented on an additional device that is part of the vaporizer device, such as a wearable and / or handheld device, a tablet, a laptop, a desktop, an electronic kiosk, etc., and operational control logic. The control logic or other software functionality used to provide these features can include a user interface and can provide input / output and analytical capabilities for modulating the operation of the vaporizer. Examples of first communication hardware for the device and / or second communication hardware for the vaporizer are described above.

[0273] Barrel identification

[0274] Typically, the vaporizer may include one or more technologies for cartridge identification and / or communication, including the use of markings (e.g., QR codes, IR or US markings, etc.), mechanical and / or electronic keying, etc. Specifically described herein are methods and apparatus for electronic cartridge identification and communication, wherein the cartridge can transmit information between the cartridge and the vaporizer via one-way or, in some embodiments of the present subject matter, two-way (including two-way or multi-way) electronic communication, such that the vaporizer can receive information from the cartridge. This information may include information about the vaporizable material and / or the cartridge, such as one or more of the following: type of vaporizable material, concentration of vaporizable material, amount of vaporizable material, volume of vaporizable material, properties of the vaporizable material (e.g., thermal properties, composition, etc.), configuration of the cartridge (e.g., heater, electrical properties, etc.), batch number, production date, expiration date, cartridge authentication, etc.

[0275] The cartridge including the identification circuit (also referred to herein as the cartridge or compartment identification circuit) can be configured to communicate and transmit such information from the cartridge to the vaporizer. The cartridge identification circuit can include a memory (e.g., an EEPROM). In cartridge variations (wherein the heater (e.g., a resistive heating element such as a resistance coil or wire) is controlled by applying power to one or more (e.g., 2, 3, 4, etc.) heater electrical contacts that communicate with corresponding contacts on the vaporizer), despite the increased complexity and potential for damage to the heater, the cartridge identification circuit can still communicate with the vaporizer through the same heater electrical contacts.

[0276] A system for identifying vaporizer device cartridges (e.g., a capsule identifier) ​​can be implemented. More specifically, the identification system can utilize an identification chip, pattern, label, a coating layer applied to the cartridge, cartridge packaging, cartridge identification circuitry, etc. that can contain or convey information (e.g., electronically stored information). The information can be read using a camera, a tag reader (e.g., radio frequency identification (RFID) technology), an optical sensor, by connecting the cartridge to contacts (e.g., spring pins) of the vaporizer device, by direct and / or wired connection, and / or via other information collection systems. Depending on the implementation (e.g., based on cost), a readable or more complex rewritable memory can be utilized. For example, the information can be used to control how the cartridge performs, to communicate the information to a user device, an external application, or a server for analysis.

[0277] The evaporator device can be configured so that each time the cartridge / capsule is inserted into the evaporator body 50, it feels the same to the user. For example, the consistent (device-to-device) capsule retention force between the evaporator body and the cartridge can be within a tolerance range of 25%. In some aspects, the tolerance range can be greater or less than 25%. To achieve consistent capsule retention force, the spring-loaded contact design for the capsule interface can be designed to withstand repeated connections between the capsule and the evaporator body. The spring-loaded contact design can include a spring that is configured to provide consistent capsule retention force over time and is configured to reduce instances of permanent spring deformation. The evaporator device and / or spring-loaded contact design can be configured to provide a tolerance stack to compensate for extremes in container contacts, cartridge contacts, and / or pin travel to ensure excellent capsule electrical signal integrity between the capsule and the evaporator body. The evaporator device can be configured to pass a wobble test standard and, together with the capsule retention, be configured to provide sufficient spring force to ensure excellent electrical signal integrity with the capsule. The evaporator device can be configured to improve product reliability by implementing a device-side wiping / cleaning action on the capsule-side contacts (e.g., the cartridge contacts 60). For example, a wiping action can be generated on the capsule contacts when the capsule is inserted into the device (e.g., the cartridge container 54) to create better electrical connectivity. The wiping action can be accomplished by including a mechanical cover or wiper on the evaporator body 50 and / or the capsule 52. The mechanical cover or wiper can be configured to retract and wipe the container contacts 62 and / or the cartridge contacts 60 when the capsule 52 is inserted into the device. Although mechanical wipers are described herein, computer or other wiping methods can also be implemented.

[0278] The term "capsule" is used in the following description and throughout this document to refer generally to a vaporizer cartridge (e.g., the portion of the vaporizer that holds vaporizable material in a reservoir, such as a Figures 1A to 1EThe evaporator may be a cartridge 52 or other container that can be refilled when empty or disposable in favor of a new pod containing additional vaporizable material of the same or different type. For example, a multi-use vaporizer may include a heating chamber (e.g., an oven) configured to receive a pod having a reservoir or the like for holding vaporizable material. In some embodiments of the current subject matter, the vaporizer may include functionality for communicating with the pod containing the vaporizable material. The vaporizer may also communicate with a device (e.g., a mobile phone, user device 305, etc.) that is part of the vaporizer system, but this is not required. Whether under the control of or otherwise communicating with a device that is part of the vaporizer system or as a standalone unit separate from the vaporizer system, the vaporizer may be configured such that its operation, etc., can be modified and controlled based on one or more parameters received from the pod or accessed from a database or other information source (e.g., a remote server 307) based on the pod's identification. For example, a vaporizer consistent with embodiments of the current subject matter may be configured to recognize a pod and identify (and, in some cases, transmit) or otherwise obtain information about the pod (e.g., a "pod identifier"). In other words, a computing element associated with the evaporator body, such as controller 24, can obtain information about the pod via data exchange. Various methods of pod identification / recognition by the evaporator are within the scope of the present subject matter. While wireless connectivity, as described herein, can be advantageously employed, any of the methods described herein can be performed with or without the addition of wireless communication / connectivity.

[0279] The term "application" is used in the following description and throughout this document to refer to a user interface configured to enable a user to interact with a communication device (or alternatively, a device) that communicates with the vaporizer. Such a device may be a component of the vaporizer system as described above and may include first communication hardware that can establish a wireless communication channel with second communication hardware of the vaporizer. For example, a user device used as part of the vaporizer system may include a general-purpose computing device (e.g., a smartphone, a tablet, a personal computer, some other user device such as a smartwatch, user device 305, etc.) that executes software to generate a user interface for enabling a user of the user device to interact with the vaporizer.

[0280] Consistent with some embodiments of the current subject matter, a vaporizer and / or vaporizer system can be configured to determine a pod identifier to retrieve pod information and information about how the pod is used (e.g., data location tracking usage patterns, switching success rates for consumers in specific geographic locations and demographics to understand areas of focus to improve switching rates). The vaporizer system can also be configured to integrate with an application to obtain more information about the consumer and their intended use (e.g., if a consumer desires to reduce their nicotine consumption over time, for example, the device can use algorithms to reduce the amount of nicotine or vapor over time (which may include different pod configurations of 5%, 3%, and / or 1.7% nicotine). Information about the consumer and / or the consumer's intended use can be determined based on user feedback. For example, the application can ask or prompt the user for answers regarding the consumer's preferences and / or intended use. User feedback can also include learned behavior based on past use. Information retrieved from the pod and / or user feedback can be included in a user profile, usage profile, device profile, etc.

[0281] The vaporizer system can be configured so that the application communicates with the vaporizer device about how to algorithmically control vapor delivery and / or other adjustable features. The application can provide recommendations to the consumer based on expected usage, user profiles, usage profiles, capsule identifiers, etc. For example, the application can provide a recommendation to a user who wants to achieve a goal of switching from a 5% nicotine capsule to a 3% nicotine capsule. The vaporizer system can then verify, at least in part based on the capsule identifier of the capsule, that the consumer has indeed switched to a lower nicotine capsule (e.g., a 3% capsule) before the vaporizer system enables the vaporizer device function, thereby not allowing the consumer to continue using a higher (e.g., 5%) capsule. The vaporizer system can also be configured to deliver the same amount of vapor to the user but adjust the nicotine concentration. The vaporizer system can adjust the operating temperature of the vaporizer to change the total particulate matter (TPM) (e.g., nicotine) delivered to the user.

[0282] The vaporizer system can also be configured to prevent consumers from refilling the pod based on the pod identifier, which can enhance product safety. In response to determining the pod identifier of a pod connected to the vaporizer, the vaporizer system can track pod usage and determine whether such usage is consistent with the pod being tampered with, refilled, reused, etc. For example, the vaporizer system can determine that pod usage exceeds a threshold number of puffs of vaporizable material available for use in the pod. This can indicate that the container has been refilled, and the vaporizer system can disable functionality of the pod and / or vaporizer device. In other aspects, the vaporizer system can determine from the pod identifier that a particular pod has been used with multiple vaporizer devices, exceeding a threshold number of devices consistent with normal use (e.g., resale). The vaporizer system can also prevent pod and / or vaporizer use based on other information obtained from the pod identifier and / or pod (e.g., location, pod age, manufacturer identifier, retailer identifier, number of insertions, number of puffs, etc.).

[0283] The vaporizer system can be configured for unidirectional data transmission of information about the pod (e.g., reading data from the pod, such as the manufacturing date, etc.). The vaporizer system can also be configured for bidirectional data transmission about the pod (e.g., reading and writing to the pod). For example, user preferences regarding how vapor is delivered (e.g., for each specific stock keeping unit (SKU)) can be recorded by writing preference information to the pod (without requiring an application to control the preferences). Pod identification can also be based on the resistance of the heater coil. In some aspects, the device can measure resistance to determine the nicotine level and / or flavor of the pod. For example, a 5%, 3%, or 1.7% pod can be configured to use different coil resistances or a discrete range of coil resistances to heat pods with different nicotine levels. The pod can use only a few bits of data (e.g., 3 bits) to store this information. The pod can also include more bits to store more information and can include a specific bit format to store information related to the pod, user, vaporizer device, usage, etc. In some aspects, the vaporizer system can combine the coil resistance with other pod information obtained based on the pod identifier. The vaporizer system may also use optical or QR or emitter / detector pairs in the device to seek out points at specific locations on the bottom of the pod to determine flavor or other pod information.

[0284] Usage tracking and management can be beneficial features for users. The specific data collected can help determine whether changes to the device need to be made manually or automatically by the user based on specific real-time values, minimums, maximums, or averages of the collected data. Vapor and nicotine content can be useful information to obtain. Puff start time and puff duration can also provide users with detailed information on how their device usage may vary depending on their inhalation. The device can discern when a user has reduced their usage and deliver more or less nicotine in a puff. In some aspects, the vaporizer device can communicate to the user their daily, weekly, or monthly allotment of puffs, nicotine, vaporized material, etc. The device can also be adjusted based on the time of day. For example, if a user prefers higher levels of nicotine in the evening, the device can be set to automatically deliver higher levels of nicotine in the evening. Similarly, information about altitude and temperature can be collected, providing similar benefits. One or more light-emitting diodes (LEDs) on the cartridge and / or vaporizer body can be changed based on the flavor and / or cartridge being used. Alternatively, these settings can be set on a server, and specific settings can be tested and implemented in real time on-site. This information can be tracked and settings saved for the user across multiple cartridges and then transferred from one cartridge to another.

[0285] The vaporizer system can also prompt the user for information about preferences to determine if changes should be made to the vaporizer system. For example, the user can be prompted to answer questions about past usage (e.g., "What type of smoker are you?", "What types of cigarettes do you smoke?", "Are you a menthol smoker / unfiltered smoker, etc.?", "How many cigarettes do you smoke per day?"). Based on the user's answers, there may be a set of different flavors and / or associated total particulate matter (TPM) that are best suited for a particular user (e.g., 20 cigarettes per day vs. menthol smoker). After collecting usage data, the system can provide recommendations based on previous smoking profiles. In some aspects, the application can periodically inquire about current smoking habits.

[0286] In some embodiments of the current subject matter, usage tracking can record data (e.g., cigarette use, puffs smoked) based on gestures to the vaporizer device (e.g., tapping the vaporizer device a specific number of times, shaking the vaporizer device for a specified duration, moving the vaporizer device into a specific mode) or other user input, without having to enter the information into the application. User input can be used to characterize usage and satisfaction with a smoking cessation program and / or specific flavors / strengths over time to improve future recommendations. For example, satisfaction or usage reviews can be combined with flavor data and other demographic data to enhance user profiles (flavor / quit / reduce journeys) to make recommendations based on flavor, strength, total particulate matter, etc. and / or combinations of the above. For example, vapor thickness or operating temperature (producing different vapor thicknesses) may be more suitable for certain flavors.

[0287] In some embodiments of the current subject matter, usage tracking may also include tracking usage relative to one or more usage limits set by the user. The user may set usage limits by inputting a value corresponding to the usage limit via a user interface. To help the user determine appropriate usage limits, the user device may output one or more usage statistics associated with the user via a user interface, such as an average daily, weekly, and / or monthly puff volume. Alternatively and / or additionally, the user may indicate a goal to reduce usage, in which case usage limits may be automatically determined based on previous usage levels. For example, if a user puffs a certain amount x number of times on the device in a first unit of time (e.g., day, week, month, etc.), the usage limit may be set to the puff volume xn for a subsequent unit of time (e.g., the next day, second week, second month, etc.).

[0288] Figure 103A Figures 2 through 3 depict examples of user interfaces consistent with embodiments of the present subject matter. Figure 103A , the user device may display a user interface 1030 that may display one or more usage statistics associated with the user to facilitate setting usage limits for the user. Figure 103A In the example shown, the user interface 1030 displays the average daily usage in terms of the average number of puffs taken per day. However, it should be understood that the user interface 1030 may also display other statistical information at the same and / or different granularity, including, for example, the average daily, weekly, and / or monthly consumption of active ingredient measured in terms of equivalent cigarettes, weight, etc.

[0289] refer to Figure 103B , the user device may display a user interface 1032 that may be configured to receive input from the user to set usage restrictions. Figure 103BIn the illustrated example, the user interface 1032 may include a scrolling horizontal dial that can be adjusted to increase and / or decrease the value of the usage limit. However, it should be understood that the user interface 1032 may include different elements for inputting usage limits. Furthermore, usage limits may be set based on various quantities, such as the amount of puff, the amount of capsule used, the amount of active ingredient consumed, etc.

[0290] In some implementations of the current subject matter, usage tracking can also include notifying the user of the user's progress toward reaching a usage limit. Figure 103C An example of a user interface 1034 is depicted depicting a progress meter 1040 showing that a user has taken zero puffs out of a daily limit of 50 puffs set for the user. Figure 103D , the progress meter 1040 may be updated to show that the user has taken 20 puffs out of the 50 daily puff limit set for the user. Figure 103E As shown, the progress meter 1040 may also be updated to show when the user has exceeded the 50 daily puff limit set for the user. It should be understood that the progress meter 1040 may be one type of visual representation for showing the user's progress toward reaching the usage limit. Other types of visual representations may also be used, including, for example, Figure 103F The bar graph 1050 shown in the example of the user interface 1036 depicted in FIG. Figure 103F As shown in , the bar graph 1050 can display one or more usage statistics, where usage below a usage limit is shown in one manner (e.g., using a first color, symbol, etc.) and usage above the usage limit is shown in a different manner (e.g., using a second color, symbol, etc.).

[0291] Figure 103E Another example of a user interface 1038 is depicted, which notifies a user of the user's progress toward reaching a usage limit. The user interface 1038 may include a banner 1060 displayed by the user device to convey an alert that the user has reached a threshold percentage (e.g., 50% or a different fraction) of the usage limit set for the user. It should be understood that the user can set the threshold percentage that triggers the notification. Furthermore, the user device may communicate the alert to the user in various ways, including, for example, a visual alert (e.g., an LED), an audio alert, a tactile alert, and the like. The notification may be provided by the user device and / or a vaporizer device coupled to the user device.

[0292] In some embodiments of the current subject matter, the setting of a usage limit can be a tracking mechanism that does not affect the operation of the vaporizer device. For example, the vaporizer device can remain active even if the user has exceeded the usage limit set for the user. Alternatively, the operation of the vaporizer device can depend on the user's progress toward reaching the usage limit set for the user. For example, the vaporizer device can be configured to shut down for a period of time in response to the user having reached the usage limit set for the user. The vaporizer device can be configured to adjust the amount of active ingredient delivered to the user (e.g., by adjusting the total particulate matter (TPM)) based on the user's progress toward reaching the usage limit set for the user. Thus, as the user moves closer to exceeding the usage limit set for the user, the vaporizer device can deliver a proportionally smaller amount of active ingredient.

[0293] In some embodiments of the current subject matter, a vaporizer device and / or vaporizer system can be configured to generate recommendations regarding inhalation time, inhalation frequency, flavor, strength, total particulate matter, etc. based on usage patterns associated with a user and / or a group of similar users. For example, one or more groups of similar users can be identified based on similarities in demographics, preferences, smoking cessation goals, etc. of the respective users. Groups of similar users can be identified by applying one or more clustering algorithms, including, for example, k-means clustering, mean-shift clustering, fuzzy C-means clustering, expectation-maximization clustering, hierarchical clustering, etc. The vaporizer device and / or vaporizer system can generate recommendations by applying filtering techniques (e.g., collaborative filtering, content-based filtering, etc.), such that recommendations for a first user include a first type of capsule (e.g., flavor, strength, total particulate matter, etc.) based on the first type of capsule being similar to a second type of capsule preferred by the first user and / or a second user similar to the first user being preferred.

[0294] In some embodiments of the current subject matter, a vaporizer device and / or vaporizer system can generate recommendations for a user by identifying one or more correlations within the usage patterns of at least the user and / or a group of similar users. For example, the vaporizer device and / or vaporization system can identify correlations between the total intake of active ingredient (e.g., total intake of nicotine, etc., per day, week, and / or month), the type of capsule (e.g., flavor, strength, total particulate matter, etc.), and / or puffing pattern. As used herein, a "puffing pattern" can include the time of individual puffs (e.g., first puff at 10 AM, second puff at 10:15 AM, etc.), the frequency of individual puffs (e.g., number of puffs per minute, hour, etc.), the dosage of individual puffs, etc. Thus, the vaporizer device and / or vaporizer system can generate recommendations regarding the type of capsule and / or puffing pattern that reduces and / or minimizes the total intake.

[0295] For example, if the vaporizer device and / or vaporizer system determines that the user and / or group of similar users may have a lower total intake when using a first type of pod rather than a second type of pod, the vaporizer device and / or vaporizer system may recommend the first type of pod to the user rather than the second type of pod. The vaporizer device and / or vaporizer system may also recommend that the first user adopt a puffing pattern (e.g., timing, frequency, dosage, etc.) associated with a lower total intake. It should be understood that the recommendation regarding the puffing pattern may be specific to the type of pod. Thus, the vaporizer device and / or vaporizer system may respond to the use of the first type of pod (e.g., the first type of pod being inserted into the vaporizer device) by at least providing a recommendation regarding a puffing pattern (e.g., timing, frequency, dosage, etc.) that reduces and / or minimizes the total intake of the first type of pod.

[0296] In some embodiments of the current subject matter, a vaporizer device and / or vaporizer system can generate recommendations for a user based on the user's pattern of use of combustible cigarettes. For example, the user's pattern of use of combustible cigarettes may include the brand of combustible cigarettes, the type of combustible cigarettes (e.g., light, menthol, etc.), the amount of combustible cigarettes consumed (e.g., the number of combustible cigarettes used in a day, a week, etc.), etc. These recommendations may include a capsule type and / or puff pattern that mimics the user's pattern of use of combustible cigarettes. For example, the recommendation may include a certain capsule strength, puff duration, puff frequency, puff intensity, dose delivered per puff, and / or length of time between consecutive puffs that will deliver to the user the same amount of active ingredient as the combustible cigarettes used by the user.

[0297] In some embodiments of the current subject matter, a vaporizer device and / or vaporizer system can be configured to adjust an operating parameter of the vaporizer device based on a recommendation. Adjustments corresponding to at least a portion of the recommendation can be made automatically and / or in response to user input indicating that the user accepts at least a portion of the recommendation. For example, the vaporizer device and / or vaporizer system can identify, based at least on a capsule identifier, that a user has inserted a capsule of a first type recommended to the user into the vaporizer device. In response to the user inserting a capsule of the first type recommended to the user, the vaporizer device and / or vaporizer system can adjust the temperature of the heater based on a puff pattern (e.g., timing, frequency, dosage, etc.) also included in the recommendation. Alternatively and / or additionally, the vaporizer device and / or vaporizer system can adjust the total particulate matter (TPM) of an active ingredient (e.g., nicotine, etc.) in the vapor produced by the vaporizer device based on the recommendation.

[0298] In some embodiments of the current subject matter, the vaporizer device and / or vaporizer system can also be configured to generate recommendations based on one or more other factors, including, for example, device health, battery life, and the like. The vaporizer device and / or vaporizer system can also generate recommendations to accommodate periods when the vaporizer device may be unavailable to the user (e.g., flights, meetings, etc.) by identifying at least correlations between puff duration, pod type, and / or puff pattern. For example, when a user and / or a group of similar users use a certain type of pod and / or puff pattern, the vaporizer device and / or vaporizer system may detect a period of time x during which no puffs have been taken. Thus, the vaporizer device and / or vaporizer system can recommend that the user use that pod type and / or observe puff patterns before the period of time during which the vaporizer device is unavailable to the user. For example, the vaporizer device and / or vaporizer system may determine that the user and / or a group of similar users are likely to not take any puffs within four hours after taking 10 puffs on a 5% strength mango-flavored pod. Thus, to prepare the user for a four-hour flight in which the vaporizer device is unavailable to the user, the vaporizer device and / or vaporizer system may recommend that the user take 10 puffs of a 5% mango flavored pod prior to takeoff.

[0299] Device information such as power output, battery voltage, and charging details (start time, length, start and end battery levels, etc.) can also be helpful in understanding the user's usage. Error conditions such as battery failure, communications, pressure sensors, light emitting diode (LED) sensors, and battery fatigue can be tracked to help identify issues with the device or cartridge.

[0300] The vaporizer cartridge identification system can also incorporate social media functionality, where various consumption and usage information can be provided by users on various social media sites. This can be beneficial from a marketing perspective, as word-of-mouth on social media serves as a form of free advertising, and social media is crucial for growing one's business. A "Golden Ticket" cartridge can remind users that they have won something special, such as a free pack of cartridges. As previously mentioned, this "Golden Ticket" feature can also be implemented through social media functionality.

[0301] The consumption tracking feature can identify a variety of detailed information about the cartridges themselves, which can provide very useful information to the user and offer the possibility of increased sales. The ability to identify when a cartridge is nearing empty can provide the option to automatically order a new cartridge or remind the user that a new cartridge needs to be ordered. This can motivate the casual user to order more cartridges, preventing the user from finishing a cartridge and forgetting to order more or delaying doing so due to the need to purchase them manually. Additionally, the user can be prompted for a customer satisfaction survey and / or feedback when the cartridge is nearing its end, which is often the best time to learn feedback about the device or a specific cartridge and / or flavor. Marketing opportunities can be considered, as users can be sent discounts and / or reminders for multi-packs of the same or different flavors based on consumption.

[0302] An identification system for vaporizer device cartridges may include various security features, such as counterfeit identification and / or prevention. The system may identify if a cartridge from a different manufacturer is being used, in which case the cartridges will not be heated, rendering them useless. This may provide assurance that a consumer is not using a vaporizer with cartridges from a different manufacturer simply because a different flavor is available and / or the cartridges are less expensive. Other security features may include theft detection. The cartridge may be authenticated for a specific device or external device so that if the cartridge is stolen, it will not be usable with a different e-cigarette device. Another security feature may include the implementation of thresholds, such as the number of times each cartridge can be used and / or the number of times a cartridge can be refilled, thereby limiting the use of competitor cartridges and / or the refilling of counterfeits.

[0303] Another useful embodiment of an identification system can be point of purchase and / or cartridge tracking information. From a legal and safety perspective and / or from a marketing perspective, the location and / or date the cartridge was originally purchased, as well as the seller information, can be beneficial. For example, if a cartridge is found to be in the possession of a minor, the cartridge purchase information can identify whether the seller did not perform age verification at the point of purchase or whether the cartridge is being purchased by an "age-appropriate" person and provided to the minor. From a marketing perspective, if it is determined that a large number of cartridges were purchased from a particular seller, marketing can adjust its strategy to increase sales. Additionally, since users can be notified that a particular cartridge has been recalled, it is easier to track recalls of particular batches of cartridges.

[0304] The cartridge identification circuit may also be configured such that the cartridge may be inserted into the vaporizer in a variety of orientations without disrupting the operation of the cartridge identification circuit.

[0305] In some embodiments of the current subject matter, the vaporizer can be configured to both read from and write to the memory, for example, when using a cartridge identification circuit. In this example, the vaporizer can write to the cartridge identification circuit. Figure 1A and Figure 2As described, the vaporizer may include a controller that controls the application of power from the battery to the heater to heat and thereby vaporize the vaporizable material. Any of these controllers may include a printed circuit board (PCB) and may also include: a microcontroller; a switch; a resistance measurement circuit including a reference resistor or a Wheatstone bridge and a differential operational amplifier; and an algorithm including logic for controlling parameters. In some embodiments of the current subject matter, the controller (e.g., a microcontroller, a processor, etc.) cycles the switch at fixed intervals to measure the resistance of the resistive heating element relative to the reference resistor and applies the algorithm control parameters to control the temperature of the resistive heating element. This same circuit that controls the heater may be adapted to read and / or modify a memory in the barrel connected via the heater electrical contacts.

[0306] like Figure 2 As shown in the block diagram of , the evaporator can utilize a proportional-integral-derivative controller or proportional-integral-derivative (PID) controller that is programmed to follow a specific proportional-integral-derivative control law algorithm. The PID controller calculates an "error" value as the difference between the measured process variable and the desired set point. When PID based control is enabled, the power to the coil is monitored to determine if acceptable evaporation is occurring. With a given airflow over the coil, if the device is generating vapor (removing heat from the coil to form vapor), more power is required to keep the coil at a given temperature. If the power required to keep the coil at the set temperature drops below a threshold, the device indicates that it is currently unable to produce vapor. Under normal operating conditions, this indicates that there is not enough liquid in the wick for normal evaporation to occur.

[0307] In parallel with such a proportional-integral-derivative controller, the vaporizer controller may also monitor changes in the load of the heater contacts (electrodes) to read from the cartridge memory, thereby identifying the cartridge and receiving information from the cartridge, as described above.

[0308] Therefore, the printed circuit board may further include logic capable of detecting a signal (resistance change) on the heater contact when the memory outputs information stored in the memory. When the microcontroller runs a proportional-integral-derivative control law algorithm, in addition to detecting the difference (error) between the set point and the coil temperature to control the power to the coil so that the coil reaches the set point temperature (e.g., between 200° C. and 400° C.), the microcontroller may also decode a digital signal sent from the cartridge along the heater contact, wherein the received signal includes information about the cartridge and / or the vaporizable material within the cartridge.

[0309] A battery or other power source may power a microcontroller (MCU). The microcontroller may turn on the power to the heater for a predetermined period of time (e.g., every 100ms or 1ms) so that a reference voltage (e.g., Rref or R2) and R_COIL. When Q2 is off, the control law controls Q1 via PWM (pulse width modulation) to power the coil (when Q1 is on, the battery discharges through Q1 and R_COIL). The signal applied by the memory at the heater electrode contacts can be detected as R coil In some embodiments of the present subject matter of the device, the device body further comprises at least one of: a second heater contact; a power switch; a pressure sensor; and an indicator light.

[0310] Typically, the resistance of the heating element (i.e., the resistance between the contacts) can be an input to the microcontroller. In some cases, the resistance can be determined by the microcontroller based on measurements from a circuit having at least one resistor with a known resistance, such as a Wheatstone bridge. Alternatively, the resistance of the heating element can be measured using a resistive voltage divider in contact with the heating element and a resistor with a known and substantially constant resistance. The measurement of the resistance of the heating element can be amplified by an amplifier. The amplifier can be an operational amplifier or an instrumentation amplifier. The amplified signal can be substantially noise-free. In some cases, the charging time of the voltage divider between the heating element and the capacitor can be determined to calculate the resistance of the heating element. In some cases, the microcontroller can disable the heating element during the resistance measurement. The resistance of the heating element can be a function of the temperature of the heating element, so that the temperature can be determined directly from the resistance measurement. The output of the memory (digital signal output) can also be determined based on these resistance measurements. Since the unknown contact thermal resistance between the temperature sensor and the heating element is eliminated, a more accurate measurement can be generated directly based on the heating element resistance measurement rather than determining the temperature from an additional temperature sensor. Additionally, determining the output of the memory based on small changes (e.g., detectable using a Wheatstone bridge in the circuitry of the evaporator) can be performed without compromising heater control as would be the case with changes in thermal resistivity. A temperature measurement can be determined directly, ignoring the effects of the memory output, which can be digitally decoded by a microprocessor either alone or in parallel.

[0311] Figure 2 The PID control block diagram shown is an example of a resistance measurement circuit used in this PID control scheme. Figure 2In the block diagram, the block diagram includes a measurement circuit that can measure the resistance of the resistive heater (e.g., a coil) and provide an analog signal to the microcontroller, the device temperature (which can be directly measured by the microcontroller and / or input into the microcontroller), and input from a sensor (e.g., a pressure sensor, a button, or any other sensor). For example, when a user is taking a puff on the device or when the device is set to a higher temperature (e.g., a standby temperature), the microcontroller can use the sensor input to determine when the resistive heater should be heated. The measurement circuit can also decode changes in the electrical property (e.g., resistance) measured at the heater electrical contacts to determine cartridge information.

[0312] Figure 2 In the , the signal from the measurement circuit goes directly to the microcontroller and the summing block. In the , the signal from the measurement circuit is fed directly to the microcontroller. Figure 3 The summation block in Figure 1 represents the functions that the microcontroller may perform when the device is heating; the summation block shows that the control algorithm uses the error (e.g., in this case, the target resistance minus the measured resistance of the resistive heater) to calculate the power applied to the coil until the next coil measurement is taken.

[0313] In the example shown, the signal from the measurement circuit can also be sent directly to the microcontroller. When the device has not yet heated the resistive heater, for example, after a period of time has passed since the device last heated the resistive heater, the resistive heater can be used to determine a baseline resistance (also referred to herein as the resistance of the resistive heater at ambient temperature). Alternatively or additionally, the baseline resistance can be determined by determining when the coil resistance changes over time at a rate below a certain stability threshold. Thus, the resistance measurement of the coil can be used to determine the baseline resistance of the coil at ambient temperature.

[0314] The known baseline resistance can be used to calculate a target resistance associated with a target increase in coil temperature.Similarly, fluctuations in this baseline resistance at appropriate frequencies corresponding to the output of the memory (EEPROM) can be decoded as information from the cartridge memory. Figure 2 The configuration shown in represents an example of data exchange circuitry consistent with embodiments of the current subject matter, in which data can be transferred between a cartridge memory (e.g., in embodiments in which the identifier 28 of the cartridge 52 includes a cartridge memory for storing information about the cartridge 52) and a controller 24 that is part of a vaporizer body 50 coupled to the cartridge 52. Such data exchange circuitry allows data (e.g., one or more parameters of the cartridge, vaporizable material contained in the cartridge, etc.) to be transferred between the cartridge memory and the controller 24 that is part of the vaporizer body 50.

[0315] Figure 2The example provides for both delivering electrical energy from a power source 22 that is part of the vaporizer body 50 to an atomizer 26 that is part of the cartridge 52, and also provides for data exchange between an identifier 28 on the cartridge 52 and a controller 24 that is part of the vaporizer body 50 by merely engaging two mating electrical contacts (cartridge contacts) on the cartridge 52 with corresponding electrical contacts (vaporizer body contacts) on the vaporizer body 50. Other embodiments of data exchange circuits for such data exchange may include the use of a dedicated data circuit separate from the power delivery circuit for transferring power from the power source 22 (on the vaporizer body) to the atomizer 26 (on the cartridge). However, since more than two sets of mating electrical contacts may be required, having two separate circuits for data exchange and power delivery increases the complexity of the hardware. Implementations of the present subject matter allow for the use of two mating contacts on the cartridge 52 and the vaporizer body 50, respectively, for data exchange and power delivery. It will be understood that the above reference to Figure 2 The fluctuation of the baseline resistance discussed represents one option for combining data exchange and power delivery via a single pair of mating electrical contacts. For example, within the scope of the current subject matter, data exchange can be encoded in the power circuit by fluctuations or modulations of one or more of frequency, resistance (as described above), current pulses, voltage, etc.

[0316] The baseline (also known as the resistance of the resistance heater at ambient temperature) can also be used to calculate the target resistance. The evaporator temperature can be used to calculate the absolute target coil temperature instead of the target temperature rise. For example, the evaporator temperature can be used to calculate the absolute target coil temperature for more precise temperature control.

[0317] The evaporator device can be configured for reliable temperature control. For example, the test swing resistance on a new device and / or new coil may be <10mOhm for 100% unused devices. The device can be configured to have an acceptable swing resistance of <20mOhm swing resistance on >=95% of the devices before and after testing after extensive device use (spring contact abuse test). Testing can include cyclically heating the test load chamber with wet / dry cycles and 10k cycles of chamber insertion.

[0318] The resistance of the heating element can be a function of the temperature of the heating element (and the output of a cartridge accumulator connected in parallel with the heating coil), so that the temperature can be determined from the resistance measurement. The output of the cartridge accumulator can be detected by analyzing relatively small changes in resistance within a specific frequency (time) range; these changes can be ignored or filtered out when calculating the temperature. The resistance of the heating element has a roughly linear relationship with the temperature of the heating element.

[0319] The same cartridge identification circuitry can also be programmed with information about the cartridge, vaporizable material, and cartridge history, including, for example, time of use and / or total power applied.

[0320] The information stored (read and / or written) on the memory can be encoded, including using encryption, error correction coding (e.g., Hamming code, etc.), etc. In operation, when a cartridge is first inserted into the vaporizer body, the vaporizer microcontroller can be configured to first determine whether a signal encoding information about the cartridge and / or identifying that the cartridge is compatible with the vaporizer can be read from the cartridge. The information can be read using the vaporizer's measurement circuitry. In some embodiments of the current subject matter, the vaporizer can use default settings even when the cartridge may not be read (e.g., the cartridge identification circuitry may not be included or cannot be read from the cartridge identification circuitry).

[0321] During operation, if detected, the vaporizer can periodically (e.g., after each puff, etc.) write to the memory in the cartridge identification circuit. The vaporizer can perform the write by applying power to the capacitive circuit for a predetermined timer period. The vaporizer microcontroller can then apply a bit pattern to one of the contacts by applying a high voltage to the contacts at a controlled rate, which will be received by the I / O line of the memory.

[0322] The vaporizer can signal the memory to request a read from the memory, similar to how the device writes to the memory. The battery voltage applied to the heater contacts can then be disconnected to allow the memory (e.g., an EEPROM) to take control of the I / O line and use it to output data, thereby providing a digital output (switching the I / O line low / high) that transmits the output detected by the vaporizer through the resistance measurement circuit. Typically, if the memory is transmitting, the absolute accuracy of the temperature control can be affected; the vaporizer can be configured so that the device does not heat when the memory is transmitting (outputting), and normal heating operation does not trigger the memory to transmit data.

[0323] Cartridge identification circuitry consistent with one or more embodiments of the current subject matter may be integrated and / or combined into a custom chip (e.g., an ASIC). Such dedicated circuitry may be included as an identifier (e.g., Figure 1A The identifier 28 shown in FIG.

[0324] Alternatively or additionally, the evaporator can incorporate an LDS (laser direct structuring) method and the resulting structure. In LDS, circuit traces are integrated into one or more mechanical components of the evaporator, such as the evaporator housing and / or the evaporator body housing, as a substitute for a traditional printed circuit board. As a result, weight and assembly space can be effectively reduced. For example, a three-dimensional circuit carrier can be injection molded from a modified polymer material, allowing laser activation of the circuit traces on the surface of the circuit carrier. A laser can be used to engrave the circuit layout directly onto a plastic part, typically immediately after the part is injection molded (no tools or masks are required). The activated area can be metallized in a chemical metallization bath to create conductive traces. Other similar processes can be used alternatively or additionally, such as molded interconnect devices or Midentifier structures, in which injection molding and hot stamping are used to integrate conductive structures. Therefore, any component described herein may include an LDS doping material compatible with the LDS method for forming circuits. In particular, electrical traces for the cartridge (eg, identifier 28 embodied as and / or within the circuit) may be formed directly on the plastic components of the cartridge without the need for an additional PCB.

[0325] As will be described in more detail below, information stored in the memory of the cartridge identification circuit (such as the information described herein) can be used for dose control (e.g., calculating and storing dose information) as well as for safety, communication, and storage of operating parameters, particularly in devices with wireless capabilities. However, cartridge identification can be useful even in the absence of wireless communication capabilities.

[0326] As discussed, a memory (e.g., an EEPROM) can store information about the vaporizable material and / or the cartridge. An example of information that can be stored can include values ​​related to the specific performance of the heating element, such as the nominal heater R (resistance) for the cartridge, which includes the heating element of the cartridge. This value can be determined and stored at the factory when the device is manufactured / produced, and / or can be performed subsequently. Storing the specific R value of each cartridge in a memory belonging to the cartridge can be useful for precise temperature control of the device, including determining the baseline resistance at ambient temperature, as described above. Although the resistance / baseline measurement on the production line may be slightly different from the measurement used by the device, a baseline adjustment (determined by an algorithm) can also be used. Alternatively or additionally, once a reliable baseline for the cartridge has been determined, the baseline can be associated with an identifier belonging to the specific cartridge (e.g., in a remote database, on a remote server, etc.) so that if the cartridge is removed and reinserted, the same baseline value can still be used (once the cartridge identifier is determined), which is a faster check than waiting for a stable baseline to be detected.

[0327] Typically, storing cartridge characteristics (e.g., heater resistance) in the cartridge itself can also be useful for confirming that the connection between the vaporizer and the cartridge is good and that the vaporizer's resistance measurement circuit is functioning properly. Thus, in any of the methods and apparatus described herein, the nominal cartridge resistance can be stored in the cartridge's memory (or can be stored on a remote server / device and retrieved based on a unique cartridge identifier) ​​and can be used to confirm that the connection between the device and the chamber is good and / or that the device's resistance measurement circuit is functioning properly and / or that the cartridge's resistance has not changed since the cartridge was assembled or filled.

[0328] As described above, in some embodiments of the current subject matter, the vaporizer can write usage information to the cartridge's memory; the usage information can be used to estimate the amount of vaporizable material that has been removed from the cartridge and the amount of vaporizable material that remains. The usage information can include the number of puffs / puffs taken, the dose delivered, etc.

[0329] Cabin Identifier Technical Specifications

[0330] By way of non-limiting example, consistent with an embodiment of the present subject matter as described herein, one or more embodiments may include one or more of the following basic cabin identifier device requirements: maximum electrical supply voltage of 3.3 volts; minimum supply voltage of 1.8 volts; maximum electrical supply current of 5 milliamperes; data interface: 1-Wire serial; minimum data rate of 50 kbps; package: 2-pin package; pin 1: power / serial sharing; pin 2: ground; minimum ESD resistance: ±8 kV; security element to prevent cloning: ECDSA signature verification; minimum one-time programmable flash memory for Mfg.: 92 bits; factory one-time settable value: unique identifier and / or private key for ECDSA security; non-resettable counter: 9-bit counter and / or 16-bit counter; non-resettable fusion bit: 5 bits; temporary flash memory: 32 bits; maximum L x W x H (L x W x H): 3 mm x 3 mm x 1 mm; and / or interface pads: exposed pads for direct interface to spring finger contacts.

[0331] To further illustrate, Figure 102 A table 1200 is depicted that illustrates data fields that may be included in a tank identifier consistent with embodiments of the current subject matter. It should be understood that a tank identifier consistent with embodiments of the current subject matter may include one or more of the data fields shown in table 1200. Additionally, as Figure 102 As shown, a pod identifier consistent with embodiments of the current subject matter may include data fields that are set during manufacturing and data fields that are set by the vaporizer assembly during operation.

[0332] Reference again Figure 102A tank identifier consistent with embodiments of the present subject matter may include one or more data fields programmed during manufacturing, the values ​​of which indicate the tank structure, tank flavor, tank strength, manufacturing date, fill date, fill plant, manufacturing plant, and heater coil resistance. Each data field may store one or more data bits. For example, the tank structure may be stored as a 5-bit value, the tank flavor may be stored as an 8-bit value, the tank strength may be stored as a 3-bit value, the manufacturing date and fill date may each be stored as a 16-bit value, the fill plant and manufacturing plant may each be stored as a 6-bit value, and the heater coil resistance may be stored as a 32-bit value. Alternatively and / or additionally, a tank identifier consistent with embodiments of the present subject matter may include one or more data fields, the values ​​of which correspond to a private key (e.g., a 256-bit Elliptic Curve Digital Signature Algorithm (ECDSA) key) and a unique tank identifier (e.g., a 64-bit value). The authenticity of a tank carrying a tank identifier consistent with embodiments of the present subject matter may be determined based on the private key and / or the unique tank identifier included in the tank identifier.

[0333] In some embodiments of the current subject matter, a pod identifier consistent with embodiments of the current subject matter may further include one or more data fields whose values ​​may be set by a vaporizer device into which a pod carrying the pod identifier is inserted. The values ​​of these data fields may correspond to a puff counter (e.g., a 10-bit value), pod power (e.g., a 16-bit value), a lock fuse (e.g., a 6-bit value), and / or a miscellaneous data register (e.g., a 32-bit value). It should be understood that at least some of these data values ​​may not be reset, including, for example, the puff counter, pod power, and lock fuse.

[0334] By way of non-limiting example, consistent with implementations of the present subject matter as described herein, one or more embodiments may include one or more of the following guiding principles for mechanically attaching the pod identifier to the pod: must not require surface mount assembly / surface mount technology (SMA / SMT) to a PCB or other substrate prior to installation; must be mechanically attached directly to the pod; must be mechanically robust to survive high-speed assembly; and / or must be packaged / ready for high-speed insertion. Examples of one or more embodiments for mechanically attaching the pod identifier to the pod may include one or more of the following: a flat package with quad flat no-lead (QFN) pads; staking and / or glue heated into the cavity; packaging on nails; and / or attachment methods including: heat staking; glue; snap fit; encapsulation; stapling and / or pressing.

[0335] By way of non-limiting example, consistent with implementations of the present subject matter as described herein, one or more embodiments may include one or more operations of the following pod identifier manufacturing process: installation into the pod (e.g., using robotic and / or automated placement and attachment to the pod body; packaging must be mechanically robust to handle high-speed installation); initial communications (e.g., electrical testing and programming of initial manufacturing information into the pod identifier integrated circuit, which must support high-speed inline programming for automation); handling and stuffing; filling the pod; more communications (e.g., post- and / or pre-fill programming and locking of the pod identifier integrated circuit; which must support high-speed inline programming during the filling operation); handling, stuffing, and packaging; and / or shipping.

[0336] Applications / Connectivity.

[0337] The vaporizer and / or vaporizer system may include software, firmware, or hardware that is separate or detachable from the vaporizer and that communicates wirelessly with the vaporizer. For example, an application program ("app") may be executed on a processor of a portable and / or wearable device including a smartphone, smartwatch, etc., which may be referred to as a personal digital device or alternatively simply as a device that is part of the vaporizer system (e.g., Figure 3 These digital devices may provide an interface for the user to engage with and interact with functions associated with the vaporizer, including data communication back and forth between the vaporizer and the digital device and / or with other third-party processors (e.g., servers such as those in Figure 3 The device may communicate data to a server 307 (e.g., a server 307 in the device). For example, a user may optionally control certain aspects of the vaporizer (temperature, dosage, etc.) and / or transmit and receive data to and from the vaporizer via a wireless communication channel between the device's first communication hardware and the vaporizer's second communication hardware. Data may be communicated in response to one or more actions of the user (e.g., including interaction with a user interface displayed on the device) and / or as a background operation, such that the user does not have to initiate or authorize the data communication process.

[0338] The user interface can be deployed on the digital device and can assist the user in operating the vaporizer. For example, the user interface operated on the digital device can include icons and text elements that inform the user of various ways in which the user can adjust or configure the vaporizer settings.

[0339] The vaporizer may include or incorporate one or more authentication features. For example, the user interface ("app") may include, for example, PIN-based authentication and biometric authentication (which may include fingerprint-based authentication, iris scan-based authentication, facial recognition-based authentication, etc.). Authorization may include age analysis, such as estimating or calculating the user's age based on analysis of facial features. Authorization may be used to lock / unlock the vaporizer.

[0340] The authentication process can be implemented as a feature of an application installed and running on a personal digital device that is capable of communicating data using wired or wireless methods (e.g., as part of the vaporizer system described herein). The personal digital device (e.g., a smartphone) can have an operating system capable of running the application.

[0341] The vaporizer can be deactivated after a period of inactivity, for example, by entering a "sleep mode" when no use is detected within a predetermined and / or preset time period. In some embodiments of the current subject matter, in order for the vaporizer to be activated and thus usable by the user for vapor generation purposes, user authentication is required to ensure that the device is being used by the intended user and to prevent unauthorized use, accidental or unintentional activation of the device, or ingestion of active ingredients (including nicotine) by individuals of ineligible age. Personal identification number (PIN)-based authentication can apply a user-selected PIN to verify end-use. Alternatively and / or additionally, one or more forms of biometric authentication can be used to authenticate the user and reactivate the vaporizer. For example, a fingerprint-based authentication process can authenticate the user. An iris scan-based authentication process can use an eye or iris scan, etc. to authenticate the user. Facial recognition-based authentication can use a facial scan or image processing algorithm to authenticate the user. Iris scan-based authentication and facial recognition-based authentication can be particularly useful if the personal digital device has a camera (e.g., a front-facing camera).

[0342] The personal vaporizer can be disabled after a threshold criterion is met. For example, the vaporizer can be deactivated after a period of inactivity. The inactivity period can be pre-set and / or selected by the user (e.g., using control software running on the personal digital device). Thus, the inactivity period can be a configurable parameter of the vaporizer. The application software / firmware can include functionality to unlock or activate the vaporizer using authentication, as described above.

[0343] An authentication process may be performed. If the authentication process is unsuccessful, the vaporizer may remain disabled. If the authentication process is successful, the vaporizer may be unlocked and ready for use.

[0344] The vaporizer may include a heating element configured to heat a vaporizable material. The application may be configured to disable and / or lock the vaporizer by disabling power to and / or use of the vaporizer's heating element. For example, the control system (e.g., via firmware) may be configured to selectively prohibit certain (e.g., standard heating) actions of the user-activated heating element. In some aspects, the device may be configured to ignore pressure sensor readings and / or other indicia of a user puffing on the device. The application may be configured to provide a notification indicating that the vaporizer has been operationally disabled and / or locked. Additionally or alternatively, the device may be configured to alert the user that the device is locked (e.g., using one or more LEDs, sounds, haptics, etc.) upon determining that the user has attempted to puff on the device. In some embodiments, the vaporizer may be configured to become operational in response to the vaporizer being within a threshold range of a user device. In some embodiments, the vaporizer may be configured to become operational in response to the vaporizer receiving a signal from the user device. In some embodiments, the vaporizer may be configured to become inoperable in response to the vaporizer receiving a signal from the user device. For example, the user may lock and / or unlock the vaporizer through user input to the application, such as using a touch recognizer.

[0345] The vaporizer device can be configured to lock so that key functions (e.g., vapor production) are disabled to prevent unauthorized parties from using the locked device. In some embodiments, the vaporizer device paired with the application can implement a lock / unlock feature so that a given user can lock the device, thereby preventing unauthorized users from unlocking and / or accessing the vaporizer device. The lock feature can be configured with strong security (e.g., encryption, firewall, etc.) to prevent hackers from defeating the lock feature.

[0346] The application can be configured to disable and / or lock the vaporizer in response to the vaporizer being outside a threshold communication range with the user device. For example, if the vaporizer is out of communication range with the user device, the vaporizer can be configured to disable vaporizer operation such that the vaporizer is inoperable until it returns to communication range with the user device.

[0347] The application device may be configured to disable and / or lock the vaporizer in response to location and / or time parameters (eg, how long the vaporizer has been out of range of the user device).

[0348] The application can be configured to enable and / or unlock the vaporizer in response to the vaporizer being within a threshold communication range with the user device. For example, the vaporizer can resume an operational state in response to being within a communication range with the user device.

[0349] The vaporizer can be configured to receive information associated with a first user of a first user device. The vaporizer can be configured to activate and / or unlock vaporizer operation in response to the vaporizer and the first user device associated with the first user being communicatively coupled and within a threshold communication range. The vaporizer can be configured to disable vaporizer operation in response to the vaporizer being outside a threshold communication range with the first user device. The vaporizer can be configured to disable vaporizer operation in response to the vaporizer being communicatively coupled with a second user and / or second user device. For example, if a first user pairs the first vaporizer with the first user device, the first vaporizer can be disabled and / or locked in response to the second user attempting to pair the first vaporizer with the second user device. Figures 23 to 30 An exemplary user interface is shown for tracking reports and other data indicating underage use, retailers, locations, reviews, surveys, preventative measures, and the like.

[0350] Locking out the device may be performed by disabling power to the evaporator's heater element, pressure sensor, or other components.

[0351] In some embodiments, a vaporizer device lock feature for locking (e.g., disabling) or unlocking (e.g., enabling) a vaporizer device from a user interface of a user device can be configured to be available when the vaporizer device is within communication range of a user (e.g., the user device is within a threshold range of the vaporizer device). In response to the vaporizer device being locked, the vaporizer device can be configured to disable some or all functions of the vaporizer device. In response to detecting an attempted inhalation / puff on a locked vaporizer device, the vaporizer device can be configured to display a "locked" LED indicator, block airflow, and / or provide another indication that the device is locked. In some aspects, locking the vaporizer device can change the state of the home screen on the user interface so that if the vaporizer device is locked, a "locked" notification is displayed, and the user can unlock the vaporizer device from the home screen. The vaporizer device can be configured so that the user can unlock the vaporizer device only via an application logged into the user account. In some embodiments of the current subject matter, the lock feature and / or unlock feature can be available with or without Wi-Fi and / or data service reception by the user / device.

[0352] In some embodiments, the vaporizer device and / or the user application can be configured to display a first notification of a locked device that is "in range" (e.g., the user device is within a threshold range of the vaporizer device). In some embodiments, the vaporizer device and / or the user application can be configured to display a second notification of a locked vaporizer device that is "out of range" (e.g., the user device is outside a threshold range of the vaporizer device), such as Figure 28As shown. The vaporizer device and / or the user application can be configured to display an option for the user to "opt in" to some or all of the "auto-lock" features. For example, the vaporizer device and / or the user application can be configured to display a time-based countdown timer for "auto-locking" the vaporizer device when the user device is "in range" (e.g., within a threshold range of the vaporizer device). In some embodiments of the current subject matter, the user can have the option to specify the length of time after which the "auto-lock" response occurs (e.g., a time different from the default time of 24 hours can be provided). In some embodiments, the vaporizer device can be configured to automatically lock the vaporizer device in response to the vaporizer device changing from an "in range" state to an "out of range" state. In some embodiments, the vaporizer device can be configured to automatically lock the vaporizer device in response to the vaporizer device being "out of range" for a defined period of time (e.g., 24 hours). In some embodiments of the current subject matter, the vaporizer device can be configured to automatically unlock in response to returning to an in-range state. In some embodiments, the vaporizer device and / or user application may be configured to display an overlay depicting the lock feature / unlock feature and / or a picture and / or animated gif representation of the vaporizer being in range and / or out of range.

[0353] Figures 23 to 30 An exemplary user interface is shown that may appear in an application installed on a communication device that communicates with a vaporizer (eg, as part of an "app" or other software on a user's mobile device). Figures 23 to 30 The user interface of the invention relates to a locking and reporting feature that may provide benefits in providing data as well as vaporizer-specific controls for preventing unauthorized and / or underage use, purchase, etc. of the vaporizer.

[0354] Figure 23 An app screen view or similar method can be used to prompt the vaporizer user to implement the device lock feature. In one example, this can be provided as an "opt-in" feature, so that the vaporizer has a default state that does not automatically transition to a locked state. Alternatively, the lock feature can require the user to "opt-out" to disable automatic locking. In other examples, the automatic lock feature may not be a user-configurable option.

[0355] Figure 24 and Figure 25The screen view shown in FIG. 1 shows a view that may be presented to a user upon selecting the opt-in feature. This screen may be used to explain that if a certain period of time passes without communication between the user's mobile device and the vaporizer exceeding a threshold length of time, the vaporizer will automatically transition to a locked state. Functionally, when this feature is enabled, the vaporizer's controller (e.g., a microcontroller, a PCB, software running on a programmable processor, other computing hardware, etc.) may perform operations to track the duration of time since the last successful communication with the user's mobile device paired with the vaporizer. If this duration exceeds a certain threshold, the vaporizer controller may interrupt the normal operation of the vaporizer, for example, by preventing the delivery of current to the heating element or otherwise activating the atomizer that generates the inhalable aerosol.

[0356] Figure 26 and Figure 27 The screen view shows how to activate controls such as sliders ( Figure 26 and Figure 27 In one exemplary embodiment, the user can disable and enable the automatic lock feature by, for example, clicking on the upper left corner of the screen in the Figures 23 to 25 The view selection opts in or opts out with the auto-lock feature available. At any given time, the user can choose to use Figure 26 and Figure 27 The on / off selection shown enables or disables the auto-lock feature for the vaporizer. This feature may need to be disabled if the user intends to use the vaporizer for a period of time without the user's mobile device nearby, or if the user's mobile device needs to be turned off or otherwise placed in a state where it cannot communicate with the vaporizer. In some embodiments of the current subject matter, it may be advantageous to have a time limit on the auto-lock disable feature, such that the vaporizer controller returns to the auto-lock enabled state after a fixed or user-configurable duration in which the auto-lock has been disabled.

[0357] In some embodiments, the vaporizer device and / or the user application can be configured to display a first notification of a locked device when the device is "in range" (e.g., the user device is within a threshold range of the vaporizer device). In some embodiments, the vaporizer device and / or the user application can be configured to display a second notification of a locked vaporizer device when the device is "out of range" (e.g., the user device is outside a threshold range of the vaporizer device), such as Figure 28As shown. The vaporizer device and / or the user application can be configured to display an option for the user to “opt in” to some or all of the “auto-lock” features. For example, the vaporizer device and / or the user application can be configured to display a time-based countdown timer for “auto-locking” the vaporizer device when the device is “in range” (e.g., the user device is within a threshold range of the vaporizer device). In some embodiments of the current subject matter, the user can have the option to specify a length of time after which the “auto-lock” response occurs (e.g., a time different from the default time of 24 hours can be provided). In some embodiments, the vaporizer device can be configured to automatically lock the vaporizer device in response to the vaporizer device changing from an “in range” state to an “out of range” state. In some embodiments, the vaporizer device can be configured to automatically lock the vaporizer device in response to the vaporizer device being “out of range” for a defined period of time (e.g., 24 hours). In some embodiments of the current subject matter, the vaporizer device can be configured to automatically unlock in response to returning to an in-range state. In some embodiments, the vaporizer device and / or user application may be configured to display an overlay depicting the lock feature / unlock feature and / or a picture and / or animated gif representation of the vaporizer being in range and / or out of range.

[0358] in other words, Figure 28 A screen view is shown that may indicate that auto-lock is enabled and the vaporizer is out of range of the mobile device (and therefore unusable until communication is reestablished between the mobile device and the vaporizer). Figure 29 An optional screen view is shown that can be included to require the user's mobile device to receive a passcode or some biometric verification (e.g., fingerprint sensor recognition, facial recognition, etc.) to reauthorize use of the vaporizer, thereby allowing the mobile device to communicate with the vaporizer controller to once again allow the vaporizer to operate. Such a feature can prevent minors or other unauthorized users from using the vaporizer simply by being somewhere close enough to the user's mobile device (e.g., in an adjacent room, etc.) to allow communication between the mobile device and the vaporizer to be reestablished. Figure 30 An example of a screen view is shown that may indicate that proper authorization has not been received such that the vaporizer will remain disabled.

[0359] In some embodiments, a vaporizer lock feature for locking (e.g., disabling) or unlocking (e.g., enabling) a vaporizer device from a user interface of a user device can be configured to be available when the vaporizer is within communication range of a communication device (e.g., the user device is within a threshold range of the vaporizer device). In response to the vaporizer device being locked, the vaporizer device can be configured to disable some or all functions of the vaporizer device. In various examples, locking the vaporizer can include one or more of: disabling power to the heater element, ignoring input from a pressure sensor or other switch configured to activate the vaporizer to generate aerosol, and the like. In response to detecting an attempted inhalation / puff on a locked vaporizer device, the vaporizer device can be configured to display a "locked" LED indicator, block airflow, and / or provide another indication that the device is locked. In some aspects, locking the vaporizer device can change the state of the home screen on the user interface, such that if the vaporizer device is locked, a "locked" notification is displayed, and the user can unlock the vaporizer device from the home screen. The vaporizer device can be configured so that the user can only unlock the vaporizer device via an application logged into the user account. In some implementations of the current subject matter, the lock feature and / or unlock feature may be available with or without Wi-Fi and / or the user / device having data service reception.

[0360] In addition to the aforementioned automatic lock feature, the vaporizer device can also be configured to provide an "access feature" to registered app users for account login with or without age verification. The vaporizer device can optionally be configured so that access feature availability can be linked to the app and / or user login, rather than to a specific user mobile device. In some embodiments, a user device using a device app with a specific user logged into a user account can unlock / lock a specific device that was previously locked by that user using another instance of the device app.

[0361] Figures 31 to 36 Exemplary user interface screen views that may appear in an application installed on a communication device are shown. Figures 31 to 36 The user interface screen views shown relate to reporting features that can be used on a mobile device that does not need to be paired with a vaporizer. It should be understood that while the shape and size of these screen views are consistent with the dimensions of a mobile device such as a smartphone, the indicated user interface functionality can be implemented on any computing device such as a tablet, desktop, or laptop computer.

[0362] Figure 31 and Figure 32A screen view is shown through which a person can report a vaporizer (referred to on the view as a "device" being used by an unauthorized user (e.g., a minor). The view allows entry of a serial number and includes a data entry option (here, a drop-down menu or scroll-down menu, but optionally any type of input, including free text entry) for the reporter to indicate their title or other identifying information. For use in a school setting (e.g., if these features are used to prevent vaporizer use in schools other than by minors), the title might be "school administrator," "teacher," "counselor," etc. The view also includes fields for entering identifying information about the school and a "Submit" user interface element to allow the entered data to be transmitted to a server for analysis, aggregation, etc. The view may include user interface elements for providing the user with instructions on how to find the device's serial number, and optionally instructions for sending the device to a location where it can be analyzed to determine its origin.

[0363] exist Figure 33 and Figure 34 In the example, the screen view shows an example of an invalid serial number being entered. Here, the user interface can ask the user to double-check the serial number, and if the serial number is correct for the confiscated vaporizer, the user can be prompted to report it as a counterfeit vaporizer, which can trigger other actions. If the device is identified as counterfeit, then Figure 35 The screen view may prompt the user to enter any available further information, such as place and date of purchase, etc., and may add a prompt requesting the user to send the device to the manufacturer or other location for analysis and investigation. Figure 36 is an instance of the Thank You screen view.

[0364] Figures 37 to 41 Shown are exemplary screen views that can be displayed on any computing device to visually display data results based on data reported via the methods discussed herein and other methods. It will be understood that these screen views can be displayed on any type of computing device.

[0365] Figure 37The screen view displays a map view that includes school markers with various overlay options, allowing the user to select the type of data to be displayed on the map relative to one or more locations. The overlays may include a heat map-style view that illustrates the frequency of different events determined based on the collected data. Data sources used for collection may include, for example, school reports (e.g., which can be entered via the aforementioned screen view), retailer data (e.g., sales volume at a given location, tracking information regarding the source of sales of confiscated vaporizers, etc.), social media data (e.g., data regarding the estimated age and demographics of social media users discussing vaporizers and / or their use relative to the estimated locations of those social media users), secret shopper data (e.g., data regarding unauthorized or insufficiently authorized sales to undercover investigators attempting to purchase vaporizers from retail stores), regulatory reports (e.g., from the FDA, etc.). The screen view may also include a data insights subview that displays information about recently added data, trends, and more. Clicking on a given school location enables deeper analysis of specific data types. Such a screen view can be used to develop strategies to prevent underage vaporizer use, for example, by easily displaying geographic correlations between school confiscations, social media, illegal sales activity, and more.

[0366] Figure 38 The screen view shows an example of a news feed mentioning a given school regarding vaporizers and / or underage use of such devices. Figure 39 The screen view displays a summary of the confiscated device report for the selected school location. Figure 40 The screen view shows a map with a heatmap but no other data, and Figure 41 A screen view of shows a map with social media information highlighted.

[0367] Figures 42 to 49 A screen view is shown illustrating exemplary features of data driven functionality surrounding the use of data such as above in tracking the use and / or sale of illegal vaporizers. The data source control box allows a user to view data from different sources as an overlay on a map based on location. Figure 42 , a fictional retail store was highlighted and overlaid with social media mentions. Figure 43 Examples of additional data insights related to the fictitious retail store are shown, along with statistics (eg, 6 confirmed confiscated devices were sold there). Figure 44 A map view with no data overlay is shown. Figure 45 Shows the option to drill down to additional retailer reports. Figure 46 shows examples of data from such reports, including details of seized devices, Figures 47 to 49Social media data with estimated locations is displayed to allow inference of relevance to given retail stores and other data sources.

[0368] In addition to the data sources described above (which can be used with existing vaporizers that may not include connectivity features), other data sources provided by such connected vaporizers can further enrich the functionality of the current subject matter. For example, geofences can be set up near schools and / or other places where underage vaporizer use is considered problematic. Vaporizers with connectivity features can be detected when in such areas, enabling mapping of potential hotspots of illegal use. In other examples, an application executable on a mobile device can be provided to teachers or other school employees. Such an application can allow the mobile device to act as a mobile detector for vaporizers in the mobile device's vicinity. Collecting serial number data or other data from such vaporizers can better track the origin of vaporizers used by teenagers and other minors.

[0369] In some embodiments of the current subject matter, the vaporizer and / or associated application can have a dashboard-style user interface in which a user can view one or more metrics indicating his or her progress over time. These metrics can be generated or otherwise derived from individual data (e.g., data specifically related to the user) and / or group data (e.g., data aggregated and anonymized from multiple users). For example, the group data can show, as a group, what the average smoking conversion rate is at any given time since starting to use the vaporizer. The device can provide a view in which the user can select other users to define a group (a group of people) based on their starting criteria (e.g., packs per day, age, gender, etc.).

[0370] The dashboard can be configured to display different quit smoking programs and their success rates for certain individuals, groups, subgroups, and / or demographics. For example, for a certain group (e.g., women aged 30 to 39 in Southern California), the dashboard and group data may show that the success rate of the first quit smoking program is 50%, while the success rate of the second quit smoking program is 75%. The user can select the second quit smoking program and view different operations related to the quit smoking program (e.g., nicotine concentration, flavor, timeline, frequency of use, diet, etc.). For example, by using a cabin identifier to track flavor and other cabin information, the vaporizer system is able to determine and provide recommendations about which flavor profiles, concentrations, vapor consistencies, frequency of use, duration of use, etc. are most suitable for individuals with given personal goals, user profiles, group profiles, past use, age, gender, etc. If the user deviates from the quit smoking program, the vaporizer system can be configured to provide recommendations for resuming the quit smoking program (e.g., counseling, community participation, groups, products, etc.). Figures 50 to 54 An exemplary user interface for depicting different data related to smoking cessation metrics on a dashboard is shown.

[0371] In some aspects, the aggregated smoking cessation information can be combined with machine learning algorithms to provide improved recommendations based on user interactions and / or feedback received from other users, vaporizer devices, applications, websites, reviews, etc.

[0372] The vaporizer device can be configured to provide an "access feature" to registered application users for account login with or without age verification. The vaporizer device can be configured so that access feature availability can be linked to the application and / or user login rather than to a specific user device. In some embodiments, a user device using a device application with a specific user logged into a user account can unlock / lock a specific device that was previously locked by that user using another instance of the device application.

[0373] The vaporizer device can be configured so that the access function can operate on the user device without Wi-Fi, LTE, or other internet connectivity. The access function can respond to the device being within Bluetooth Low Energy (BLE) range of the user device and the user currently logged into the user account. In such an embodiment, a request to an external server may not be required to unlock or lock the vaporizer device from the application.

[0374] In some embodiments of the current subject matter, pairing, locking, and / or unlocking a vaporizer device can be accessed only by logging into an application linked to a user account for the vaporizer device. The vaporizer device can be configured to automatically lock after an extended period of inactivity with the user's device and / or application. For example, if the vaporizer device does not connect to the paired application within a set window (e.g., 1 second, 24 hours, 7 days, and / or other duration), the vaporizer device can automatically lock to prevent unauthorized use of a lost or stolen vaporizer device.

[0375] The vaporizer device may be configured so that the lockout feature can persist across power events. Configuration and status data for such features must be maintained in the vaporizer device's non-volatile memory to survive power-on reset (POR) and / or other reset conditions.

[0376] The vaporizer device can be configured so that the locked device cannot be factory reset (lock hold feature), and an indication can be provided to the user that the vaporizer device is locked. For example, if a user attempts to "factory reset" a locked vaporizer device, the vaporizer device can display a "locked" LED indication without resetting.

[0377] The vaporizer device can be configured so that the lock-retention feature includes sufficient security to prevent hackers from defeating the lock functionality. In some embodiments of the current subject matter, a shared private key is required to lock / unlock the vaporizer device. The shared private key can be generated by the application and transmitted to the vaporizer device during a lock request. To unlock the device, the application can be configured to provide a challenge-response authorization to the vaporizer device using the private key to initiate the unlock sequence.

[0378] The vaporizer device can be configured to authorize the permitted vaporizer device to link to a different user device owned by the same user account holder. For example, if a user loses their user device, the user can log into the application on their new user device and connect the vaporizer device to the new user device. For a vaporizer device that was previously paired with another user device and associated with the user account holder, the vaporizer device can be paired with the new user device in response to the user credentials of the application being identical to the user credentials used to pair the vaporizer device on the previously paired user device.

[0379] The vaporizer device can be configured so that an authorized user does not have to "handshake" (e.g., perform an electronic handshake communication exchange) with the same user device logged into the same user account after first pairing and / or linking to the user account. For example, when the vaporizer device is linked to a user account (with or without age verification), the vaporizer device can "remember" the pairing until it is unlinked from the user account. User credentials can be stored on the vaporizer device so that linked application information is retained.

[0380] The vaporizer device can be linked and authorized (e.g., bound to an account, with or without age verification), such that a specific set of features can be provided to the user based on the authorization and / or linking. The vaporizer device can be configured so that an authorized and authenticated device can be linked and a specific set (full set) of features can be provided to the user via the application.

[0381] The vaporizer device can be configured so that authorized ownership prohibits a vaporizer device owned by another account holder from being linked to another account without the device owner explicitly releasing the vaporizer device from the original account, thereby making theft more difficult by communicating that the vaporizer device is paired to another account user. For a vaporizer device previously paired with another user device and associated with a user account, the vaporizer device can only be paired with the new user device in response to the user credentials of the application being the same as those used to pair the vaporizer device on the previously paired user device. In some embodiments, in response to the vaporizer device being paired with a first user account and / or first user device, the vaporizer device can be configured so that it cannot be paired with a second user account and / or second user device.

[0382] The vaporizer device can be configured to authorize ownership. For example, if a user attempts to link a vaporizer device paired with a first user account to a second user account, the user interface can be configured to display the name of the vaporizer device and / or the second user (e.g., the user accidentally swapped with a friend).

[0383] The vaporizer device can be configured to communicatively connect to one user device at a time. For example, the vaporizer device can only pair and bind to a single Bluetooth central user device, so that subsequent pairing and binding overrides the previous connection.

[0384] The vaporizer device may be configured to pair with a Bluetooth central user device when locked, such that the vaporizer device may be unlocked by any Bluetooth central user device logged into the user account.

[0385] The vaporizer device can be configured so that a user who links a vaporizer device can only link a specified number of vaporizer devices per time period to prevent underage abuse (e.g., device blocking for teens). For example, matching e-commerce regulations may limit the linking of a maximum of five devices per 90-day period (e-commerce purchase restrictions). The application can be configured to communicate a date after which the user can link another vaporizer device.

[0386] The vaporizer device may be configured for "shake to pair" for initial pairing of the vaporizer device with a user account (to prevent other vaporizer devices within range from pairing). The vaporizer device may provide an indication that it has been shaken and is ready to pair.

[0387] The vaporizer device can be configured so that counterfeit vaporizer devices may not be able to connect to the app and / or cloud during the initial pairing process with the user device. The app can be configured to verify that the vaporizer device is not a counterfeit device before allowing the vaporizer device to be linked to the user account and / or providing any app services (e.g., firmware updates). Such a process can utilize industry-standard security procedures to ensure that the service is secure and unhackable.

[0388] The vaporizer device can be configured so that genuine vaporizer devices can take steps to pair and connect only to genuine manufacturer apps and clouds to ensure security. The vaporizer device can be configured to independently verify that the connected app and / or cloud is provided by the manufacturer and not a third-party service to prevent fraud and other unauthorized activity. Such a process can utilize industry-standard security procedures to ensure that the service is secure and unhackable.

[0389] The vaporizer device may be configured so that the first pairing (of a non-associated device) and user device linking must occur when the application has internet access. Internet access may be required to verify a genuine (as opposed to a counterfeit) vaporizer device.

[0390] The vaporizer device can be configured so that the user can pair additional devices to their account ("add device") under restrictions (e.g., x number of devices within a certain length y period of time). The app can be configured to verify such criteria and provide a verification (or not) notification.

[0391] Unless the device is locked, the vaporizer device can be configured for a "factory reset." A factory reset may include resetting the vaporizer device to a new factory state, including clearing the logbook, and resetting the "research mode" of data collection to "standard mode." If a reset gesture is attempted while the vaporizer device is locked (for example, if the pod is removed and / or inserted), the vaporizer device may be configured so that the LED displays a "locked" indication. The user must first unlock the device to enable a factory reset. Gestures for a factory reset may include orienting the device vertically (so that the pod is pointing upward), removing the pod, orienting the device (so that the end of the pod is pointing downward), inserting the pod, removing the pod a second time, orienting the device so that the end of the pod is pointing upward, reinserting the pod, and the like.

[0392] The vaporizer device can be configured so that if a user loses a locked device and releases it from their user account, then finds it again, they can reconnect the device by logging into their user account to resume use. If the device is lost in a locked state and an attempt is made to re-pair it with the account it was originally associated with, the device may function normally and the link to that account may be restored. If re-pairing is attempted with a different account, the device may remain locked.

[0393] The vaporizer device can be configured so that a device that is not yet associated with an account (even if it has been unauthorizedly linked to a user device) can be re-paired and bound with any user device and any user account, so that the device can be repaired and bound to the application without imposing an ownership structure on the link until the device is connected to the vaporizer device user account.

[0394] In some embodiments, a vaporizer device that is not yet linked to another user account can be paired and bound to the user device and the application without requiring the user to log into the application (e.g., for a new vaporizer device where the user has not yet logged in or authenticated). However, the application can be configured to provide a simplified set of functionality until the user logs in using an existing user account or creates a new user account.

[0395] In some embodiments, a user may be able to unlink a vaporizer device from an associated user account (e.g., if the user wants to discard the vaporizer device or has lost it). In one embodiment, a new user of the vaporizer device can see the data (e.g., usage data) of the previous user. The vaporizer device associated with an account can be released ("unlinked") from the user account both when in range and when out of range via the app. The vaporizer device can be configured to restore factory settings, including unlocking the vaporizer device if it is "locked," and clearing the logs but maintaining the latest firmware in response to an attempt to re-pair the vaporizer device to the app.

[0396] The vaporizer device can be configured such that, in response to the vaporizer device's firmware (main / operating image) being overwritten / updated, the vaporizer device may not function properly (e.g., may not produce vapor). A static LED pattern (or other indication) can be provided to alert the user that the vaporizer device is being updated. In some embodiments of the current subject matter, basic vaporizer device functionality can be suspended in response to the firmware being loaded into the microcontroller memory. A static LED pattern (or other indication) can be displayed during the update state to alert the user that the vaporizer device is operating and updating its firmware.

[0397] To prevent device firmware updates from interfering with data logging, the full log can be downloaded and deleted from the vaporizer device before the firmware update occurs. The vaporizer device can be configured so that if the connection to the peripheral device fails (e.g., the device goes out of range, the application crashes, or the user device is restarted), the firmware update can be resumed from the point where it was stopped in response to the user device reconnecting within a threshold time period (e.g., within five minutes).

[0398] The vaporizer device can be configured to implement image verification safeguards (or other protections) to ensure that when newly updated firmware is run on the vaporizer device, a failsafe is in place that is configured to revert to the previous firmware in response to a failure of the new firmware. The vaporizer device can implement a failsafe firmware image bootloader that can verify the integrity of the image so that before booting the new image, the old image can be retained as a failsafe backup until the new image is successfully booted. The bootloader can be configured to implement mechanisms for determining whether the firmware image has been successfully booted (e.g., a watchdog timer, a reset counter, and other means can be utilized to mitigate undesirable behavior and vaporizer device blocking).

[0399] The vaporizer devices can be configured for background firmware updates, such that a server initiates seamless, autonomous (e.g., does not require user intervention to initiate) firmware updates to maintain updated firmware across connected vaporizer devices. The vaporizer device firmware can be automatically updated (without user knowledge or intervention) such that firmware updates are systematically pushed to users to ensure new features are pushed to the vaporizer devices to fix critical bugs and / or test new features.

[0400] In some embodiments of the current subject matter, the vaporizer device can be configured for background firmware updates, such that the vaporizer device must wait until 60 minutes of inactivity (another time period) has passed before initiating the firmware update, thereby ensuring that the process is as non-disruptive as possible. During the inactivity period, new vaporizer device firmware can be pushed to the vaporizer device and verified, and the main firmware boot image can be updated. Inactivity can be defined by events such as the vaporizer device or all vaporizer devices being charged / on a charger, inactivity for a certain period of time, specific times of day, and extended periods of inactivity. Firmware transfer can be determined based on proper connectivity with the user device.

[0401] The vaporizer device can be configured for background firmware updates, such that normal vaporizer device behavior can be interrupted while the firmware download and update occurs. In some embodiments of the current subject matter, the update process can take 1-5 minutes. During a background firmware update, if motion is detected or if the vaporizer device is removed from the charger, the vaporizer device can display an LED pattern (or other indication) to notify the user that the firmware is being updated and normal functionality is unavailable.

[0402] In some embodiments, the vaporizer device firmware update can be configured to provide an immediate update in response to the availability of a firmware update. This update can be displayed on the "Home" screen of the vaporizer device application user interface. The application can be configured to enable the user to "Update Now" and / or obtain information about the nature of the update. In some embodiments of the current subject matter, a "top of page" reminder for the currently selected vaporizer device can be displayed on the application's home screen, configured to update the vaporizer device firmware upon the user selecting an "Update Firmware Now" option. Some embodiments of the current subject matter can include an overlay (e.g., with a gray background) where the user can "Update" or "Cancel" the firmware update. In response to a user's "Cancel" command, the "Update Firmware" reminder can be displayed at the top of the page, while allowing other application features to continue functioning. A "Learn More" option can be provided to provide the user with information about the update. In response to selecting "Update Now," the vaporizer device firmware update page flow can be presented. In some embodiments, the vaporizer device can be configured to alert the user when the installed firmware version is out of date. The user can select an option via the user interface to automatically update the vaporizer device firmware (e.g., to enable automatic firmware updates).

[0403] The vaporizer device can be configured to prevent file corruption during the firmware download process (which could cause the vaporizer device to malfunction) and verify the image signature to ensure that the firmware image is not corrupted during the download process. The integrity of the downloaded firmware image must be verified to ensure that the vaporizer device does not run corrupted (e.g., malicious or otherwise) firmware. Algorithms such as the Elliptic Curve Digital Signature Algorithm (ECDSA) can be utilized to ensure that this feature is mathematically unbreakable.

[0404] In some embodiments, the vaporizer device can be configured for firmware updates, allowing for new firmware to be immediately applied to the vaporizer device at certain times, thereby overriding normal vaporizer device functionality to ensure proper operation of the vaporizer device. Such updates can typically be used during the vaporizer device's connection (to a user device and / or application) and can be used for critical firmware updates. The vaporizer device can support a mode in which a firmware image is downloaded and the main image is updated immediately upon receiving a command. In this immediate update mode, all other vaporizer device functionality is overridden by the update process. Subsequently, firmware can be downloaded from the user device and / or application, and an update to the main image can occur.

[0405] In some embodiments, the vaporizer device can be configured such that during an immediate firmware update, if a problem occurs (e.g., connection to the vaporizer device is lost, connection to the internet is lost, etc.), the application can communicate the error or problem to the user and automatically cancel the update and return to the previous vaporizer device state and application user interface.

[0406] In some embodiments, the vaporizer device can be configured so that the immediate firmware update process can occur as quickly as possible to ensure a positive user experience (e.g., forcing the image download and main firmware swap process to be fully executed in <3 minutes or <1 minute).

[0407] In some embodiments, the vaporizer device can be configured so that during an immediate firmware update, the application provides a progress / status bar estimating the time remaining to complete the update. In some embodiments of the current subject matter, user confirmation is required before initiation. The estimated image download time and micro-estimated refresh time can be closely mapped to the actual download time through pre-processing, past history, testing, aggregated data from other devices, etc.

[0408] In some embodiments, the vaporizer device can be configured for master image swapping to facilitate testing different firmware versions on the same vaporizer device and / or updating the master firmware to a different image recognizer based on a command received from a Bluetooth central user device. If more than one image is stored on the vaporizer device (internal and / or external flash memory), a method can allow the Bluetooth central user device to initiate an update to a given firmware image stored in one of the vaporizer device's non-volatile memory areas.

[0409] In some embodiments, to prevent the vaporizer device from becoming stuck during a firmware update (particularly when swapping old and new firmware), the vaporizer device's battery must be at a minimum state of charge before the running firmware is updated. In some embodiments of the current subject matter, when updating the running image with a newly downloaded image, the vaporizer device's battery strength must be greater than 25% (or other percentage) or connected to a charger, which can be confirmed by the user device and / or the firmware. In some embodiments of the current subject matter, to prevent the vaporizer device from becoming stuck during the firmware update process, the user device's battery must be at a minimum state of charge before the running firmware is updated. During an immediate firmware update, the user device's battery must be charged to 25% or connected to a charger.

[0410] The vaporizer device can be configured with strong security measures in place to prevent the vaporizer device firmware from being accessed and / or read by external parties. For example, all local images can be stored in an encrypted format. In some embodiments of the current subject matter, implementation must pass a National Cybersecurity Center (NCC) and / or other security audit. The vaporizer device and / or cartridge can include a 256-bit private key within an encryption chip to achieve military-grade security.

[0411] In some embodiments, usage data can be tied to a user account so that if the user logs into the application on a different user device (or logs out and then logs back in), the data is retained. Usage data may include one or more of: vapor experience, goal data (e.g., from user settings, new user onboarding process), guided puff results, location history, and / or other usage data.

[0412] In some embodiments, if a user deletes the associated user account, all data associated with the user must be irrevocably unlinked from the user's account in an irreversible manner in accordance with the General Data Protection Regulation (GDPR). The user application can be configured to unlink user data, provide user data upon user request (e.g., via CSV, etc.), and provide the user with a terms and conditions page.

[0413] In some embodiments, a user can perform age verification from one of multiple application locations, resulting in an associated update to the application's feature set. The application's "Account Settings" page may display the "Verified Age" for the user's country (or other geographic region) and may include other information associated with the user and / or accounts associated with the user. In response to the age verification update, enabled features may include checkout, vaporizer device replacement, external web pages, mobile sites, and / or other features. Checkout, vaporizer device replacement, and other features may require age verification. Age verification may be accessed from one or more of checkout (e.g., shopping), the account menu, the vaporizer device replacement process, login, internet connection, and / or other application features. The user's age verification status may be reflected in the account settings. The application may provide the age verification status and the country for which verification is applicable. The user may be provided with the option to perform age verification from within the application. In response to an unverified request, an external mobile web page may be provided.

[0414] In some embodiments, the age verification process may include verification using a database service. In some embodiments, personal user information such as a social security number, driver's license, ID card, credit history, facial recognition, etc. may be used to verify the user's age. In some embodiments, two-factor authentication may be used to verify the user's name and phone number (e.g., receiving a code via text message). Other age verification procedures may include a "passport" feature. For example, a user may create an authorized use identification via the user interface of the user device. When the vaporizer device leaves the vicinity of the associated user device, the vaporizer device may be configured to disable functionality. The functionality may be re-enabled in response to returning to within a threshold proximity of the associated user device. In some embodiments, the vaporizer device may be configured so that the vaporizer device remains enabled in response to exceeding a threshold proximity to the user device for a limited duration (e.g., the vaporizer device may be locked once a given time period has expired).

[0415] In some embodiments, the vaporizer device can be configured to require activation via a user interface of a user device prior to use. In some embodiments, the vaporizer device can be configured for immediate use upon purchase, without requiring activation by pairing with a user device for a limited duration. For example, the vaporizer device can be used by the user for a period of time (e.g., a day, a week, a month, and / or other duration) or usage (e.g., ten puffs, a cartridge, and / or other usage) after purchase, but the vaporizer device can be configured to lock (e.g., disable functionality) in response to a threshold time period and / or usage expiration if the user fails to register via the user interface. As described in further detail below, registration can include a user age verification process.

[0416] Figures 55 to 69 An exemplary user interface is shown that may appear in an application installed on a communication device that communicates with a vaporizer (eg, as part of an "app" or other software on a user's mobile device). Figures 55 to 69 The user interface of the vaporizer includes an age verification feature that can provide benefits in terms of providing data and vaporizer-specific controls for preventing unauthorized and / or underage use, purchase, etc. of the vaporizer. In one embodiment, the vaporizer can be configured to activate functionality only after an age verification process is successfully completed via the user interface. In another embodiment, the vaporizer can be configured to disable itself in response to failure to complete the age verification process within a threshold duration after purchase.

[0417] Can be used Figure 55The vaporizer user may be prompted to implement the device's age verification feature through an application screen view or similar method. In one example, the user may be prompted to enter the age verification process by consenting to the age verification. Alternatively, the vaporizer may be configured to disable the feature in response to the user "opting out" of the age verification process and / or falling below a threshold age. The threshold age may be based on consumer laws in the user's geographic region and / or other considerations.

[0418] Figures 56 to 59 The screen view shows a view that may be presented to the user when selecting and agreeing to the age verification feature. This screen may prompt the user to enter personal user information (e.g., user name and phone number). In some embodiments, other user information may be required, such as a social security number, driver's license, ID card, credit history, and facial recognition. In response to the user entering the user information, the age verification feature may be configured to verify the user's age using one or more authentication methods. For example, two-factor authentication may be used to verify the user's name and phone number (e.g., receiving a code via text message). The user may then receive an authentication message containing a unique or "one-time use" numeric and / or alphanumeric security code, such as Figure 60 shown.

[0419] like Figure 61 and Figure 62 As shown, the user can be prompted to enter the security code they received. Once the user enters the security code, they can use Figure 55 The user information may be verified using one or more of a third-party verification system, a user information database, and / or other verification methods. The duration of the verification process may be displayed (e.g., "in one minute" and / or other duration). In response to successful verification of the user information, the user may be logged in via Figure 64 However, if the user information cannot be verified, the Figure 65 The user may be notified through an application screen view or similar method and may be prompted to provide additional user information to continue the age verification process.

[0420] In response to the unauthenticated user continuing the authentication process, Figures 66 to 69 A screen view or similar method may be used to prompt the user to provide user information documents, such as a valid driver's license, state identification card, passport, social security number and / or other information. The application may be configured to access one or more features of the user's device (e.g., a camera feature) to capture, scan, or otherwise record the user's information. In one embodiment, facial recognition may be used to verify and authenticate the photo identification provided by the user. In response to the submission of the user information documents and / or image, Figure 69An application screen view or similar method may be used to communicate that user information is being verified. In some embodiments, an estimated duration of verification time and / or a status bar may be displayed. In response to successful verification of user information, a user may be logged in via Figure 64 The application screen view or similar method to notify the user.

[0421] Once the age verification process has been completed, you can Figure 70 The application screen view or similar method prompts one or more user actions (such as shaking the vaporizer and / or other user input) to configure the vaporizer for activation. Figure 71 As shown, confirmation of activation of the vaporizer device may be provided.

[0422] In some implementations of the current subject matter, in response to a user exiting and returning to an application, such as Figure 72 The screen view shown may be provided. A new user may initiate the age verification process, or a returning verified user may "log in" to their associated user account. The logged in verified user may then access other features of the application, including the pairing process of the vaporizer device with a mobile device or other user device, such as Figure 73 As shown. The application can provide a quick start guide and / or other introductory instructions (e.g., a user manual and / or tutorial configured to familiarize the user with the vaporizer device) to the logged-in authenticated user. As further described herein, additional training and habit management programs can also be provided. In some embodiments, after activation, the device can periodically re-authenticate in the background with little or no action required by the user. For example, the vaporizer may be required to be connected to the user device periodically (e.g., once a week, once every two weeks, and / or other durations).

[0423] Figures 74 to 80 The screen view shows an embodiment of an automatic lockout feature associated with an age verification feature, the automatic lockout feature being configured to disable and enable the vaporizer via a user interface, such as in conjunction with Figures 23 to 30 In some embodiments, an age verification process may be required only in response to inserting a particular cartridge type (eg, a flavor cartridge) into the vaporizer device.

[0424] Figures 81 to 83 One or more age verification methods are described to ensure the appropriate age of the vaporizer device. Figure 81As shown, the first purchase of a device in a store may require one or more of the following actions for age verification and / or device activation: (1) purchasing a disabled device in the store; (2) unboxing and downloading the mobile application; (3) age verification based on public records; (4) activating the vaporizer device by pairing with a user device via Bluetooth and / or other connection; and / or (5) automatic re-authentication of the device. Subsequent purchases of the device in the store may require one or more of the following actions for age verification and / or device activation: (1) purchasing a disabled device in the store; (2) activating the vaporizer device by pairing with a user device via Bluetooth and / or other connection; and / or (3) automatic re-authentication of the device. Purchasing a device online for the first time may require one or more of the following actions for age verification and / or device activation: (1) creating an online account and performing age verification before making the online purchase; (2) receiving the disabled device, unboxing it, and downloading the mobile application; (3) logging into the application using the online account credentials; (4) activating the vaporizer device by pairing it with the user device via Bluetooth and / or other connection; and / or (5) automatically reauthenticating the device.

[0425] like Figure 82A As shown, another embodiment of the age verification method for ensuring age-appropriate use of a vaporizer device may include one or more of the following operations to perform age verification and / or unlocking of the vaporizer device: (1) unboxing the vaporizer device and / or cartridge; (2) downloading an application; (3) age verification; (4) unlocking the vaporizer device by pairing with a user device via Bluetooth and / or other connection; and / or (5) automatically re-authenticating the device. In the age verification method for ensuring age-appropriate use of a vaporizer device, as shown, Figure 82B In yet another embodiment shown, one or more of the following operations may be included for age verification and / or unlocking of the vaporizer device: (1) unboxing the vaporizer device and / or cartridge; (2) reading the provided youth prevention information; (3) downloading the application; (4) performing age verification based on public records; and (5) activating the vaporizer device by pairing with a user device via Bluetooth and / or other connection.

[0426] like Figure 83 As shown, another embodiment of an age verification method for ensuring age-appropriate use of a vaporizer device may include one or more of the following operations for performing age verification via a user interface: (1) providing a welcome screen; (2) providing new user information and prompting for age verification information; (3) verifying the user information through authentication; and / or (4a) providing a notification of successful age verification; or (4b) requiring additional age verification information.

[0427] After a user's age is verified and their associated vaporizer device is unlocked using one or more of the methods described herein, the user may be required to reauthenticate themselves periodically. Reauthentication may be required daily, every specified number of days, every week, every specified number of weeks, every month, every specified number of months, and so on (e.g., based on firmware within the vaporizer device). In some embodiments, the vaporizer device may require reauthentication every two weeks. Reauthentication may be performed using a user device executing a specific application capable of communicating with the vaporizer device, such as those described herein. For example, reauthentication may require the user to periodically electronically pair their vaporizer device with the user device through the application (e.g., via Bluetooth). In some aspects, once the vaporizer device detects that it is no longer paired with the user device, a reauthentication period may begin, which may be restarted each time the vaporizer device detects that it is paired with the user device, which may be restarted regardless of the most recent pairing (e.g., based on a restart of a specific reauthentication process implemented by executing the application), and so on.

[0428] In some embodiments, after a user has been age-verified using one or more of the methods described herein, an application executing on the user device may store credentials for the user indicating that the user is age-verified (e.g., user account information with a specific value for an "age-verified" field associated with the user account). In some embodiments, the credentials may be created as part of a registration process implemented using the application executing on the user device. In some embodiments, after the user's initial account setup and / or age-verification, the user device may receive the credentials, or a portion thereof, from a server. For example, if the user verifies their age using a web browser, a dedicated kiosk, multi-factor authentication (e.g., via email, SMS, etc.), and / or other methods external to the application executing on the user device, a server configured to communicate with the user device may send the credentials, or a portion thereof, to the user device. In some aspects, if the credentials stored on the user device indicate that the user is age-verified, the user may be allowed to (re)authenticate themselves solely for the purpose of unlocking the user device. In some aspects, a device purchased using an age-verified user account may be shipped in an activated state, but may still require (re)authentication within a specified time period.

[0429] In some aspects, a user may be restricted from purchasing a specific number of vaporizer devices and / or cartridges for use with vaporizer devices within a specific time period. For example, in some aspects, a user may be restricted from purchasing more than one, two, three, etc., devices within a month (e.g., a calendar month, or a rolling number based on the last purchase of a vaporizer device). In some aspects, a user may be restricted from purchasing more than ten, fifteen, twenty, etc. sets of cartridges (e.g., each set having two, three, four, five, etc. cartridges) within a month (e.g., a calendar month, or a rolling number based on the last purchase of a set of vaporizer devices). In some embodiments, a user's purchases may be tracked via more than one source. For example, a user's total purchases within a specific time period may be determined based on data received via a user device, a web browser, a kiosk, a retail store (e.g., via a point-of-sale system), an online retailer, a server configured to communicate with one or more of the above. To track a user's total purchases, the user may be required to use an age-verified user account for each purchase.

[0430] To prevent users from creating multiple user accounts, users can be limited to one account for each set of unique credentials (e.g., information that uniquely identifies only one person). To determine whether a set of credentials is unique, the system (e.g., via a server) may require the user to provide a valid name, date of birth, permanent address, and the last four digits of their social security number. This information can be verified by a third party and / or cross-referenced with publicly available records to confirm that the person is of age in their location / jurisdiction. If the user's public records do not match or they do not wish to provide their social security number, the user may be required to upload or swipe (through a card reader) a valid government-issued identifier for compliance checks. In some aspects, users may be required to verify themselves through multi-factor authentication. For example, to create a user account, the user may be required to provide a phone number and then a code sent to that phone number before proceeding. In some aspects, the code can only be sent to the phone if the phone number is known to be associated with a person of legal age to purchase a vaporizer device. In some aspects, the SIM card associated with the phone number can be verified, and the user is only allowed to use the code sent to the phone number if the SIM card is verified (e.g., if the SIM card is associated with the phone number). Additionally or alternatively, the user may be required to upload or swipe (through a card reader) a valid government-issued identifier and scan their face through a facial recognition interface (e.g., provided by executing an application on the user device being used for account creation). To prevent a user from using multiple user accounts from different users, the user may be required to authenticate themselves each time they make a purchase using their user account, e.g., through electronic verification of an identifier (e.g., a driver's license), facial recognition, etc.

[0431] In some embodiments, a self-service terminal or other device can be configured for device activation. For example, the self-service terminal can be configured to receive user input to verify the user's age according to the methods described herein. Once the user passes age verification, the self-service terminal can provide the user with a receipt with a code (e.g., a barcode, QR code, a numerical value, an alphanumeric string, etc.) to present to a store clerk. The clerk can scan or enter the code into a system that indicates what the user can purchase before allowing the store to sell the vaporizer device or cartridge to the user. In some aspects, the self-service terminal can be connected (e.g., physically, electronically, and / or in communication with) to a vending machine having the vaporizer device and / or cartridge. Once the user passes age verification and makes a purchase, the vending machine can dispense the purchased item to the user.

[0432] In some aspects, a vaporizer device stored in a vending machine may be disabled and / or require authentication (e.g., via one or more device pairing methods described herein) before a user can use the vaporizer device. In some aspects, the vaporizer device may not be configured for wireless communication with a user device. Thus, such a vaporizer device may be prevented from being activated based on information stored on the device, such as a register (e.g., a single bit) in the vaporizer device. To activate the device, the user may be required to place the device in an interface that communicates with a self-service terminal. After verifying the user's age and placing the vaporizer device in the interface, the self-service terminal may be configured to change the register value to unlock the device. In some embodiments, the interface may include a cradle and / or cable with an electronic interface capable of communicating with the vaporizer device via an interface built into the vaporizer device (e.g., a USB or other data communication interface, such as one or more pins). Once the device is unlocked, a serial number or other unique identifier, activation date, purchase date, etc. associated with the vaporizer device may be associated with the user's account for tracking purposes. While a self-service terminal is described, any device capable of communicating with the device without wireless communication may be used.

[0433] Activation system for connecting evaporator units

[0434] In some embodiments of the current subject matter, a vaporizer device can be configured to ensure age-appropriate purchase and / or use of the vaporizer device. For example, vaporizer devices distributed to retailers for in-store purchase by consumers can be sold in a locked or disabled state. When a device is first purchased in a store, age verification and / or initial device setup prior to use can be required. An activation system can be provided so that after purchasing the vaporizer device, the user can activate the vaporizer device on-site using the activation system in response to successful completion of a security verification provided by the activation system.

[0435] In some embodiments, an activation system for activating a vaporizer device may be provided, for example, at a retail store. For example, the activation system may be configured to receive input from a user purchasing the vaporizer device and authenticate the user according to one or more of the methods described herein. The activation system may include a user device. The user device may be an electronic self-service terminal, such as a kiosk, tablet, smartphone, personal computer, etc. For example, the user device may be an interactive self-service terminal configured to unlock the vaporizer device for commercial use in response to a qualified user entering user information via a touch screen, trackball, computer keyboard, buttons, and / or other input device configured to communicate with the user device. Alternatively and / or additionally, the activation system may be coupled to and / or integrated with a point-of-sale (POS) system.

[0436] The activation system may include one or more of a user device and a docking station coupled to the user device. The docking station may also be configured to receive a vaporizer device and couple to the vaporizer device, thereby communicatively coupling the vaporizer device and the user device. For example, the docking station may provide a mechanical connection between the vaporizer device and the user device, securing the vaporizer device to at least a portion of the user device (e.g., the periphery of the user device, the front surface of the user device, the back of the user device, etc.). Alternatively and / or additionally, the docking station may provide electrical coupling and / or optical coupling between the vaporizer device and the user device, enabling the vaporizer device and the user device to exchange data signals. For example, the docking station may provide the vaporizer device with direct and / or indirect access to a serial port and / or a parallel port on the user device. Alternatively and / or additionally, the docking station may include an adapter that allows a first type of port on the vaporizer device to couple to a second type of port on the user device.

[0437] The activation system may include security controls incorporated into an application executing on a user device in communication with the docking station and / or vaporizer device. For example, the application executing the security controls on the user device in communication with the docking station and / or vaporizer device may receive an identifier for the vaporizer device and determine whether security settings are included in the user profile or other settings associated with the vaporizer device. A user interface may be presented on a user device, such as a handheld device, tablet computer, laptop computer, desktop computer, interactive kiosk, etc., as part of the activation system running the control logic. The control logic or other software functionality used to provide these features may include a user interface and may provide input / output and analysis capabilities for modulating the operation of the vaporizer device. Examples of first communication hardware for the user device and / or second communication hardware for the vaporizer device are described above. Such features may be used to require user authentication at the user device in communication with the docking station and / or vaporizer device in order to unlock the vaporizer device before use.

[0438] The activation system can be communicatively coupled to the vaporizer device via a wired and / or wireless connection. For example, in some embodiments, the activation system can be configured to transmit a firmware upload from the user device to the vaporizer device when the vaporizer device is coupled to the docking station, which in turn couples the vaporizer device to the user device. The docking station can include a 5-pin connector configured to align with and couple to a 5-pin connector of the vaporizer device to enable communication between the vaporizer device and the docking station and / or user device. In response to a user successfully completing security verification at the user device, the user device can transmit the firmware upload to the vaporizer device, thereby starting or activating the vaporizer device for use by the consumer.

[0439] In some embodiments of the current subject matter, a 5-pin connector of the vaporizer device and / or docking station may include two pins configured for charging and three pins configured for a serial connection. Alternatively and / or additionally, the docking station may include a wired connection configured to couple to one or more ports on the user device, including, for example, a Universal Serial Bus (USB) port (e.g., USB-A, USB-B, USB-C, mini-USB, micro-USB, USB 3, etc.), a lighting connector, etc. According to some exemplary embodiments, instead of and / or in addition to the wired connection, the activation system may be configured to enable the user device to communicatively couple with the vaporizer device via a wireless connection, such as a Bluetooth connection.

[0440] The docking station may include a container. At least one end of the container may be open to receive the vaporizer device, and an opposite end of the container may include a connector (e.g., a 5-pin connector, a USB port, etc.) that couples to a corresponding connector on the vaporizer device. Coupling the vaporizer device to the docking station may include inserting the vaporizer device into the docking station. The docking station may include one or more mechanisms for retaining at least a portion of the vaporizer device within the docking station, including, for example, a snap fit, a friction fit, a magnet, and the like. Furthermore, the docking station may be secured to the user device using one or more of a snap fit connection, an adhesive, and the like.

[0441] In some embodiments of the current subject matter, the connector can be built into a user device, such as a tablet computer case, and / or adhered to the back of the tablet computer. As described in further detail below, the docking station can be configured to maintain coupling with the vaporizer device through magnetic forces, tension, and / or other mechanisms while the vaporizer device is communicating with the user device. For example, the 5-pin connector can include a magnet that is configured to maintain the position of the vaporizer device when the vaporizer device is coupled to the docking station. Alternatively, the docking station can include a spring member configured to retain the vaporizer device. The user can insert the vaporizer device into the docking station, which can provide a stable connection to the user device while the user completes security verification and / or firmware unlocking of the vaporizer device. One or more components of the activation system can be configured to couple with an external power source to provide charging to one or both of the user device and / or the vaporizer device.

[0442] To achieve consistent connection between the evaporator device and the docking station, the docking station may include a spring-loaded contact configuration that can withstand repeated connection between the evaporator device and the docking station. The spring-loaded contact design may include a spring configured to maintain the position of the evaporator device while the evaporator device is received by the docking station. The spring-loaded contact design of the evaporator device and / or the docking station may be configured to provide consistent tension between the evaporator device and the docking station to ensure stable contact and excellent electrical signal integrity between the electrical contact pins of the evaporator device and the electrical contact pins of the docking station.

[0443] Figure 84 A block diagram of an activation system 8400 for a vaporizer device 8402 is shown. The activation system 8400 can include one or more of a user device 8406, a docking station 8404, and / or a vaporizer device 8402. The vaporizer device 8402 can be configured to couple with the docking station 8404. In a first embodiment, coupling can include inserting the vaporizer device 8402 into the docking station 8404 by sliding a connection end of the vaporizer device 8402 from an open end of the docking station 8404 (e.g., a first side of the docking station), as shown. Figures 87A to 87C As shown. The docking station 8404 can use magnetic coupling to hold the evaporator device 8402 in place. In another embodiment, the evaporator device 8402 can be coupled to the docking station 8404 by inserting the connection side of the evaporator device 8402 into the connection side of the docking station 8404. The docking station 8404 can include spring-loaded contacts configured to hold the evaporator device 8402 in place by tension, such that the spring compresses when the evaporator device 8402 is inserted into the docking station 8404. The top end of the evaporator device 8402 can then be inserted (e.g., snapped into place) into the top end of the docking station 8404, as shown. Figures 86A to 86Cshown.

[0444] The docking station 8404 can be configured to couple with a user device 8406. The docking station 8404 can be coupled to the user device 8406 via a wired connection, such as through a USB-C port, or can be wirelessly coupled to the user device 8406, for example, via a Bluetooth connection. The user device 8406 can be configured to transmit power and / or data to the docking station 8404 via a connection 8408. Similarly, the docking station 8404 can be configured to transmit power and / or data to the vaporizer device 8410 via a connection 8410. Power from an external power source can be delivered to one or more of the docking station 8404, the vaporizer device 8402, and / or the user device 8406 via a connection 8412. Figure 85 A process flow diagram 8500 is shown illustrating features of a method consistent with one or more embodiments of the present subject matter. It should be understood that other embodiments may include or exclude certain features. At 8502, a docking station 8404 may be coupled to a user device 8406. At 8504, a vaporizer device 8402 may be inserted into the docking station 8404. At 8506, the user device 8406 may communicate with the vaporizer device 8402. At 8508, the user device 8406 may prompt a user to confirm the user's eligibility (e.g., age verification) to unlock the vaporizer device 8402 and enable use. At 8510, in response to the user successfully completing the eligibility verification, the vaporizer device 8402 may be unlocked for use.

[0445] Figures 86A to 86C An embodiment of a docking station 8604 is shown. The docking station 8604 may include a spring end 8614 and a connection end 8616. The spring end 8614 may be configured to retract to allow insertion of the vaporizer device 8602. The connection end 8616 may include one or more connection terminals configured to align with and couple to one or more connection terminals of the vaporizer device 8602. The docking station 8604 may include a user device attachment 8618 configured to attach to a user device and / or a housing enclosing the user device.

[0446] Figures 87A to 87CAnother embodiment of a docking station 8704 is shown. The vaporizer device 8702 can be configured to slidably couple with the docking station 8704 such that a connection end of the vaporizer device 8702 can slide into an open end 8714 of the docking station 8704. In response to the vaporizer device 8702 being fully inserted into the docking station 8704, one or more connection terminals at the connection end of the vaporizer device 8702 can align and couple with one or more connection terminals of the docking station 8704 at a connection end 8716 of the docking station 8704. The docking station can include a user device attachment 8718 configured to attach to the user device 8706 and / or a housing enclosing the user device 8706.

[0447] Figures 88A to 88D 8804. The activation system 8800 can include a vaporizer device 8802 configured to be inserted into a docking station 8804. The docking station 8804 can be configured to couple with a user device 8806.

[0448] Figures 89A to 89D Rear, front, top, and side perspective views, respectively, of an embodiment of an activation system 8900 consistent with embodiments of the present subject matter are shown. Activation system 8900 can include a vaporizer device 8902 configured to be inserted into a docking station 8904. Docking station 8904 can be configured to couple with a user device 8906.

[0449] Figures 90A to 90D Rear, front, top, and side perspective views, respectively, of an embodiment of an activation system 9000 consistent with embodiments of the present subject matter are shown. The activation system 9000 can include a vaporizer device configured to be inserted into a docking station 9004. The docking station 9004 can be configured to couple with a user device 9006.

[0450] Figures 91A to 91D Rear, front, top, and side perspective views, respectively, of an embodiment of an activation system 9100 consistent with embodiments of the present subject matter are shown. The activation system 9100 can include a vaporizer device 9102 configured to be inserted into a docking station 9104. The docking station 9104 can be configured to couple with a user device 9106.

[0451] Figures 92A to 92D9204. The present invention also provides a perspective view of the activation system 9200. The present invention also provides a perspective view of the activation system 9200. The present invention also provides a perspective view of the activation system 9200. The present invention also provides a perspective view of the activation system 9200.

[0452] Figures 93A to 93D 9304. The activation system 9300 can include a vaporizer device 9302 configured to be inserted into a docking station 9304. The docking station 9304 can be configured to couple with a user device 9306.

[0453] Figures 94A to 94D Rear, front, top, and side perspective views, respectively, of an embodiment of an activation system 9400 consistent with an embodiment of the present subject matter are shown. Activation system 9400 can include a vaporizer device 9402 configured to be inserted into a docking station 9404. Docking station 9404 can be configured to couple with a user device 9406.

[0454] Figure 95 An example of a vaporizer device having a 5-pin connector is shown. Pins 9520 may include a CH_A pin, a SWDIO pin, a TX pin, a RX (SWDCLK) pin, and a CH_B pin. The CH_A pin and the CH_B pin may provide input to a bridge rectifier for reversibly charging the vaporizer device. The TX pin and the RX pin may serve as transmit and receive lines, respectively, for establishing serial communication with the vaporizer device. Figure 95 In the example of the evaporator device shown, the signal on the RX line can be multiplexed with the SWCLK signal. The signal on the SWDIO line and the SWCLK signal can be used to debug the evaporator device. For example, the SWCLK signal can be a clock signal from a host computer that controls the debugging of the evaporator device, while the SWDIO pin can be a bidirectional data pin that communicates input and output data for debugging the evaporator device.

[0455] In some aspects, a user may be allowed to purchase vaporizer devices and / or cartridges exceeding a set limit, but the vaporizer devices and / or cartridges may be retained until the current time period in which the user exceeded the set limit expires. For example, if a user is restricted from purchasing more than two vaporizer devices per month, and the user attempts to purchase a third vaporizer device within the same month (either a calendar month or a rolling month based on the purchase of the first vaporizer device), the vaporizer devices may be retained until the end of the month. At the end of the month, the vaporizer devices may be released to the user (e.g., automatically shipped). Additionally or alternatively, a user may be limited to a number of activations per specified time period (e.g., two activations per month). Activations may be tracked by a server configured to communicate with multiple devices configured for vaporizer device activation (e.g., user devices executing dedicated applications, etc.). In an exemplary embodiment, if a user is restricted from activating more than two vaporizer devices per month, and the user attempts to activate a third vaporizer device within the same month (either a calendar month or a rolling month based on the activation of the first vaporizer device), the device configured for vaporizer device activation may not allow the user to activate the device until the end of the month. The device can notify the user that they have exceeded their activation limit and / or provide the user with information indicating when they will be able to activate the vaporizer device. If the user returns the device, additional activation information can be credited to the user's account within a specific time period.

[0456] In some aspects, in addition to being restricted from purchasing and / or activating a certain number of vaporizer devices per month, a user may also be restricted from purchasing and / or activating a certain number of vaporizer devices per year. For example, a user may be prevented from purchasing and / or activating more than two vaporizer devices per month and more than ten devices per year.

[0457] In some embodiments, when a user purchases or activates a vaporizer device using a user account, a serial number, MAC address, or other unique identifier associated with the vaporizer device, activation date, purchase date, etc., may be associated with the user account for tracking purposes. If a user account is determined to be associated with inappropriate activity (e.g., providing vaporizer devices to minors, shipping vaporizer devices to other jurisdictions, etc.), the user account may be blocked / prevented from making additional purchases or activations.

[0458] Age verification can also be linked to location information to determine whether the user meets an age threshold. For example, the vaporizer and / or application can receive global positioning system (GPS) information to identify the location of the vaporizer and / or application. In some aspects, the age threshold can be based on a geographic location, such as a specific country, state, city, and county. If the age threshold has changed based on the location of the vaporizer and / or application, the vaporizer and / or application can re-authenticate the user based on the updated age threshold. In some aspects, meeting the age verification requirement can additionally or alternatively be based on GPS information. For example, based on the determined GPS location, the user can be prompted to provide a specific document (e.g., a driver's license or passport or just a passport, etc.) that is sufficient for identification for age verification based on the jurisdiction covering the GPS location.

[0459] Performing this multi-factor authentication through proximity detection can reduce the likelihood of underage and / or unauthorized use of vaporizers. Additionally, associating proximity and / or location information with age verification and / or identification information can allow for greater flexibility in preventing vaporizer operation in designated areas.

[0460] The vaporizer device can be configured to receive vaporizer device settings from the user via the application. The vaporizer device settings may include changing the vaporizer device name. The user account can be configured to store the user's vaporizer device settings so that if the user logs into the user account on a new user device, the user's previous settings are retained. The vaporizer device settings retained by the user account may include brightness, lock status, low battery reminder, vaporizer device name, and / or other settings. The user account can be configured to unlink the vaporizer device from the user account. As a non-limiting example, in response to the user selecting "Unlink vaporizer device," a prompt may be provided, such as, "Are you sure you want to unlink <John's device> from your account? The vaporizer device can be reset to factory settings and can be linked to any other user's account." In response to the user selecting "Yes," the vaporizer device can be unlinked. In response to the user selecting "No," unlinking may not remove usage data from the user account, may remove all location data, and / or may remove the vaporizer device from the location feature.

[0461] Additionally, the vaporizer device settings may include the vaporizer device warranty and / or registration status. In response to an unregistered vaporizer device (e.g., when the vaporizer device is not linked to an account because the user is not logged into an account), a warranty registration page may be displayed, providing vaporizer device information and prompting the user to create or log in to a user account. In some embodiments of the current subject matter, the application may be configured to allow the user to create a new account and / or log in to an existing account using existing Google, Facebook, and / or other account login information.

[0462] In some embodiments, the battery level of the vaporizer device can be displayed on the user device without enabling the vaporizer application. For example, a "battery service" can be configured to display the battery level of the vaporizer device as an icon via the user interface of the user device. Such vaporizer device information can be displayed in response to the vaporizer device being within a threshold range of the user device.

[0463] The vaporizer device can be configured to provide a low-battery reminder. For example, a user can select, via a user interface, to receive a push notification in response to the battery reaching a threshold battery level (e.g., 20% battery level). In some embodiments of the current subject matter, the low-battery reminder can be provided by one or more LEDs. The low-battery feature can be provided via a vaporizer device setting in the user interface, which can be accessed from the vaporizer device card (e.g., accessible from a tab on the card). In some embodiments of the current subject matter, the low-battery feature can be enabled in response to an application being enabled on the user device. The user can turn the low-battery reminder feature on or off. In some embodiments of the current subject matter, the low-battery feature can be enabled in response to the vaporizer device being within range of the user device. In some embodiments of the current subject matter, the vaporizer device does not need to be within range to opt in to the low-battery feature; however, the feature can only be enabled on the vaporizer device once the vaporizer device is within range. In response to the vaporizer device being out of range, the low-battery feature can be displayed as disabled in the user interface. In response to a user attempting to enable the low-battery feature for a vaporizer device that is out of range, the user can receive a notification to return to range of the vaporizer device. In some embodiments of the current subject matter, push notifications from the user interface must be enabled on the user device. The user can adjust the notification method of the threshold battery level or low battery level notification feature through the vaporizer device settings of the user interface.

[0464] The vaporizer can perform onboard data collection, data analysis, and / or data transfer methods. As described above, a vaporizer with wired or wireless communication capabilities can interface with digital consumer technology products (e.g., smartphones, tablets, laptops / netbooks / desktop computers), wearable wireless technology (e.g., "smart watches"), and other wearable technology (e.g., Google Glass), or similar devices using programs, software, firmware, GUIs, wireless communications, wired communications, and / or software commonly referred to as applications or "apps." A wired communication connection can be used to interface the vaporizer to the digital consumer technology product for the purpose of transferring and exchanging data back and forth between the vaporizer and the digital consumer technology product (and thus also interfacing with applications running on the digital consumer technology product). A wireless communication connection can be used to interface the vaporizer to the digital consumer technology product for the purpose of transferring and exchanging data back and forth between the vaporizer and a digital wireless interface. The vaporizer can use a wireless interface that includes one or more of an infrared (IR) transmitter, a Bluetooth interface, an 802.11-specified interface, and / or communication with a cellular telephone network to communicate with the consumer technology.

[0465] The vaporizer may include a microcontroller system. The microcontroller system may control the functions of the vaporizer system and / or facilitate the transmission and / or retention of specific data with an external host (e.g., a mobile phone, a computer terminal, etc.) via a wireless (e.g., Bluetooth Low Energy (BLE)) and / or hardwired interface. An antenna system may be used to transmit data to and from the microcontroller system. The software and / or firmware of the microcontroller system may be remotely upgradeable.

[0466] The vaporizer can be configured to perform onboard data collection, data analysis, and / or data transmission. The data can include one or more of puff characteristics, charging events, device health, error events, accelerometer readings, motion detection, and / or other data associated with the vaporizer device. Puff characteristics can include one or more of puff start time, puff length, average power, minimum power, maximum power, rise time, overshoot, deviation from set point, average puff intensity, minimum puff intensity, maximum puff intensity, temperature rise time, vaporizer device orientation, and / or other puff characteristics. For example, average puff intensity can be determined by pressure differential. Charging events can include the use of a battery charger, the age of the charger, and / or the type of charging used (e.g., a stand charger or charging station). Charge flow status can be calculated after a puff and / or in increments. Charge flow status can be determined for a loaded voltage (e.g., when a battery is connected) and / or for an unloaded voltage (e.g., when a battery is not connected). Device health may include one or more of the following: number of puffs per battery charge, resistance baseline, resistance rise time, double taps of the vaporizer device, device orientation, pressure sensor readings, altitude measurements, ambient temperature, and / or other vaporizer device health characteristics. For example, an accelerometer may be used to determine the orientation of the vaporizer device, double taps of the vaporizer device, and / or other data. The vaporizer device may be configured to communicate error events. Error events may include one or more of an accelerometer lock, a pressure sensor error (e.g., "unable to read"), a pressure sensor error (e.g., "bad data"), an LED sensor (e.g., "unable to read / write"), a charger circuit (e.g., "unable to communicate with charger" or "battery failure"), battery fatigue, and / or other error events.

[0467] The vaporizer device can be configured to have sufficient data capacity for key lifecycle status and counters, and to effectively store error data on an incorrect return merchandise authorization (RMA) device without requiring any device or app pairing (e.g., one week of heavy usage) and / or having a meaningful amount of prior usage data available to the user for use with tracking app features (e.g., a minimum of three weeks). The vaporizer device can be configured to collect data regarding overall device lifecycle statistics and error code counters (e.g., total puffs, drops, and / or errors). For example, the vaporizer device can be configured to collect high-density data related to puffs n that are sufficiently detailed for diagnosis (e.g., 7 days x 200 puffs per day = 2,800 for 97% of users). Alternatively and / or additionally, the vaporizer device can be configured to collect lower-density data related to additional puffs m that are sufficient to detect changes and / or patterns in device usage and frequency (e.g., time-stamped usage patterns, puffs, and / or puff sizes) (e.g., three weeks of heavy use days). The vaporizer device may be configured to collect data without interrupting vapor production and / or degrading device performance.

[0468] The vaporizer device can be configured to measure and control the display of daily / weekly / monthly usage via the user interface. The user interface can be configured to display "average puffs per cigarette (or capsule)" based on the user's measurement of inhalations on the vaporizer device. The vaporizer device can be configured to measure and differentiate between small, medium, and / or large inhalations and convert this measurement into a standardized measurement for display to the user (e.g., large inhalation = 2 puffs, small inhalation = 1 / 2 puff, etc.). The user interface can be configured to convert the inhalation unit from "puffs" to another unit. The user interface can be configured to display usage information such as average puffs, puffs per day, peak consumption time, etc.

[0469] The vaporizer device can be configured to prevent flash memory writes from affecting device performance (e.g., erasing and writing the NRF52 internal flash memory causes the device to cease normal operation, with worst-case timing exceeding the puff wait time). The vaporizer device can be configured in a shipping mode, whereby the device enters an ultra-low power sleep mode at the factory to preserve battery life, as a means of archiving the device for out-of-the-box use by most users. The vaporizer device can be configured to wake from the ultra-low power sleep mode in response to the initial insertion of the pod. In response to the initial insertion of the pod, the vaporizer device can be configured to pair with a phone or other user device. For subsequent pairings, the pod must be removed.

[0470] The vaporizer device can be configured to remotely configure the device between different "modes" of data collection and / or storage. Each mode can be categorized by one or more of the type of data collected, the rate at which data is captured and / or stored, the action in response to the device running out of memory, and / or other categories. The mode classifications can enable different data collection for standard device functions and / or research purposes, where data synchronization can occur at a more frequent cadence and different data can be valuable. Research mode can be exited using a standard factory reset. Robust security can prevent accidental entry into research mode, allowing users to enter "research mode" only through explicit action by the manufacturer and / or customer service team (e.g., through an invitation from an authorized research / beta testing team).

[0471] The evaporator device may be configured to enable the evaporator device to remotely update data schema characteristics (the type of data collected and at what frequency) based on the implementation of new features and new understanding of which data is most valuable.

[0472] The vaporizer device can be configured to use "Research Mode" to remotely configure the device into a data collection and / or storage mode suitable for research purposes. "Research Mode" may require the collection of a different set of fields and / or a higher data storage and recording rate, which may be necessary for recording intra-puff data (as opposed to the "per-puff data" required by "Standard Data Mode"). For example, intra-puff recording may include a rate of ~20 Hz per puff. Device data captured in Research Mode can be referenced via the "Device Data: Type" tag.

[0473] Vaporizer devices can be configured to capture a specified data set from a specified user population at a specified rate. Modifying the data collected for this population can be done remotely (by the manufacturer) without requiring a firmware update on the vaporizer device. For example, an update to the data type collected for all devices in a particular batch can occur in response to a problem discovered with that batch of devices. Devices in research mode can be configured to enable users to create "experiments" for a given population of devices. As a non-limiting example, within an experiment, users may be required to: 1. Create or register a participant population / devices in the experiment (which can be based on batches, user geography, user characteristics, etc.); 2. Define the data type and rate at which data will be collected; 3. Define the duration and / or expiration of the experiment; 4. Define where data will be stored, or how data will be tagged to separate experimental data from production data; 5. Define what happens when the device runs out of memory (e.g., whether data is overwritten or the experiment is stopped); 6. Test the experiment on local test devices before a full rollout; and / or 7. Remotely "start" a formal experiment with an audience via a server (e.g., the "cloud").

[0474] The evaporator device can be configured so that the default mode for data collection for the evaporator device is "Standard Mode." Standard Mode can be characterized by a specific set of collected data fields, data storage and / or logging rates, and / or device memory full behavior. Device data captured in this mode can be referenced by the "Device Data: Type" label.

[0475] The vaporizer device can be configured such that, when in a first mode (e.g., standard mode), the device can maintain, without loss, device health data including overall device life statistics and error code counters (e.g., total puffs, drops, errors, etc.), "high density" data associated with the number of recent puffs n that is sufficiently detailed for diagnosis (e.g., 7 days x 200 puffs / day = 2,800 for 97% of users), and "low density" data associated with the number of next most recent puffs m that is detailed enough to detect changes and / or patterns in device usage and frequency (e.g., timestamped usage patterns, puffs, and / or puff sizes). It will be appreciated that the "high density" data and / or the "low density" data can be stored in a circular buffer such that old data can be overwritten by new data when the buffer reaches maximum capacity.

[0476] The vaporizer device can be configured such that, while in a second mode (e.g., research mode), device health data, including overall device life statistics and error code counters (e.g., total puffs, drops, errors), is not lost due to memory limitations, while all other data retention and / or overwriting procedures after reaching the data storage limit can follow the specific requirements of the respective experiment, for example, as specified by the researcher. For example, the experiment can be stopped and the vaporizer device can be returned from the second mode (e.g., research mode) to the first mode (e.g., standard mode). In response to the change in operating mode, data stored on the vaporizer device can be compressed, and older data stored in the circular buffer can be overwritten. The vaporizer device can be configured with strong security and / or other precautions to prevent consumers from accessing certain operating modes (e.g., research mode).

[0477] The evaporator device can be configured with memory to ensure that firmware updates do not affect and / or corrupt any recorded data. For example, the device can require that all recorded data be transferred to the device before updating and / or partitioning data storage areas for recording and / or firmware updates, making it less likely that one process will affect / hinder / corrupt another and allowing for improved testability and / or quality control of each process. Stored data can remain unchanged during firmware updates and gated firmware updates by pushing data to the cloud. During firmware upgrades, memory blocks used for data storage can be lockable to prevent corruption of stored device data and statistics.

[0478] The evaporator device can be configured so that the data storage is designed to ensure that a flash memory area is not burned out (rendered unusable) due to excessive writes to that area. For example, a device with heavy use and heavy synchronization has a service life of 18 months. The data storage must implement wear leveling or other techniques to ensure that specific flash memory areas are not burned out. Flash memory sectors should be wear-leveled and precautions should be taken to ensure that wear is evened out even during repeated write events.

[0479] The vaporizer device can be configured so that data is recorded at all times without interfering with normal device functionality (e.g., vapor production) in all modes. The vaporizer device can also be configured for RMA. For example, if the device is an RMA version, product development / research must be able to extract all existing data from the device (not requiring Bluetooth), regardless of whether the data has been synced to the cloud.

[0480] To maximize the likelihood and / or frequency of usage data uploads, the vaporizer device can be configured to automatically and / or opportunistically upload device data in the background, such that no direct action on the part of the user is required. The vaporizer device can be configured so that data logged to the device is uploaded, such that normal device functionality remains active. The vaporizer device can be configured to upload data from the device in large chunks, as downtime and user device and / or application connectivity permit, until the device data buffer is cleared, connectivity is lost, or a higher priority device function supersedes the data upload.

[0481] The vaporizer device can be configured for streaming (real-time) data upload of certain data types to facilitate features such as guided puff training, usage measurement, and sessions. Streaming data upload can be configured for certain sensor data states (e.g., differential pressure) to facilitate application visualization.

[0482] For even greater user privacy and anonymity, the vaporizer device can be configured so that the advertising beacon data packet identifier is both (1) anonymized for each device associated with each user account and (2) changed so that it is not constant and therefore more easily associable. When enabling / disabling this feature, the advertising payload data should be updated or rolled to a new "code". The vaporizer device can be configured with a peripheral device to broadcast advertising packets (e.g., iBeacon, etc.) for determining the proximity of user devices and / or applications to the device. The frequency of advertising can be balanced with user experience (e.g., how long the user has to wait when searching for the device, the level of accuracy of the GPS location, etc.) and battery consumption. For example, the vaporizer device can be configured to send advertising packets at a frequency that is less than a maximum frequency (e.g., no more than one packet every 5 seconds) and / or greater than a minimum frequency (e.g., at least one packet every 8 seconds).

[0483] The vaporizer device may be configured to maintain a log of the last known connection location(s) (e.g., receipt of an advertising packet) in response to a user logging in and the device being linked to the user's account to provide the user with a point on a map where the device was last “seen.”

[0484] The vaporizer device can be configured with sound location so that when the device is in range and connected to the app (on any user device that is logged in with login credentials), the app can be configured to trigger / sound a buzzer (or provide any other notification) on the device associated with the user account. The vaporizer device can be configured with security to prevent unassociated applications and / or user accounts from triggering the buzzer feature so that the security cannot be cracked by a penetration tester and a secure connection to the device must be required to activate the buzzer.

[0485] The vaporizer device can be configured so that the location feature can be used on the user device without Wi-Fi, LTE, or other connection to the Internet, and can be responsive to the peripheral device being within Bluetooth range of the user device and the application logging into the user account. Such in-range connection and buzzer functionality can be independent of external server requests.

[0486] The vaporizer device can be configured to be located via a user interface map. The user interface can be configured to display the last known location of the vaporizer and the time the vaporizer device was last detected at that location. Vaporizer devices that are out of range can be displayed with a first notification, while vaporizer devices that are in range can be displayed with a second notification. For example, the user interface can provide information about vaporizer devices that are in range as having a different size, color, and / or shape than vaporizer devices that are out of range. Vaporizer devices that are in range can be displayed on the map using a first color and / or graphic. In some embodiments of the present subject matter, a user can zoom in and / or out and navigate around the map. For example, a default location and zoom level of the map can be set so that the vaporizer device of interest is displayed. Alternatively and / or additionally, other information may be provided for the vaporizer device, including: the name of the vaporizer device, the distance of the last connection (0.# or #mi) and the time, displayed as any of the following: - X minutes ago (if < 60 minutes ago) - "Today XX:XX" (if 12:00am - now) - "Yesterday XX:XX" (if yesterday 12am - 11:59pm) - "Day XX:XX" (if < 7 days ago, where day is the day of the week) - MMM DD XX:XX - etc.

[0487] The vaporizer may interface (e.g., communicate) with digital consumer technology products and applications as a way to relay information and data to add additional functionality.

[0488] The vaporizer can be configured to emit a signal in response to a prompt communicated by the user device. The signal can include one or both of an audible signal and a visual signal, such as a sound emitted by a speaker or illumination of a light-emitting diode (LED). For example, an LED disposed on the vaporizer body can illuminate in response to successful pairing of the vaporizer with the user device.

[0489] The evaporator device may include a user interface. By way of non-limiting example, x LEDs may be positioned on one face of the device to provide a user interface. In other embodiments, x white LEDs may be positioned linearly, perpendicular to the long device dimension on the wide surface, evenly spaced and centrally positioned on the end cap near the aluminum body to end cap junction, and / or other placement locations. In addition, the evaporator device may include one or more LEDs of different colors adjacent to one or more of the x LEDs to indicate a lock and / or error code. The evaporator device may be configured to distinguish between the LED side and the non-LED side of the device, for example, the front and back sides of the device (sides with and without LEDs) may be visually distinguished. The evaporator device may be configured so that the LED brightness is sufficient to make the LED visible outdoors in daylight, at midday sunlight. Although certain colors and numbers of LEDs are described herein, other combinations of colors and numbers of LEDs are also within the scope of this application.

[0490] The user interface can be configured to adjust and / or customize vaporizer device settings. For example, a user can adjust LED brightness from a default level via a slider (e.g., a continuous scale). The vaporizer device can be configured such that brightness updates and / or other user customizations of the vaporizer device are applied in real time...

Claims

1. An evaporator system comprising: at least one data processor; and at least one memory storing instructions that, when executed by the at least one data processor, cause the at least one data processor to perform operations comprising: receiving first usage data associated with a first user interacting with a first vaporizer device, wherein the vaporizer system identifies a correlation between a type of capsule, a puff pattern, and a total intake of active ingredient, the puff pattern including timing of individual puffs, frequency of individual puffs, and / or metering of individual puffs; determining a first recommendation for the first user to interact with a first vaporizer device and / or a second vaporizer device based at least on the first usage data, the first recommendation comprising a type of pod and a puffing pattern for the type of pod, the type of pod and the puffing pattern being associated with a lower total active ingredient intake; and In response to a capsule of the type included in the first recommendation being inserted into the first evaporator device and / or the second evaporator device, a temperature of a heater at the first evaporator device and / or the second evaporator device is adjusted according to the puffing pattern included in the first recommendation.

2. The system of claim 1 , wherein the first usage data comprises a flavor of a vaporizable material in a cartridge inserted into the first vaporizer device, a strength of the vaporizable material, an amount of the vaporizable material remaining in the cartridge, a timing of one or more puffs on the first vaporizer device, a strength of the one or more puffs, a duration of the one or more puffs, a frequency of the one or more puffs, a total dose of active ingredient delivered with the one or more puffs, and / or a length of time between two or more consecutive puffs.

3. The system of claim 2, wherein the first usage data further comprises user input indicating a smoothness of vapor puffed by the one or more puffs.

4. The system of claim 3, wherein the user input comprises motion and / or sound associated with a user coughing, tapping the vaporizer device, shaking the vaporizer device, and / or moving the vaporizer device in a particular pattern.

5. The system of any one of claims 2 to 4, wherein the first recommendation comprises the flavor and / or the strength of the vaporizable material based at least on the flavor and / or the strength of the vaporizable material being associated with a lower puff frequency, a lower total dose of active ingredient delivered, and / or a longer length of time between two or more consecutive puffs than another flavor and / or strength of the vaporizable material.

6. The system of any one of claims 2 to 4, wherein the first recommendation comprises the timing of the one or more puffs based at least on the timing of the one or more puffs being associated with a lower puffing frequency, a lower total dose of active ingredient delivered, and / or a longer length of time between two or more puffs than another timing of the one or more puffs.

7. The system according to any one of claims 1 to 4, wherein the at least one data processor is further caused to perform operations comprising: determining that the first user is similar to the second user; and A second recommendation for a second user to interact with a third vaporizer device is determined based at least on the first usage data.

8. The system of claim 7, wherein the first user and the second user are determined to be similar based at least on one or more attributes associated with each of the first user and the second user, and wherein the one or more attributes include demographic information, preferences, and / or smoking cessation goals.

9. The system of claim 8, wherein the first user and the second user are determined to be similar by at least applying a clustering algorithm configured to identify one or more similar user groups based on the one or more attributes associated with each of the first user and the second user.

10. The system of any one of claims 8 to 9, wherein the second recommendation comprises a flavor of a vaporizable material in a cartridge inserted into the third vaporizer device, a strength of the vaporizable material, a timing of one or more puffs on the third vaporizer device, a strength of the one or more puffs, a duration of the one or more puffs, a frequency of the one or more puffs, a total dose of active ingredient delivered with the one or more puffs, and / or a length of time between two or more consecutive puffs.

11. The system according to any one of claims 1 to 4, the first usage data comprising a first type of data having a first sampling rate and a second type of data having a second sampling rate.

12. The system of claim 11 , wherein the at least one data processor is further caused to perform operations comprising: performing sample aggregation to generate one or more data samples having a third sampling rate lower than the first sampling rate and the second sampling rate based on a first plurality of data samples including data of the first type and / or a second plurality of data samples including data of the second type; and The one or more data samples having the third sampling rate are stored in a log.

13. The system of claim 12, wherein the third sampling rate is determined based at least on whether the one or more data samples comprise behavioral data or diagnostic data.

14. The system of any one of claims 12 to 13, wherein the third sampling rate is determined based at least on the first user having a goal of transitioning from combustible cigarettes to the vaporizer device, reducing use of combustible cigarettes, and / or reducing use of the vaporizer device.

15. The system according to claim 11, wherein The at least one data processor is further caused to perform operations comprising: Batch aggregation is performed to generate a metric based on a first plurality of data samples including data of the first type, the metric generated based on the first plurality of data samples collected by a single thread, and the generation of the metric also excluding a second plurality of data samples collected by another thread.

16. The system of claim 15, wherein the metrics include temperature ramp time, observed temperature, deviation from temperature set point, and / or pressure differential.

17. The system according to any one of claims 1 to 4, wherein the at least one data processor is further caused to perform operations comprising: A user interface is generated that is configured to display the first recommendation on a user device associated with the first user.

18. The system of any one of claims 1 to 4, wherein the first recommendation comprises the strength of the vaporizer material in the cartridge inserted into the first vaporizer device, the timing of one or more puffs on the first vaporizer device, the strength of the one or more puffs, the duration of the one or more puffs, the frequency of the one or more puffs, the total dose of active ingredient delivered with the one or more puffs, and / or the length of time between two or more consecutive puffs that deliver the same amount of the active ingredient to the first user as a combustible cigarette consumed by the first user.

19. The system according to any one of claims 1 to 4, wherein: The first usage data is received from a user device coupled to the first vaporizer device.

20. A computer-implemented method comprising: receiving first usage data associated with a first user interacting with a first vaporizer device and identifying a correlation between a type of capsule, a puff pattern, and a total intake of active ingredient, the puff pattern including timing of individual puffs, frequency of individual puffs, and / or metering of individual puffs; determining a first recommendation for the first user to interact with the first vaporizer device and / or the second vaporizer device based at least on the first usage data, the first recommendation comprising a type of pod and a puffing pattern for the type of pod, the type of pod and the puffing pattern being associated with a lower total active ingredient intake; as well as In response to a capsule of the type included in the first recommendation being inserted into the first evaporator device and / or the second evaporator device, a temperature of a heater at the first evaporator device and / or the second evaporator device is adjusted according to the puffing pattern included in the first recommendation.

21. The method of claim 20, wherein the first usage data comprises a flavor of the vaporizable material in the cartridge inserted into the first vaporizer device, a strength of the vaporizable material, an amount of the vaporizable material remaining in the cartridge, a timing of one or more puffs on the first vaporizer device, a strength of the one or more puffs, a duration of the one or more puffs, a frequency of the one or more puffs, a total dose of active ingredient delivered with the one or more puffs, and / or a length of time between two or more consecutive puffs.

22. The method of claim 21 , wherein the first usage data further comprises user input indicating a smoothness of vapor puffed by the one or more puffs.

23. The method of claim 22, wherein the user input comprises motion and / or sound associated with a user coughing, tapping the vaporizer device, shaking the vaporizer device, and / or moving the vaporizer device in a particular pattern.

24. The method of any one of claims 21 to 23, wherein the first recommendation comprises the flavor and / or the strength of the vaporizable material based at least on the flavor and / or the strength of the vaporizable material being associated with a lower frequency of puffs, a lower total dose of active ingredient delivered, and / or a longer length of time between two or more consecutive puffs than another flavor and / or strength of the vaporizable material.

25. The method of any one of claims 21 to 23, wherein the first recommendation comprises the timing of the one or more puffs based at least on the timing of the one or more puffs being associated with a lower puffing frequency, a lower total dose of active ingredient delivered, and / or a longer length of time between two or more puffs than another timing of the one or more puffs.

26. The method according to any one of claims 20 to 23, further comprising: determining that the first user is similar to the second user based at least on one or more attributes associated with each of the first user and the second user, the one or more attributes including demographic information, preferences, and / or smoking cessation goals; as well as A second recommendation for a second user to interact with a third vaporizer device is determined based at least on the first usage data.

27. The method of claim 26, wherein the first user and the second user are determined to be similar by at least applying a clustering algorithm configured to identify one or more similar user groups based on the one or more attributes associated with each of the first user and the second user.

28. The method of any one of claims 20 to 23, wherein the first recommendation is further generated based on a usage pattern of a combustible cigarette, and wherein the usage pattern includes a brand of combustible cigarette, a type of combustible cigarette, and / or an amount of the combustible cigarette consumed by the first user, and wherein the first recommendation includes the strength of a vaporizer material in a cartridge inserted into the first vaporizer device, the timing of one or more puffs on the first vaporizer device, the strength of the one or more puffs, the duration of the one or more puffs, the frequency of the one or more puffs, the total dose of active ingredient delivered with the one or more puffs, and / or the length of time between two or more consecutive puffs that deliver the same amount of the active ingredient to the first user as the combustible cigarette consumed by the first user.

29. A non-transitory computer-readable medium storing instructions that, when executed by at least one data processor, result in operations comprising: receiving usage data associated with a first user interacting with a first vaporizer device and identifying a correlation between a type of capsule, a puff pattern, and / or a total intake of active ingredient, the puff pattern including timing of individual puffs, frequency of individual puffs, and / or metering of individual puffs; determining, based at least on the usage data, a recommendation for at least one of: (i) the first user interacting with the first vaporizer device and / or the second vaporizer device, and (ii) a second user interacting with a third vaporizer device, the recommendation comprising a type of capsule and a puffing pattern for the type of capsule, the type of capsule and the puffing pattern being associated with a lower total active ingredient intake; and In response to the type of pod included in the recommendation being inserted into the first evaporator device, the second evaporator device, and / or the third evaporator device, adjusting a temperature of a heater at the first evaporator device, the second evaporator device, and / or the third evaporator device according to the puff pattern included in the recommendation.

30. An evaporator system comprising: a first evaporator device; a user device communicatively coupled to the first vaporizer device; and A remote server comprising at least one data processor and at least one memory storing instructions, the instructions, when executed by the at least one data processor, causing the at least one data processor to perform operations comprising: receiving, from the user device, usage data associated with a first user interacting with the first vaporizer device, wherein the server identifies a correlation between a type of capsule, a puff pattern, and a total intake of active ingredient, the puff pattern including timing of individual puffs, frequency of individual puffs, and / or metering of individual puffs; determining, based at least on the usage data, a recommendation for at least one of: (i) the first user interacting with the first vaporizer device and / or the second vaporizer device, and (ii) a second user interacting with a third vaporizer device, the recommendation comprising a type of capsule and a puffing pattern for the type of capsule, the type of capsule and the puffing pattern being associated with a lower total active ingredient intake; as well as In response to the type of pod included in the recommendation being inserted into the first evaporator device, the second evaporator device, and / or the third evaporator device, adjusting a temperature of a heater at the first evaporator device, the second evaporator device, and / or the third evaporator device according to the puff pattern included in the recommendation.

31. An evaporator device comprising: means for receiving, from a user device, usage data associated with a first user interacting with a first vaporizer device, wherein the device identifies a correlation between a type of capsule, a puff pattern, and a total intake of active ingredient, the puff pattern including timing of individual puffs, frequency of individual puffs, and / or metering of individual puffs; means for determining, based at least on the usage data, a recommendation for at least one of: (i) the first user interacting with the first vaporizer device and / or the second vaporizer device, and (ii) a second user interacting with a third vaporizer device, the recommendation comprising a type of capsule and a puffing pattern for the type of capsule, the type of capsule and the puffing pattern being associated with a lower total active ingredient intake; and In response to a pod of the type included in the recommendation being inserted into the first, second, and / or third evaporator devices, the response includes adjusting a temperature of a heater at the first, second, and / or third evaporator devices according to the puff pattern included in the recommendation.

Images