RU2825126C2 - Evaporator controls - Google Patents

Abstract

FIELD: evaporators; evaporative systems.

SUBSTANCE: evaporators and evaporative systems may include a user device that maintains communication with the evaporator, may include one or more features related to the control of the functions and/or features of the evaporator. A method is provided for blocking the evaporator. The method includes determining whether or not the evaporator is located within the communication range of the second device. The method additionally includes blocking the evaporator in response to the presence of the evaporator within the mentioned communication range. The method additionally includes receiving information associated with the user of the evaporator. The method additionally includes determining, based on the received information, the age of the user and unblocking, by means of one or more processors and based on the age of the user satisfying the threshold value, the evaporator in order to activate the operation of the evaporator.

EFFECT: activate the evaporator operation.

13 cl, 39 dwg

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Provisional Patent Application No. 62/609,289, filed December 21, 2017, entitled "Vaporizer Device Locking," and U.S. Provisional Patent Application No. 62/690,947, filed June 27, 2018, entitled "Connected Vaporizer Device Systems," and U.S. Provisional Patent Application No. 62/745,959, filed October 15, 2018, entitled "Vaporizer Device Locking," and U.S. Provisional Patent Application No. 62/760,918, filed November 13, 2018, entitled "Connected Vaporizer Device Systems," the disclosures of which are incorporated herein by reference in their entirety.

Field of technology to which the invention relates

[0002] The equipment, devices, systems and methods described herein relate to vaporizing devices, such as electronic vaporizers, and to methods of using, controlling and/or verifying the authorized use, manufacture, etc. of such devices.

State of the art

[0003] Vaporizing devices, which may also be referred to as electronic vaporizing devices, electronic cigarettes, or e-cigarettes, or simply as "vaporizing devices," may be used to deliver a vapor containing one or more active ingredients via inhalation of the vapor by a user of the vaporizing device. Electronic vaporizing devices are becoming increasingly popular for use in prescription medical applications, drug delivery, and for the use of tobacco and other plant-based smoking materials. Among other technical difficulties associated with vaporizing devices, underage or other unauthorized use of such devices may pose a wide range of problems. Preventing such use may present many challenges.

The essence of the invention

[0004] Aspects of the present invention relate to controlling the operation (e.g., one or more settings or operating parameters) of an evaporator.

[0005] Some aspects relate to computer-implemented methods for operating an evaporator. Such methods include determining, by one or more processors, whether or not the evaporator is within the communication range of a second device, and blocking or unblocking the evaporator in response to the evaporator being within said communication range. The method further includes receiving, by one or more processors, information associated with a user of the evaporator. The method further includes determining, by one or more processors and based on the received information, the age of the user. The method further includes unblocking, by one or more processors and based on the age of the user satisfying a threshold, the evaporator to activate the operation of the evaporator.

[0006] In another aspect, an evaporator is provided. The evaporator includes at least one processor. The evaporator further includes at least one memory device storing instructions that, when executed by the at least one processor, instruct the evaporator to at least determine whether or not the evaporator is within the communication range of a second device. The evaporator is further instructed to lock the evaporator to deactivate the operation of the evaporator in response to the evaporator being within said communication range. The evaporator is further instructed to receive information associated with a user of the evaporator; determine, based on the received information, the age of the user. The evaporator is further instructed to unlock, based on the age of the user satisfying a threshold, the evaporator to activate the operation of the evaporator.

[0007] Implementations of the present invention may include, but are not limited to, methods according to the descriptions provided herein, as well as articles that contain a tangibly embodied computer-readable medium configured to instruct one or more machines (e.g., computers, etc.) to ultimately perform operations that implement one or more of the described features. Similarly, computer systems are also described that may include one or more processors and one or more memory devices coupled to the one or more processors. The memory device, which may include a non-transitory computer-readable or machine-readable storage medium, may include, encode, store, etc. one or more programs that instruct one or more processors to perform one or more operations described herein. Computer-implemented methods according to one or more implementations of the present invention may be implemented by one or more data processors resident in a single computing system or in a plurality of computing systems. Such a plurality of 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, via a network connection (e.g., via the Internet, a wireless wide area network, a local area network, a wide area network, a wired network, etc.), via a direct connection between one or more of the plurality of computing systems, etc.

[0008] The details of one or more variations of the invention described herein are set forth in the accompanying drawings and in the description below. Other features and advantages of the invention described herein will be apparent from the description and drawings and from the claims. Although certain features of the disclosed present invention are described by way of illustration with respect to electronic vaporizer devices, it should be readily understood that such features are not intended to be limiting. The claims that follow this disclosure are intended to define the scope of the protected subject matter of the invention.

Brief description of the drawings

[0009] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate specific aspects of the invention disclosed herein and, together with the description, help to explain certain principles associated with the disclosed implementations. In the drawings:

[0010] Fig. 1 illustrates a block diagram of an evaporator, according to some exemplary implementations;

[0011] Fig. 2A illustrates an exemplary exploded view of the evaporator of Fig. 1, according to some exemplary implementations;

[0012] Fig. 2B illustrates another exemplary view of the evaporator of Fig. 1, in accordance with some exemplary implementations;

[0013] Fig. 2C illustrates another exemplary view of the evaporator of Fig. 1, in accordance with some exemplary implementations;

[0014] Fig. 2D illustrates an exemplary view of the evaporator cartridge of Fig. 1, in accordance with some exemplary implementations;

[0015] Fig. 3 illustrates a block diagram of another evaporator, according to some exemplary implementations;

[0016] Fig. 4A illustrates an exemplary view of the evaporator of Fig. 3, in accordance with some exemplary implementations;

[0017] Fig. 4B illustrates another exemplary view of the evaporator of Fig. 3, in accordance with some exemplary implementations;

[0018] Fig. 5 illustrates a block diagram of a communication-based exchange between an evaporator, a user device, and a server, in accordance with some example implementations;

[0019] Fig. 6 illustrates an example device that may be used to implement one or more of the described features and/or components, in accordance with some example implementations.

[0020] Fig. 7 illustrates a communication diagram between one or more evaporators and a radio beacon, in accordance with some example implementations;

[0021] Fig. 8A illustrates a communication flow chart based on communication between one or more evaporators and a user device, in accordance with some example implementations;

[0022] Fig. 8B illustrates a flow chart of an exemplary method for authenticating a user of an evaporator, in accordance with some exemplary implementations;

[0023] Fig. 9 illustrates a flow chart of an exemplary method for blocking an evaporator, in accordance with some exemplary implementations;

[0024] Figs. 10A-10E illustrate features of exemplary user interfaces for an application that may be used with a vaporizer in accordance with embodiments of the present invention;

[0025] Figs. 11A-11B illustrate features of exemplary user interfaces for an application that may be used with a vaporizer in accordance with embodiments of the present invention;

[0026] Figs. 12A-12J illustrate features of exemplary user interfaces for an application that may be used with a vaporizer in accordance with embodiments of the present invention;

[0027] Figs. 13A-13H illustrate features of exemplary user interfaces for an application that may be used with a vaporizer in accordance with embodiments of the present invention;

[0028] Figs. 14A-14F illustrate features of exemplary user interfaces for an application that may be used with a vaporizer in accordance with embodiments of the present invention;

[0029] Figs. 15A-15E illustrate features of exemplary user interfaces for an application that may be used with a vaporizer in accordance with embodiments of the present invention;

[0030] Figs. 16A-16H illustrate features of exemplary user interfaces for an application that may be used with a vaporizer in accordance with embodiments of the present invention;

[0031] Figs. 17-36 illustrate features of exemplary user interfaces for an application that may be used with a vaporizer in accordance with embodiments of the present invention;

[0032] Fig. 37 illustrates an exemplary method in accordance with embodiments of the present invention;

[0033] Figs. 38A and 38B illustrate example methods in accordance with embodiments of the present invention; and

[0034] Fig. 39 illustrates an exemplary method in accordance with embodiments of the present invention.

[0035] Where appropriate, similar reference numbers designate similar structures, features or elements.

Implementation of the invention

[0036] Management of the use of vaporizing devices, including, for example, the implementation of measures to prevent unauthorized use of such devices, is a key factor from several perspectives. Unsupervised use of a vaporizer by a minor may raise health and regulatory concerns. In addition, because modern commercial vaporizers tend to be quite small and capable of discrete use, the use of such products may occur in locations, such as schools, hospitals, other public spaces, etc., where allowing unsupervised use is either undesirable or potentially in violation of applicable local regulations. In other examples, tampering with parts of the vaporizer, such as consumables (such as refill cartridges, etc.) that contain the substance to be inhaled, can result in poor performance of the vaporizer and can also present health concerns due to the circumvention of quality control approaches regarding the purity of the inhaled substance and/or other components of the consumable that come into contact with the inhaled air. As such, it is desirable to implement approaches that allow one or more of controlling who is allowed to use the vaporizer, controlling where the vaporizer can be used, controlling consumables that can be used with the vaporizer, etc.

[0037] The present invention includes features that can be advantageously used to resolve one or more of these and/or other needs. For example, embodiments of the present invention include methods, devices, equipment, articles and systems related to vaporizing and/or aerosolizing one or more materials for inhalation by a user, and approaches related to creating additional barriers to unauthorized use of such devices and/or consumables applicable with such devices.

[0038] With respect to preventing underage use, traditional vaporizers may rely on third parties to provide age verification at the time of purchase of the vaporizer. For example, a retail store employee may perform some form of age verification (e.g., a visual inspection of a driver's license) to authorize the purchase in a manner that is similar to current approaches to reducing unauthorized/underage use of other substances and/or delivery systems, such as alcoholic beverages, traditional cigarettes, etc. However, with respect to these other substances, authentication that occurs only at the point of sale may prevent the purchaser from providing the purchased product (e.g., a vaporizer, cartridges, or other consumables usable with the vaporizer, etc.) to an unintended party (e.g., an underage teenager), or prevent use by unintended parties when the vaporizer is lost or stolen. It may be desirable to provide additional security, authentication, or protection measures to help reduce or prevent unwanted use or users of the vaporizer. Such approaches may include technical features implemented at one or more of a plurality of stages of the purchase and use cycle for the vaporizer, as described herein.

[0039] With respect to controlling the use of evaporators at a location, controlling the use of evaporators, the inclusion of one or more communication features on the evaporator may be advantageous, such as in association with one or more features described herein.

[0040] Additionally, since multiple vaporizer devices, cartridges, or other consumables and other age-controlled substances may be resold or otherwise transferred to a new user after age-controlled purchase, it may also or alternatively be necessary to implement one or more approaches to correlate geographic clusters of unauthorized use with locations in which unauthorized sales may occur.

[0041] Various embodiments of the present invention may be used in combination with one or more of a plurality of vaporizers and/or vaporizer systems. The term "evaporator" is used generically in the description herein and in the claims such that it means any of a stand-alone piece of equipment, equipment that includes two or more separable parts (e.g., a vaporizer body that includes a battery and/or other hardware, and a cartridge that includes and/or is configured to hold a vaporizable material), and the like. A "evaporation system" as used herein may include one or more components, such as a device that communicates (e.g., wirelessly or via a wired connection) with the vaporizer, and optionally also the vaporizer itself. The vaporizer or one or more components of the vaporizer system according to embodiments of the present invention may be configured to be controlled and operated by users. As used herein, "aerosol" may mean a vapor (e.g., molecules in the gas phase of one or more substances) and/or particles (e.g., condensed droplets, solid particles, etc.) entrained in a volume of air.

[0042] Examples of vaporizers according to embodiments of the present invention include electronic vaporizers, electronic cigarettes (electronic cigarette), electronic cigarettes (e-cigarette), and the like. In general, such vaporizers are handheld devices that heat (by convection, conduction, radiation, or some combination of the above) a vaporizable material to provide an inhalable dose of the material. The vaporizable material used with the vaporizer may be provided within a cartridge (e.g., in a portion of the vaporizer that contains the vaporizable material in a reservoir or other container, and which can be replenished when empty or disposed of in favor of a new cartridge containing additional vaporizable material of the same or different type). The vaporizer may be a cartridge-based vaporizer, a cartridge-less vaporizer, or a universal vaporizer that can be used with or without a cartridge. For example, a universal vaporizer may include a heating chamber (e.g., a furnace) 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 implementations, the vaporizer may be configured to be used with a liquid vaporizable material (e.g., with a carrier solution in which the active and/or inactive ingredient(s) are suspended or held in a solution or liquid form of the directly vaporizable material) or with a solid vaporizable material. The solid vaporizable material may include plant material that releases some portion of the plant material as the vaporizable material (e.g., so that some portion of the plant material remains as waste after the vaporizable material is released for inhalation by the user), or may optionally be a solid form of the directly vaporizable material such that all of the solid material can ultimately vaporize for inhalation. The liquid vaporizable material may similarly be capable of being completely vaporized or may include some portion of the liquid material that remains after all of the material suitable for inhalation has been consumed. In certain examples, the vaporizable material may be or include one or more of a tobacco material, a marijuana-based material, a botanical material, and the like. In certain examples, the vaporizable material is or includes nicotine, a nicotine derivative, a nicotine salt, and the like. Alternatively or additionally, the vaporizable material may be or include one or more of a nutraceutical, a cannabinoid, a medicinal compound, and the like.

[0043] According to some embodiments of the present invention, the evaporator and/or evaporation system may be configured to identify the evaporable material to be evaporated and to control the operation of the evaporator accordingly. For example, the vaporizer may be configured to receive a cartridge or other pre-loaded container holding a vaporizable material (e.g., a vaporizable material such as a solution of nicotine, marijuana, and/or another active ingredient) and identify and/or determine information regarding the vaporizable material and/or the cartridge or other pre-loaded container, such as one or more of the following: a type of vaporizable material, a concentration of the vaporizable material in a solution or other impure form of the vaporizable material contained in a reservoir or other container of the cartridge, an amount (e.g., mass, volume, etc.) of the vaporizable material in the reservoir or other container of the cartridge, a configuration of the cartridge (e.g., what specific components or types of components, such as the power or configuration of a heater, one or more electrical properties, etc., are present in the cartridge), a lot number of the cartridge, a date of manufacture of the cartridge, an expiration date after which the cartridge should not be used, a date of manufacture or filling of the cartridge, etc.

[0044] An evaporator, according to embodiments of the present invention, may be configured to be connected (e.g., connected wirelessly or via a wired connection) to a communication device (or optionally devices) that communicates with the evaporator. Such a device may be a component of an evaporation system, as explained herein, and may include first communication hardware that can establish a wireless communication channel with second communication hardware of the evaporator. For example, a device used as part of the evaporation system may include a general-purpose computing device (e.g., a smartphone, a tablet computer, a personal computer, some other portable device such as a smart watch, etc.) that executes software to generate a user interface to present an opportunity for a user of the device to interact with the evaporator. In other embodiments of the present invention, such a device used as part of the evaporation system may be a dedicated piece of hardware, such as a remote control or other wireless or wired device, having one or more physical or software (e.g., configurable on a screen or other display device and selectable through user interaction with a touch screen or some other input device, such as a mouse, pointer, trackball, cursor buttons, etc.) interface controls. Although the term "device" is used herein, the term "equipment" is intended and should be construed as such.

[0045] A device that is a part of the vaporizer system defined herein may be used for any one or more functions such as dosing management (e.g., monitoring doses, setting doses, limiting doses, tracking users, etc.), session management (e.g., monitoring session status, setting sessions, limiting sessions, tracking users, etc.), obtaining location information (e.g., locations of other users, locations of retail/commercial establishments, vaping locations, relative or absolute location of the vaporizer itself, etc.), personalizing the vaporizer (e.g., assigning a name to the vaporizer, locking/password protecting the vaporizer, adjusting one or more parental controls, associating the vaporizer with a group of users, registering the vaporizer with a manufacturer or warranty service organization, etc.), engaging in entertainment with other users (e.g., communicating via social media, interacting with one or more groups, etc.), and the like. The terms "session organization", "session", "vaporizer operation session" or "steam consumption session" are used generically in the description and claims below to mean a period devoted to the use of the vaporizer. The period may include a period of time, a number of doses, an amount of vaporized material, etc.

[0046] In some embodiments of the present invention, the vaporizer may include functionality for communicating with a cartridge containing a material to be vaporized. The vaporizer may also communicate with a device that is part of the vaporization system, although this is not required. The vaporizer, under control of or otherwise communicating with a device that is part of the vaporization system, or as a stand-alone unit separate from the vaporization system, may be configured such that the operation of the vaporizer can be modified, controlled, etc. based on one or more parameters that are received from the cartridge, or accessed from a database or other information source based on the identification of the cartridge.

[0047] For example, an evaporator in accordance with embodiments of the present invention may be configured to recognize a cartridge and output (and in some cases transmit) or otherwise receive information regarding the cartridge. In other words, a computing element, such as a controller, etc., that is associated with the body of the evaporator may receive information regarding the cartridge through some form of data exchange. Many methods for recognizing cartridges by the evaporator are within the scope of the present invention, including the methods described in more detail below. Any of the approaches described herein may be performed with or without the addition of wireless communication/connectivity, also described herein, although such wireless connection as described herein may be advantageously employed as described in more detail below.

[0048] Embodiments of the present invention also include methods of using an evaporator and/or evaporation system for functions such as determining and/or controlling a dose, volume, etc. of one or more chemical species of vaporized material or of the vaporized material itself.

[0049] Fig. 1 illustrates a block diagram of an evaporator 100, according to some example implementations. As illustrated, the evaporator 100 in Fig. 1 includes an evaporator body 101. The evaporator body 101 may include a housing that houses a power source 103 (e.g., a device or system that stores electrical energy for use on demand), which may be a battery, a capacitor, a combination of the above, etc. and which may be rechargeable or non-rechargeable. The housing may also house a controller 105, which may include a processor. In the examples shown, a cartridge 114 may be attached to, in, or partially in the evaporator body 101.

[0050] Fig. 2A illustrates an example evaporator 100 that may include the features indicated in Fig. 1. As illustrated in Fig. 2A, the evaporator 100 may include an evaporator body 101 and a cartridge 114 that is separable from the evaporator body 101. Fig. 2B and Fig. 2C, respectively, illustrate front and side plan views of the example evaporator 100 of Fig. 2A. Fig. 2D illustrates an example view of the cartridge 114 of Fig. 2A separable from the evaporator body 101. In some implementations, the cartridge 114 may retain and/or is configured to retain a liquid vaporizable material. For example, when the vaporizer includes a cartridge (e.g., cartridge 114), the cartridge 114 may include one or more reservoirs 120 of and/or for vaporizable material. Any suitable vaporizable material may be contained in the reservoir 120 of the cartridge 114, including solutions of nicotine or other organic materials.

[0051] Although the exemplary evaporator shown in Figs. 2A-2D includes a cartridge 114 that is inserted into the evaporator body 101, other evaporator configurations are within the scope of the present invention. For example, evaporators with/without cartridges are applicable with the present invention. For evaporators that include the use of cartridges, such cartridges may be consumable (e.g., disposed of after the volume of vaporizable material provided is used up) or reusable (e.g., allowing for refilling with vaporizable material).

[0052] The processor of the controller 105 may include a circuit for controlling the operation of the heater 118, which may optionally include one or more heating elements for vaporizing the vaporizable material contained in the cartridge 114, for example, in a reservoir or container that forms part of the cartridge 114. In various implementations, the heater 118 may be present in the body 101 of the vaporizer or in the cartridge 114 (as shown in Fig. 1) or in both. The controller circuit may include one or more clock generators (oscillators), a charging circuit, input/output controllers, a memory device, etc. Alternatively or in addition, the controller circuit may include a circuit for one or more wireless communication modes, including Bluetooth, near field communication (NFC), Wi-Fi, ultrasound, ZigBee, RFID, etc. The evaporator body 101 may also include a memory device 125, which may form part of the controller 105 or otherwise support data exchange with the controller. The memory device 125 may include a volatile (e.g., random access memory) and/or non-volatile (e.g., read-only memory, flash memory, semiconductor data storage device, hard disk, other magnetic data storage device, etc.) memory device or data storage device.

[0053] Further referring to Fig. 1, the evaporator 100 may include a charger 133 (and a charging circuit that may be controlled by the controller 105), optionally including an inductive charger and/or a pluggable external charger. For example, a connection according to the universal serial bus (USB) standard may be used to charge the evaporator 100 and/or provide the ability to communicate via a wired connection between the computing device and the controller 105. The charger 133 may charge the built-in power source 103. The evaporator 100 according to embodiments of the present invention may also include one or more inputs 117, such as buttons, dials, etc. and/or sensors 137, including accelerometers or other motion sensors, capacitive sensors, flow sensors, etc. These sensors 137 can be used by the evaporator 100 to detect the processing and interaction of users. For example, the detection of a rapid movement (for example, a shaking motion) of the evaporator 100 can be interpreted by the controller 105 (for example, by receiving a signal from one or more sensors 137) as a user command to begin communication with a user device that forms part of the evaporation system, and which can be used to control one or more operations and/or parameters of the evaporator 100, as described in more detail below. Additionally or alternatively, the detection of a rapid movement (for example, a shaking motion) of the evaporator 100 can be interpreted by the controller 105 (for example, by receiving a signal from one or more sensors 137) as a user command to cycle through a plurality of temperature settings according to which the vaporizable material held in the cartridge 114 is to be heated by operation of the heater 118. In some optional variations, the detection of the removal of the cartridge 114 by the controller 105 (for example, by receiving a signal from one or more sensors 137) during the cycling through the plurality of temperature settings can operate with the ability to set the temperature (for example, when the cycle is performed at the desired temperature, the user can remove the cartridge 114 to set the desired temperature). The cartridge 114 can then be re-engaged with the evaporator body 101 by the user to allow the evaporator 100 to be used with the heater controlled by the controller 105 in accordance with the selected temperature setting. A plurality of temperature settings can be indicated via one or more indicators on the evaporator body 101.

[0054] The evaporator in accordance with embodiments of the present invention may also include one or more terminals 115. Terminals 115, as used herein, may refer to any of optical (e.g., LEDs, displays, etc.), tactile (e.g., vibration, etc.), or audible (e.g., piezoelectric, etc.) feedback components, etc., or some combination thereof.

[0055] The evaporator 100, according to embodiments of the present invention that include a cartridge 114, may include one or more electrical contacts (such as the electrical contacts 109, 111, 113 shown in Fig. 1) on or in the evaporator body 101 that can engage mating contacts 119, 121, 123 (e.g., pins or sockets) on the cartridge 114 when the cartridge is engaged with the evaporator body 101. The contacts on the evaporator body are generally referred to as "evaporator body contacts" and the contacts on the cartridge are generally referred to as "cartridge contacts." These contacts can be used to provide energy from the power source 103 to the heater 118 in embodiments of the present invention in which the heater 118 is included in the cartridge 114. For example, when the cartridge contacts and the evaporator body contacts are respectively engaged by means of a connection of the cartridge 114 to the evaporator body 101, an electrical power supply circuit can be formed to provide the ability to control the flow of power from the power source 103 in the evaporator body 101 to the heater 118 in the cartridge 114. The controller 105 in the evaporator body 101 can regulate this flow of power in order to control the temperature at which the heater 118 heats the evaporable material contained in the cartridge 114.

[0056] Any suitable electrical contact may be used, including pin terminals (e.g., spring pin terminals), plates, and the like. In addition, as described below, in some embodiments of the present invention, one-way or two-way communication is provided between the evaporator body 101 and the cartridge 114 via one or more electrical contacts, which may include electrical contacts used to provide energy from the power source 103 to the heater 118. The cartridge 114 and the evaporator body 101 may be removably connected to each other, for example, by engaging a portion of the cartridge housing 114 with the evaporator body 101 and/or the evaporator housing due to a mechanical connection (e.g., a latch and/or a friction fit), and the like. Alternatively or additionally, the cartridge 114 and the evaporator housing 101 may be connected magnetically or through some other connecting or engaging mechanism. In other words, the connection of the cartridge to the evaporator may be achieved by any of a variety of possible approaches, including, but not limited to, a magnetic connection, a friction fit connection, a threaded connection, a snap-on or snap-on connection, etc.

[0057] Any of the cartridges described in this document may include one or more identifiers 138. The identifier 138 may be recognized, detected, and/or read by the evaporator body 101 and may communicate information regarding the vaporizable material contained in the cartridge and/or regarding the cartridge 114 itself. The identifier 138 may include a readable and/or read/write cartridge memory. The identifier 138 may include a circuit for receiving and/or communicating information between the cartridge 114 and the evaporator body 101. For example, the data communication circuit may include a cartridge memory that stores information (e.g., data indicative of one or more parameters of the cartridge), and additional circuit that forms a data communication circuit, together with another circuit on the evaporator body 101, when the cartridge 114 is connected to the evaporator body 101.

[0058] In some embodiments of the present invention, the identifier 138 is passive and may include codes or markings (e.g., bar codes, quick response (QR) codes, etc.). In some examples, the identifier 138 may be structural (e.g., one or more pins, protrusions, etc.) on the cartridge 114, which may be detected by the evaporator body 101. Visual or mechanical identifiers may be identified directly by the evaporator body 101 using an imaging device (e.g., a camera, etc.) or a reading device (e.g., an optical reader) integrated into the evaporator body (not shown in Fig. 1), or through communication via a separate device, such as a smartphone. For example, the user can take an image of the identifier 138 (for example, a code, a marking, etc.) and transmit the code or information extracted from the code (for example, information regarding the vaporized material and/or the cartridge) to the body 101 of the evaporator via the wireless circuit 107 or optionally via a wired connection. The wireless connection (for example, a wireless communication channel) can be established between the first communication hardware of the device equipment and the second communication hardware of the evaporator. The first and second communication hardware, respectively, can include transceivers for use with one or more wireless communication protocols, non-limiting examples of which are described in this document.

[0059] Fig. 3 shows a schematic diagram of an evaporator 200 that does not use a cartridge (but may still optionally accept a cartridge), and may instead use a tear-off material. The evaporator 200 of Fig. 3 may include a loose evaporable material that may be placed in a furnace 220 (e.g., in an evaporation chamber). Many of the identical elements present in the evaporator 100 using a cartridge 114 shown in Fig. 1 and Fig. 2A-D may also be included as part of the evaporator 200 that does not use cartridges. For example, the evaporator 200 without a cartridge may include an evaporator body 201 with a control circuit 205, which may include a power control circuit and/or a wireless circuit 207 and/or a memory device 225. The power source 203 (for example, a battery, a capacitor, etc.) can be charged by means of a charger 233 (and may include a charge control circuit, not shown). The evaporator 200 may also include one or more terminals 215 and one or more inputs 217 with sensors 237. In addition, the evaporator 200 may include one or more heaters 218, which heat the furnace 220 or another heating chamber. The heater 218 may be controlled using the resistance of the heater 218 to determine the temperature of the heater, for example, by using the temperature coefficient of the specific resistance for the heater. A mouthpiece 244 may also be included.

[0060] Fig. 4A shows a side perspective view of an exemplary evaporator 200 with an evaporator body 201. In the bottom perspective view of Fig. 4b, the cover 230 is shown removed from the evaporator body 201, which makes the furnace/evaporator chamber 220 visible.

[0061] Fig. 5 shows a schematic representation of communication between the vaporizer 100, 200, the digital device 305 that communicates wirelessly with the vaporizer 100, 200, and the remote server 307 that can communicate directly with the vaporizer 100, 200 or through the digital device 305. The digital device 305 can be a handheld mobile device such as a smartphone, smart watch, tablet computer, etc., or a desktop or portable computing device. As noted herein, the digital device 305 may not necessarily be a dedicated remote control device.

[0062] In general, as schematically illustrated in Fig. 5, the evaporator 100, 200 can remotely communicate with a remote server 307 and/or a digital device 305, such as a wearable electronic device (e.g., Google Glass, smart watch, smart clothing, etc.) and/or a smartphone, smart watch, etc. Thus, the evaporator can include a communication interface (wireless circuit 107, 207), which can be implemented through a communication chip (e.g., second communication hardware) in/on the evaporator. Exemplary wireless chips may include, but are not limited to, a Bluetooth chip such as the Parani BCD 210 or the CC2650 Bluetooth Single-Chip Solution from Texas Instruments (TI) CC2650, an NFC-enabled chip (such as the QCA1990 from Qualcomm) that provides NFC communication or enhanced Wi-Fi or Bluetooth communication, wherein NFC is used to establish a communication link. As described and explained with respect to examples herein, one or more of these wireless circuits may be used to communicate with/between the cartridge 114 in implementations that are configured to read the cartridge 114, as schematically shown in Fig. 1. For example, NFC may be used to read the identifier 138 (as an RFID tag) on the cartridge 114.

[0063] The wireless communication chip may include a Wi-Fi enabled chip, such as TI's SimpleLink CC3000, which can connect the evaporator to Wi-Fi networks. In some implementations, the wireless circuit comprises a subscriber identity module (SIM) card in the evaporator housing, a nano-SIM card, etc. (e.g., providing 3G/4G cellular network communication capability). Alternative forms of communication may be used to establish two-way communication between the evaporator 100, 200 and the user device 305.

[0064] The connection between the vaporizer 100, 200 and the user device 305 may be automatic (e.g., after initial setup) or may alternatively be initiated by the user through various settings, through user interaction with the vaporizer itself (e.g., by shaking the vaporizer, quickly touching the vaporizer, pressing one or more buttons on the vaporizer, etc.).

[0065] Vaporizers, vaporizer systems, and methods for using them to customize the vaporizer and use active substances (e.g., nicotine, other drugs, etc.) based on activity patterns are also within the scope of the present invention. The vaporizer and/or vaporizer system as currently described may provide the ability for the user to personalize the vaporizer, among other possible communication-related features.

[0066] The vaporizer and/or vaporizer system according to embodiments of the present invention may be configured to facilitate interaction in the form of communication through the vaporizer. For example, the vaporizer may be configured to share usage information with others, such as third parties (e.g., healthcare providers, including physicians, attorneys specializing in reducing consumption, etc.) to better prescribe and implement treatment. The vaporizer and/or vaporizer system may also be configured to exchange data with third parties that are not healthcare providers (e.g., friends, colleagues, etc.) and with unknown third parties (which results in some or all of the information becoming publicly available). In some implementations, the vaporizers described herein, either alone or in communication with one or more communication devices that are part of the vaporizer system, may identify and provide information regarding the operation, status, or user input from the vaporizer to a public or private network. In some implementations of the present invention, the vaporizer and/or the vaporizer system may be configured to provide one or more interactive user interfaces for use by a user and/or multiple users of different (or identical) vaporizers. Interaction via the user interface(s) may be tied to operation of the vaporizer and/or user manipulation of the vaporizer (e.g., based on accelerometer output, touch or lip recognition, puff detection, etc.).

[0067] The vaporizer and/or vaporizer system in accordance with embodiments of the present invention may also be configured to provide location information, possibly including one or more information regarding the location of the user in proximity to one or more of the following: other users (known or unknown users, specified or unspecified users, etc.), retailers, specific locations (cocktail bars, clubs, locations with permission to use vaporizers), etc. The vaporizer and/or vaporizer system may also be configured to facilitate placing orders based on the use or operation of the vaporizer and/or vaporizer system.

[0068] The vaporizer may include GPS capabilities or may access GPS information from another device (e.g., user device 305) in communication with the vaporizer as part of an evaporation system.

[0069] In certain embodiments of the present invention, an evaporator that includes a cartridge may be configured to recognize and/or identify the cartridge, which optionally includes, but is not limited to, features regarding the cartridge and/or its contents. One or more recognition/identification based approaches may be used to enable a vaporizer (e.g., a controller, microprocessor, etc. that is part of the body of the vaporizer) to determine information regarding a cartridge and/or a vaporizable material retained in the cartridge, such as one or more of the following: the type of material being vaporized (e.g., nicotine, marijuana-derived material, flavors, whether the vaporizable material is pure, in the form of a solution, is a solid or liquid, a detachable or other plant-containing material, etc.), the concentration of the material being vaporized (e.g., in a carrier solution containing one or more of propylene glycol, vegetable glycerin or other solvents, etc.), the amount or volume of the material being vaporized, the configuration of the cartridge (e.g., heater properties, electrical properties, etc.), the lot number of the cartridge, the date of manufacture of the cartridge, the expiration date of the cartridge, information for verifying the source and/or authenticity of the cartridge, and etc.

[0070] This information may be directly encoded on the cartridge, or a reference indicator may be provided which the evaporator (or a processor in communication with the evaporator) can use as an index to look up some or all of this information, or a combination of a reference number and directly encoded material may be provided.

[0071] In some embodiments of the present invention, the cartridge may be recognized and/or identified by engagement between the cartridge and the evaporator. In some embodiments of the present invention, the cartridge may be configured to include a manipulated interaction with the evaporator. For example, the shape or size of some portion of the cartridge may be detected by the evaporator (so that different variations in size, shape, etc. may indicate certain features of the cartridge and/or its contents). In addition, or in addition, the cartridge may include n pin terminals or projections that may be detected when the cartridge is inserted or otherwise connected to the body of the evaporator (e.g., by completing an electrical connection). For the n pin terminals, 2 ⁿ possible combinations of markings are provided, each of which may indicate a feature or a combination of features of the cartridge and/or its contents.

[0072] In further optional variations, the cartridge may be configured or identified based on an electrical property that the evaporator may detect based on an electrical connection with the cartridge. For example, an electrical circuit may be completed by a combination of cartridges and an evaporator body by mating two or more pairs of electrical contacts (e.g., at the side of each pair on the cartridge and a corresponding contact on the evaporator body) such that a heater or other component of the cartridge is part of the completed circuit. One or more parameters of the heater or other component of the cartridge, such as, for example, a characteristic impedance, inductance, time response, etc. (e.g., a time constant, an RC time constant, an LC resonance, etc.), may be detectable after the circuit is completed. These one or more parameters may indicate a feature or a combination of features of the cartridge and/or its contents.

[0073] In some embodiments of the present invention, the cartridge may be recognized and/or identified by markings on the cartridge identified by the evaporator. These markings may or may not be visible to the user. For example, the cartridge may be marked by characteristic ultraviolet, infrared, or other wavelength-specific ink that can be detected by the evaporator, which may include, for example, an emitter/detector pair specific to the marker(s). For example, the markings may include an infrared scannable barcode located on the cartridge. In some embodiments, the markings may be a pattern, such as a QR code, a barcode, etc., that indicates information regarding the cartridge and/or the contents (evaporable material) of the cartridge. The markings may be symbolic, including alphanumeric. The markings may be "read" or detected directly by the vaporizer, which may include a camera or other optical detector, or they may be indirectly detected through communication with a second device (e.g., a wearable device, a smartphone, etc.) having a camera, etc. For example, the markings on the cartridge may be detected by the user device 305 (e.g., via a camera or other sensor that is part of or is otherwise controlled to provide input to the user device 305). For example, a smartphone acting as the user device 305 may identify a marking captured as an image via the smartphone camera using an application (e.g., software) on the smartphone to look up one or more properties from a lookup table, or it may directly transmit the marking to the vaporizer, which may look up the properties, and/or it may communicate with a remote server, which may look up the properties and transmit them to the vaporizer directly or via the smartphone.

[0074] In some embodiments of the present invention, the cartridge may be recognized by RFID (radio frequency identification) technology. RFID tags are used in a wide variety of inventory control applications. Some RFID technologies use active devices that contain their own power source, and others use passive RFID devices that interact with another device with a power supply that causes data transfer without relying on the power in the passive device. For example, a cartridge may include one or more RFID chips or components that can be detected and read by a reader in the evaporator to identify and receive information about the cartridge.

[0075] In some embodiments of the present invention, the cartridge may be recognized and/or identified by communicating with a memory device (e.g., EEPROM) on the cartridge via an electrical connection to the evaporator. In embodiments in which a heater is present on the cartridge, such as the exemplary evaporator shown in Fig. 1, it may be advantageous to use one or more electrical connections on the cartridge (e.g., contacts 119, 121, 123) that are also used to supply power and/or control the heater in such a way as to communicate with the memory device. This may be particularly complex when the cartridge may engage with the evaporator in more than one orientation, and/or when the heater is controlled via this identical contact, and modulation of the applied/received electrical signals between the cartridge and the evaporator may modify the control and/or determination of the temperature of the heater. One or more additional electrical contacts may be used in addition to the electrical contacts controlling the heater. In general, the communication between the cartridge and the vaporizer may be one-way (e.g., reading information regarding the cartridge and/or the vaporized material from the cartridge via the vaporizer), or it may be two-way (e.g., reading information regarding the cartridge and/or the vaporized material and recording information regarding the operation of the device, such as the number of uses, the duration of use, the temperature settings, etc.). The information may be recorded in the cartridge, and this information may be used to retrieve other information regarding the cartridge, including the amount of material remaining in the cartridge, etc.

[0076] In general, any of the vaporizers described herein can estimate, measure, and/or predict the amount of vapor and/or material (including active ingredients) in the vapor that can be delivered to the user. For example, as explained in detail below, the equipment described herein can be used to determine and/or control the dosing of the vaporized material. For example, the present invention includes vaporizers and methods of using such vaporizers to accurately and controllably deliver doses of an active ingredient in a vaporized material (e.g., nicotine, marijuana, and any other active ingredient/drug) based on user-specified needs, medical needs, needs for switching to e-cigarettes, or needs for quitting. Dose management may include displaying dosing information per use, per session (e.g., multiple uses over a predetermined period of time, such as 1-15 minutes, 1-30 minutes, over 1-60 minutes, 1-90 minutes, 1-120 minutes, etc.), per day, or over another predetermined and/or user-defined period of time. Dose management may also include monitoring dosing (e.g., the volume of one or more active ingredients delivered by the equipment). The dosing control may also or alternatively include controlling the operation of the vaporizer based on the volume of one or more active ingredients delivered by the equipment over time, which includes warning the user when a predetermined (user-defined, factory-set, or third-party-set) value or threshold is gradually reached (e.g., within 50%, 75%, 80%, 85%, 90%, 95%, 98%, 99%, etc. of the predetermined value) or exceeded, and/or stopping (locking, disabling, etc.) the equipment when the predetermined threshold is met or exceeded. The equipment that includes the dosing (dose) control may include internal logic (circuitry and/or programming, including application-specific integrated circuit (ASIC) logic) for dosing control and/or may communicate with an external processor (via a wireless communication link) that performs all or part of the dose control.

[0077] Information regarding the cartridge and/or the vaporizable material retained in the cartridge, optionally including one or more types of information described above, may be particularly useful in quantifying the dose of vaporizable material delivered to the user. In some embodiments of the present invention, the dose and/or usage information may be stored (recorded) on the cartridge (e.g., in a memory device); for example, based on a calculation of the amount of vaporizable material delivered, data may be written to the cartridge, and/or the data may be stored on a server and associated with a specific cartridge such that reconnection of the cartridge to an identical or different vaporizer body results in the vaporizer body being able to detect how much of the vaporizable material has previously been dispensed from the cartridge.

[0078] Additional technologies through which the vaporizer may implement recognition and/or communication with the cartridges include the use of a marker (e.g., a QR code, an IR or US marker, etc.), mechanical and/or electronic manipulation, and the like. In general, and as noted elsewhere herein, the electronic communication between the cartridge and the vaporizer may include unidirectional or, in some implementations, bidirectional (including duplexed or multiplexed) communication of information such that information may be received by the vaporizer from the cartridge, and optionally information may be written to the cartridge by the vaporizer. The information provided to the vaporizer may include information regarding the material being vaporized and/or the cartridge, such as the information discussed elsewhere herein.

[0079] A cartridge that includes an identification circuit (also referred to herein as a cartridge identification circuit) may be configured to communicate and transfer this information from the cartridge to the evaporator. The cartridge identification circuit may include a memory device (e.g., EEPROM). In variations of cartridges in which a heater (e.g., a resistive heating element, such as a resistive coil or wire) is controlled by applying power to one or more (e.g., 2, 3, 4, etc.) electrical contacts of the heater that communicate with corresponding contacts in the evaporator, the cartridge identification circuit may communicate with the evaporator through identical electrical contacts of the heater, despite increased complexity and potential for heater failure.

[0080] The cartridge identification circuit may also have a configuration in which the cartridge can be inserted into the evaporator in multiple orientations without disrupting the operation of the cartridge identification circuit.

[0081] The identical cartridge identification scheme may also be recorded with information regarding the cartridge, the material being evaporated, and the cartridge history, including, for example, the time of use and/or the total energy applied, etc.

[0082] The information stored in the memory device (readable and/or writable) may be encoded, which includes the use of encryption, error correction encoding (e.g., Hamming code, etc.), etc. In operation, when the cartridge is first inserted into the body of the evaporator, the microcontroller of the evaporator may be configured to first determine whether or not a signal encoding information regarding the cartridge and/or identifying the cartridge as compatible with the evaporator can be read from the cartridge. The information may be read using the sensing circuit of the evaporator. In some implementations, even when the cartridge may not be readable (e.g., may not include a cartridge identification circuit or is unable to read from the cartridge identification circuit), the evaporator may use a default setting.

[0083] During operation, the vaporizer may periodically (e.g., after each puff, etc.) write to a memory device in the cartridge identification circuit, if detected. The vaporizer may transmit in service signals to the memory device a request to read from the memory device, similar to how the device writes to the memory device, and then may disconnect the battery voltage applied to the heater contacts to allow the memory device (e.g., EEPROM) to gain control over the I/O line and use it to output data representing a digital output (toggle the I/O line between a low and a high level), a transmit output that the vaporizer detects through the resistance measurement circuit. Typically, if the memory device performs a transfer, this may affect the absolute accuracy of temperature control; the vaporizer may be configured such that the device does not heat up when the memory device performs a transfer (output), and normal heating operation may not trigger the memory device for data transfer.

[0084] As described in more detail below, information stored in the memory of the cartridge identification circuit, such as the information described herein, may be useful for dose management (e.g., calculating and storing dosing information), as well as for security, communication, and storage of operating parameters, particularly in devices that include wireless communication capabilities. However, cartridge identification may be useful even in the absence of wireless communication capabilities.

[0085] As explained, the memory device (e.g., EEPROM) can store information regarding the vaporizable material and/or the cartridge. One example of information that can be stored can include values associated with specific properties of the heating element, such as a nominal R (resistance) of the heater for a cartridge that includes a heating element of the cartridge. This value can be determined and stored at the factory, at the time the device is manufactured/formed, and/or it can be done at a later time. Storing a specific R-value for each cartridge in the memory device affiliated with this cartridge can be useful for precise temperature control for the device, including determining a baseline resistance at ambient temperature, as described herein. Although the resistance measurement/baseline for the production line may be slightly different from the measurement that the device applies for use, a baseline control (determined by the algorithm) can also be used. Alternatively or additionally, once a reliable baseline for a cartridge is determined, that baseline can be associated (e.g. in a remote database, on a remote server, etc.) with an identifier associated with a particular cartridge, so that if the cartridge is removed and reinserted, the identical baseline can also be used (once the cartridge identifier is confirmed), which can represent a faster check than waiting for a stable baseline to be found.

[0086] In general, storing a characteristic of a cartridge, such as the resistance of a heater directly in the cartridge, may also be useful for confirming that the connection between the evaporator and the cartridge is good and that the resistance measurement circuit of the evaporator is working properly. Thus, in any of the methods and equipment described in this document, the nominal resistance of the cartridge may be stored in the memory of the cartridge (or may be stored on a remote server/device and retrieved based on a unique identifier of the cartridge) and may be used to confirm that the connection between the device and the capsule is good and/or that the resistance measurement circuit of the device is working properly and/or that the resistance of the cartridge has not changed since the cartridge was assembled or filled.

[0087] As mentioned herein, in some implementations, the vaporizer may record usage information in the memory of the cartridge; the usage information may be used to estimate the amount of vaporizable material that has been removed from the cartridge and the remaining amount of vaporizable material. The usage information may include the number of puffs/drags, the dosage delivered, etc.

[0088] The vaporizer and/or the vaporizer system may include software, firmware, or hardware that are separate or separable from the vaporizer and that communicate wirelessly with the vaporizer. For example, applications ("applications") may be executed on a processor of a portable and/or wearable user device, including smartphones, tablet computers, smart watches, personal digital devices, etc., which are generally referred to herein as user devices (e.g., user device 305 in Fig. 3), which are part of the vaporizer system. The user device may provide an interface for the user to participate in and interact with functions associated with the vaporizer, including transmitting data to/from the vaporizer to the digital device, etc. and/or to an additional third-party processor (e.g., to servers, such as to server 307 in Fig. 3). For example, the user may control certain aspects of the vaporizer (temperature, dosing, etc.) and/or the transmission of data and the reception of data to/from the vaporizer, optionally via a wireless communication channel between the first communication hardware of the device equipment and the second communication hardware of the vaporizer. The data may be transmitted in response to one or more user actions (e.g., including interactions with a user interface displayed on the device) and/or as a background operation in such a way that the user does not have to initiate or authorize the data exchange process.

[0089] User interfaces may be deployed on a user device and may assist the user in operating the vaporizer. For example, a user interface controlling the user device may include icons and text elements that may inform the user regarding various ways in which the settings of the vaporizer may be adjusted or configured by the user. In this manner (or otherwise in accordance with the present invention), information regarding the vaporizer may be presented using a user interface displayed by the user device. Icons and/or text elements may be provided to allow the user to view information regarding the state of the vaporizer, such as battery information (remaining charge, number of remaining vapor puffs, time for charging, charging process, etc.), cartridge status (e.g., type of cartridge and vaporized material, cartridge fill status, etc.) and similar device status. Icons and/or text elements may be provided to allow the user to update internal software (aka firmware) in the vaporizer. Icons and text elements may be provided to allow the user to set security and/or authorization features of the vaporizer, such as setting a PIN code to activate the vaporizer, or using personal biometric information as an authentication means. Icons and text elements may be provided to allow the user to configure foreground data sharing and related settings.

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

[0091] The authentication process may be implemented as a feature of an application that is installed and executed on a user device capable of exchanging data using wired or wireless methods (e.g., as part of an evaporative system, as described in this document). As noted above, the user device may have an operating system that allows the application(s) to operate. Alternatively, the evaporator may directly include one or more features of the user interface (e.g., for entering a PIN code or some other approach to authentication based on user input, etc.) and/or sensors for implementing fingerprint or iris scanning, facial recognition, etc.

[0092] In some embodiments of the present invention, the vaporizer may be coupled to (e.g., communicate with) an additional (e.g., portable, wearable, smartphone, desktop, handheld, etc.) device that may provide user-programmable dose control, real-time usage monitoring, personalized usage settings, device locking, and social features. For example, the vaporizer and/or vaporizer system may include features related to security controls, including parental controls, user age management/restriction, and anti-theft controls. The vaporizer and/or vaporizer system may include anti-theft and/or authentication features that may lock or otherwise restrict use/operation of the device when the vaporizer is stolen, misplaced, etc., and may also be configured to allow locking (e.g., parental locking) to protect against children or otherwise prevent unauthorized third-party operation.

[0093] In one example, counterfeit protection or another blocking feature of this type may be implemented using cartridge identifiers to prevent the use of counterfeit consumables, such as replaceable cartridges containing an evaporable material. For example, cartridge identifiers from a verified source or supplier may include a hash or some other verification code as part of the identifier, and the vaporizer may block the use of the vaporizer if a cartridge that lacks the necessary hash or verification code is connected to the body of the vaporizer. Such a feature may be used to require input for verification of user identification data into a device communicating with the vaporizer to instruct the device to unblock the use of the vaporizer. In one example, the cartridge may include an identifier that indicates that it contains a controlled substance, and the user may be required, through an application on the device (in response to determining this with respect to the cartridge via identifier information received from the cartridge), to verify his/her identification data (e.g., by entering a password, verifying biometric identification data, etc.), and for the application to verify that the identified user is authorized to use the controlled substance, before being able to use the vaporizer with this cartridge connected to the body of the vaporizer. In another example, a cartridge containing nicotine or marijuana may require verification of user identification data such that the application on the device allows use of the vaporizer only if the user identification data is verified and the user is registered as having an age exceeding a minimum age.

[0094] In some examples, security control may be enabled through an application running on a device communicating with the vaporizer. For example, an application running on a device communicating with the vaporizer may receive an identifier of the vaporizer itself or alternatively/additionally a cartridge, and based on or otherwise using the identifier, may determine whether or not a security setting is included in a user profile or in other settings associated with the vaporizer or cartridge. According to embodiments of the present invention, such functionality may be fully or partially included in the vaporizer (and/or cartridge), or it may be distributed between the vaporizer and a user interface that may be presented on an additional device that forms part of the vaporizer system, such as a wearable and/or handheld device, a laptop computer, a desktop computer, etc., implementing control logic. The control logic or other software functionality for providing these features may include a user interface and may provide input, output and analysis capabilities for modulating the operation of the vaporizer. Non-limiting embodiments for the first communication hardware of the device and/or the second communication hardware of the evaporator are described herein.

[0095] The vaporizer may be configured to switch to a locked or "authentication-required" mode after a period of inactivity exceeding a predetermined (or optionally user-configurable) threshold amount of time. In some examples, this locked mode may be or include a "sleep mode" where no use is detected for a predetermined and/or preset period of time. In some implementations of the present invention, as a necessary prerequisite for activation and thereby being able to be used for vapor generation purposes of the vaporizer, the user must authenticate in order to ensure that the device is being used by the intended user and to thereby delay or prevent unauthorized use or accidental or unintentional activation of the device or use of the device by a person under the age of legal responsibility for consuming an active component including nicotine or marijuana. Authentication based on a personal identification number (PIN) may use a user-selected PIN to authenticate an end use. Biometric authentication may be used, optionally using one or more approaches. For example, a fingerprint-based authentication process may authenticate an end user. An iris-based authentication process may use an eye scan or iris scan, etc., to authenticate an end user. Facial recognition-based authentication may use a facial scanning or image processing algorithm to authenticate an end user. Biometric authentication, including iris scanning, facial recognition, etc., may be particularly useful if the personal digital device has a camera, such as a forward-facing camera or other sensors, capable of such authentication to enable use of the user device.

[0096] The personal vaporizer may be deactivated after threshold criteria are met. For example, the vaporizer may be placed in an inactive state after a period of inactivity. The period of inactivity may be preset and/or selected by the user (e.g., using control software for execution on a personal digital device). Thus, the period of inactivity may be a configurable parameter of the vaporizer. The application software/firmware may include functionality to unlock or activate the vaporizer using authentication as mentioned herein.

[0097] The vaporizer may include a heating element configured to heat the vaporizable material. The application may be configured to disable and/or block the vaporizer by turning off the power supply to and/or using the heating element of the vaporizer. Disabling and/or blocking the vaporizer may be based on authentication and/or verification of the age of the user. Disabling and/or blocking the vaporizer may also be based on the vaporizer being within range of a disabling/blocking signal or a disabling/blocking device (e.g., beacon 705), as discussed below with respect to Figs. 7-9. The control system (e.g., via firmware) may be configured to selectively prohibit the user from activating the heating element in accordance with certain actions (e.g., standard heating). In some aspects, the device may be configured to ignore pressure sensor readings and/or other indications that the user is inhaling on the device. The application may be configured to provide a notification indicating that the vaporizer is functionally disabled and/or locked. Additionally or alternatively, the device may be configured to alert the user that the device is being locked (e.g., using one or more LEDs, a sound, haptic feedback, etc.) upon determining that the user is attempting to puff on the device. In some implementations, the vaporizer may be configured to enable the vaporizer in response to the vaporizer being within a threshold range relative to the user device. In some implementations, the vaporizer may be configured to enable the vaporizer in response to the vaporizer receiving a signal from the user device. In some implementations, the vaporizer may be configured to disable the vaporizer in response to the vaporizer receiving a signal from the user device. For example, the user may lock and/or unlock the vaporizer via user input to the application, such as via fingerprint recognition, facial recognition, etc.

[0098] The vaporizer may be configured to be locked such that key functionality (e.g., vapor generation) is disabled to prevent unauthorized parties from using the locked device. In some implementations, the vaporizer paired with an application or other software may implement a lock/unlock feature such that a given user can lock the device, thereby preventing unauthorized users from unlocking and/or accessing the vaporizer. The lock feature may be configured with strong security (e.g., encryption, firewall, etc.) to prevent the lock functionality from being compromised by hacking.

[0099] The application may be configured to disable and/or block the vaporizer in response to the vaporizer being outside a threshold communication range with the user device. For example, if the vaporizer is outside the range of the user device, the vaporizer may be configured to disable operation of the vaporizer such that the vaporizer is inoperative until it returns within communication range with the user device.

[0100] An application running on a user device may be configured to disable and/or block the vaporizer in response to location and/or time parameters, such as how long the vaporizer has been out of range relative to the user device.

[0101] The application may 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 may resume an operating state in response to being within communication range with the user device.

[0102] The evaporator may be configured to receive information associated with a first user of the first user device. The evaporator may be configured to activate and/or unlock operation of the evaporator in response to an operative connection and being within a threshold communication range of the evaporator with a first user device associated with the first user. The evaporator may be configured to deactivate operation of the evaporator in response to the evaporator being outside a threshold communication range with the first user device. The evaporator may be configured to deactivate operation of the evaporator in response to an operative connection of the evaporator with a second user and/or a second user device. For example, if the first user pairs the first evaporator with the first user device, the first evaporator may be deactivated and/or locked in response to an attempt by the second user to pair the first evaporator with the second user device.

[0103] The user interface examples illustrated in Figs. 13A-13H relate to blocking and message generation features that may provide data sharing benefits, as well as vaporizer-specific controls to prevent unauthorized and/or underage use, purchase, etc. of the vaporizer.

[0104] The application screen view of Fig. 13A or a similar approach may be used to indicate to the user of the vaporizer the need to implement the device lock feature. In one example, it may be provided as an "explicit opt-in" feature such that the vaporizer has a default state of not automatically entering the locked state. Alternatively, the lock feature may require an "explicit opt-out" by the user to disable automatic lock. In still other examples, the automatic lock feature may not be a user-configurable option.

[0105] The screen views of Fig. 13B and Fig. 13C show views that may be presented to the user after selecting an explicit consent feature. This screen may be used to explain that the vaporizer should automatically enter a locked state if communication between the user's mobile device and the vaporizer does not occur for a period of time exceeding a threshold amount of time. Functionally, when this feature is turned on, the vaporizer controller (e.g., a microcontroller, a PCB, software running on a programmable processor, other computing hardware, etc.) may perform operations that monitor the duration since the last successful communication with the user's mobile device that is paired with the vaporizer. If this duration exceeds a threshold value, the vaporizer controller may cause the normal operation of the vaporizer to be interrupted, such as by preventing current from being delivered to the heating element or otherwise activating the nebulizer that causes the formation of an inhalable aerosol.

[0106] The screen views of Fig. 13D and Fig. 13E show the transition from disabling to enabling the automatic lock feature via activation of a user interface element, such as a slider control (upper left corner of the screens of Figs. 13D and 13E). In one exemplary implementation, the user may choose to explicitly opt in or explicitly opt out of the availability of the automatic lock feature, such as via the views of Figs. 13A-13C. At any time, the user may choose to enable or disable the automatic lock feature for their vaporizer using the on-off selection shown in Fig. 13D and Fig. 13E. Disabling the feature may be required if the user intends to use their vaporizer for a period of time when the user's mobile device is not nearby, or if the user's mobile device is to be turned off or otherwise placed in a state in which it is unable to communicate with the vaporizer. In some embodiments of the present invention, it may be advantageous for the automatic lockout disable feature to have a time limit such that the evaporator controller reverts back to the automatic lockout enable state after some fixed or user configurable automatic lockout disable duration.

[0107] In some implementations, the vaporizer device and/or the user application may be configured to display a first notification for a locked device that is "in range" (e.g., when the user device is within a threshold range relative to the vaporizer device). In some implementations, the vaporizer device and/or the user application may be configured to display a second notification for a locked vaporizer device that is "out of range" (e.g., when the user device is outside a threshold range relative to the vaporizer device), such as shown in Fig. 13F. The vaporizer device and/or the user application may be configured to display an option for the user to explicitly consent to some or all of the "automatic blocking" features. For example, the vaporizer device and/or the user application may be configured to display a countdown timer for a timed "automatically locking" of the vaporizer device that is "in range" (e.g., when the user device is within a threshold range relative to the vaporizer device). In some embodiments, the user may have the option to specify a duration after which the "automatic locking" is responsive (e.g., a time varying from a default time of 24 hours may be provided). In some implementations, the vaporizer device may be configured to automatically lock the vaporizer device in response to a change in the vaporizer device from an "in range" state to an "out of range" state. In some implementations, the vaporizer device may be configured to automatically lock the vaporizer device in response to the vaporizer device being "out of range" for a specified period of time (e.g., 24 hours). In some embodiments, the evaporation device may be configured to unlock automatically in response to returning to the "in range" state. In some implementations, the evaporation device and/or the user application may be configured to display an overlay description of the lock/unlock feature and/or an image and/or an animated GIF representation of the evaporation device being in range and/or out of range.

[0108] In other words, Fig. 13F shows a screen view that may indicate that automatic locking is enabled and that the vaporizer is not within range of the mobile device (and is therefore unusable until communication is re-established between the mobile device and the vaporizer). Fig. 13G shows an optional screen view that may be included to require that a password or some biometric verification (e.g., fingerprint sensor ID, facial recognition, etc.) be accepted by the user's mobile device to reauthorize use of the vaporizer and thereby instruct the mobile device to transmit to the vaporizer controller that operation of the vaporizer should be allowed again. Such a feature may prevent a minor or other unauthorized user 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 the mobile device and the vaporizer to re-establish communication. Fig. 13H shows an example of a screen display that may indicate that proper authorization has not been received such that the vaporizer should remain disconnected.

[0109] In some implementations, a vaporizer blocking feature for blocking (e.g., disabling) or unblocking (e.g., enabling) the vaporizer device from a user interface of a user device may be configured to be available when the vaporizer is within communication range of the communication device (e.g., when the user device is within a threshold range of the vaporizer device). In response to blocking the vaporizer device, the vaporizer device may be configured to disable some or all of the functionality of the vaporizer device. In various examples, blocking the vaporizer may include one or more of turning off power to the heating element, ignoring inputs from a pressure sensor or other switch configured to activate the vaporizer to generate an aerosol, etc. In response to detecting an attempted inhalation/puff on a locked vaporizer device, the vaporizer device may be configured to display a "locked" LED indicator, block airflow, and/or provide another indication that the device is being locked. In some aspects, blocking the vaporizer device may change the state of the home screen in the user interface such that if the vaporizer device is being locked, a "locked" notification is displayed and the user can unlock the vaporizer device from the home screen. The vaporizer device may be configured such that the user can only unlock the vaporizer device through an application logged into the user's account. In some embodiments, the blocking and/or unlocking features may be available with/without Wi-Fi and/or the user/device having data service reception.

[0110] In addition to the above automatic blocking features, the vaporizer device may be configured to provide an "access token" for registered users of the application to log into an account with/without age verification (AV). The vaporizer device may optionally have a configuration in which the availability of the access token may be associated with the application and/or the user's login to the account, rather than a specific user mobile device. In some implementations, the user device, using the device application with a specific user logged into the user account, can unlock/lock a specific device previously locked by this user using another instance of the device application.

[0111] Locking the device may be accomplished by shutting off the power supply to the heating element, pressure sensor, or other element of the evaporator.

[0112] In some implementations, a vaporizer blocking feature for blocking (e.g., disabling) or unblocking (e.g., enabling) the vaporizer from a user interface of a user device may be configured to be available when the vaporizer is within communication range of the user device (e.g., when the user device is within a threshold range of the vaporizer). In response to blocking the vaporizer, the vaporizer may be configured to disable some or all of the functionality of the vaporizer. In response to detecting an attempted inhalation/puff on a blocked vaporizer (or other attempted use of the vaporizer, such as quickly touching the device to perform a query regarding battery level and/or inserting or removing a pod), the vaporizer may be configured to display a "blocked" LED indicator, block airflow, and/or provide another indication that the device is being blocked. The "locked" indicator may include a "locked" animation, a battery level animation, an LED animation, a sound, etc. In some aspects, locking the vaporizer may change the state of the home screen in the user interface such that if the vaporizer is locked, a "locked" notification is displayed and the user can unlock the vaporizer from the home screen. The vaporizer may be configured such that the user can only unlock the vaporizer through an application logged into the user's account. In some embodiments, the lock and/or unlock features may be available with/without Wi-Fi and/or a user/device having data service reception.

[0113] In some implementations, the vaporizer and/or the user application may be configured to display a first notification for a locked device that is "in range" (e.g., when the user device is within a threshold range relative to the vaporizer). In some implementations, the vaporizer and/or the user application may be configured to display a second notification for a locked vaporizer that is "out of range" (e.g., when the user device is outside a threshold range relative to the vaporizer), such as shown in FIG. 28. The vaporizer and/or the user application may be configured to display an option for the user to explicitly agree to some or all of the "auto-lock" features. For example, the vaporizer and/or the user application may be configured to display a countdown timer for a timed "auto-lock" of the vaporizer that is "in range" (e.g., when the user device is within a threshold range relative to the vaporizer). In some embodiments, the user may have an option to specify a duration after which the "automatic lock" is responsive (e.g., a time varying from a default time of 24 hours may be provided). In some implementations, the vaporizer may be configured to automatically lock the vaporizer in response to a change in the vaporizer from the "in range" state to the "out of range" state. In some implementations, the vaporizer may be configured to automatically lock the vaporizer in response to the vaporizer being "out of range" for a specified period of time (e.g., 24 hours). In some embodiments, the vaporizer may be configured to automatically unlock in response to a return to the "in range" state. In some implementations, the vaporizer and/or the user application may be configured to display an overlay description of the lock/unlock feature and/or an image and/or an animated GIF representation of the vaporizer device being in range and/or out of range.

[0114] The vaporizer may be configured to provide an "access token" to registered users of the application for logging into an account with/without age verification (AV). The vaporizer may be configured such that the availability of the access token may be associated with the application and/or the user's login to the account, rather than a specific user device. In some implementations, a user device, using a device application with a specific user logged into the user account, may unlock/lock a specific device previously locked by this user using another instance of the device application.

[0115] The vaporizer may be configured such that the accessibility feature may operate on a user device without Wi-Fi, LTE, or other Internet connectivity. The accessibility feature may respond to the device being within Bluetooth Low Energy (BLE) range of the user device and the user currently being logged into a user account. In such implementations, a request to external servers may not be required to unlock or lock the vaporizer from the application.

[0116] In some embodiments, pairing, locking, and/or unlocking of the vaporizer may be available only through an application logged into the user account associated with the vaporizer. The vaporizer may be configured to automatically lock after an extended period of no connection to the user's device and/or application. For example, if the vaporizer is not connected to the paired application within a specified window (e.g., 1 second, 24 hours, 7 days, and/or other durations), the vaporizer may automatically lock to prevent unauthorized use of lost or stolen vaporizers.

[0117] The evaporator may be configured such that a lockout feature may be retained between power-on events. The configuration and state data for such feature must be maintained in a non-volatile data storage device on the evaporator to remain operational during a power-on reset (POR) and/or other reset conditions.

[0118] The vaporizer may be configured such that a locked device cannot be reset to factory defaults (a lock retention feature) and may provide an indication to the user that the vaporizer is being locked. For example, if the user attempts to "factory reset" a locked vaporizer, the vaporizer may display a "locked" LED indicator and not be reset.

[0119] The vaporizer may have a configuration in which the lock retention feature includes security sufficient to prevent the functionality of the lock from being compromised by hacking. In some embodiments, a shared private key must be used to lock/unlock the vaporizer. The shared private key may be generated by an application and transmitted to the vaporizer during a lock request. To unlock the device, the application may be configured to provide challenge-response authorization to the vaporizer with the private key to initiate an unlock sequence.

[0120] The vaporizer may be configured to authorize authorized vaporizers to associate with different user devices that belong to the same owner of the user account. For example, if the user loses his user device, the user may be able to log into the application account on his new user device and pair the vaporizer with the new user device. For a vaporizer previously paired with another user device and associated with the owner of the user account, the vaporizer may pair with the new user device in response to the fact that the user credentials of the application are identical to the user credentials used to pair the vaporizer on the previously paired user device.

[0121] The vaporizer may be configured such that authorized users may not be required to "shake to pair" (e.g., perform electronic exchange of information based on a handshake procedure) with an identical user device logged into an identical user account after first pairing and/or linking to the user account. For example, when the vaporizer is linked to a user account (with or without age verification), the vaporizer may "remember" this pairing until it is unlinked from the user account. The user's credentials may be stored on the vaporizer such that information about linked applications is stored.

[0122] The vaporizer may be linked and authorized (e.g., linked to an account, with/without age verification) in such a way that a specific set of features may be provided to the user based on the authorization and/or linking. The vaporizer may be configured such that authorized and authenticated devices may be linked and a specific set (full set) of features is provided to the user via the application.

[0123] The vaporizer may be configured such that authorized ownership prohibits vaporizers belonging to another account owner from associating with another account without explicitly disassociating, by the device owner, the vaporizer from the original account, thereby complicating theft by transmitting information that the vaporizer is paired with another user of the account. For a vaporizer previously paired with another user device and associated with a user account, the vaporizer may pair with a new user device only in response to the user's application credentials being identical to the user credentials used to pair the vaporizer on the previously paired user device. In some implementations, in response to pairing the vaporizer with a first user account and/or a first user device, the vaporizer may be configured such that it may not pair with a second user account and/or a second user device.

[0124] The vaporizer may be configured to have authorized ownership. For example, if a user attempts to associate a vaporizer paired with a first user account with a second user account, the user interface may be configured to display the name of the vaporizer and/or the second user (e.g., if the user accidentally swapped with a friend).

[0125] The vaporizer may be configured to operably connect to one user device at a time. For example, the vaporizer may pair and bind to one central Bluetooth user device only in such a way that subsequent pairings and bindings overwrite previous connections.

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

[0127] The vaporizer may be configured such that users who link vaporizers may link only a specified number of vaporizers per period of time to prevent underage abuse (e.g., to activate/deactivate the device to prevent youth use). For example, concurrent e-commerce regulations allow a maximum of five devices to be linked in 90 days (the e-commerce purchase limit). The application may be configured to communicate a date after which the user may link another vaporizer.

[0128] The vaporizer may be configured to "shake to pair" to initially pair the vaporizer with the user account (to prevent other vaporizers within range from pairing). The vaporizer may provide an indication that it is being shaken and paired.

[0129] The vaporizer may be configured such that counterfeit vaporizers cannot connect to the application and/or the cloud during the initial pairing process with the user device. The application may be configured to verify that the vaporizer is not a counterfeit device before allowing the device to be associated with the user account and/or providing any application services (such as firmware updates). Such a process may use standardized security procedures to ensure that the service is secure and unhackable.

[0130] The vaporizer may be configured such that genuine vaporizers may take steps to pair and communicate only with genuine manufacturer applications and the cloud to ensure security. The vaporizer may be configured to independently verify that the application and/or cloud connection is provided by the manufacturer and not a third-party service to prevent fraud and other actions not approved by the manufacturer. Such a process may use standardized security procedures to ensure that the service is secure and unhackable.

[0131] The vaporizer may be configured such that the first pairing and binding of the user device (an unassociated device) must occur when the application has Internet access. Internet access may be required to verify genuine (relative to counterfeit) vaporizers.

[0132] The vaporizer may be configured to allow users to pair additional devices with their account ("add a device") subject to a limit of five devices per 90 days. The application may be configured to verify such criteria and provide a notification regarding verification (or non-verification).

[0133] The vaporizer may be configured to "factory reset" if the device is not locked. Factory reset may include resetting the vaporizer to a "shipment" state, including clearing the log and resetting "research mode" while collecting data to "standard mode." If reset gestures are attempted (e.g., if a pod is removed and/or inserted) while the vaporizer is locked, the vaporizer may be configured such that the LEDs display a "locked" indicator. The user must first unlock the device to enable factory reset. Factory reset gestures may include orienting the device vertically so that the pod points up, removing the pod, orienting the device so that the end of the pod is at the bottom, inserting the pod, removing the pod a second time, orienting the device with the end of the pod at the top, reinserting the pod, etc.

[0134] The vaporizer may have a configuration such that if the user loses the locked device and disconnects it from the user account and then finds it again, he can reconnect the device by logging into his user account to resume use. If the device is lost in a locked state and re-pairing is attempted with the account with which the device was originally associated, the device may function normally and the connection with the account may be restored. If re-pairing is attempted with another account, the device may remain locked.

[0135] The vaporizer may have a configuration such that a device that is not associated with an account (even if it is unauthorizedly associated with a user device) can be re-paired and linked to any user device and any user account such that the device can be re-paired and linked to the application, the concept of ownership is not imposed on this linking until the device is linked to the user account of the vaporizer.

[0136] In some implementations, a vaporizer that is not associated with another user account may be paired and linked to a user device and application without requiring the user to sign in to an account for the application (e.g., for new vaporizers, if the user has not yet gone through account sign-in or authentication). However, the application may be configured to provide reduced feature sets until the user signs in with an existing user account or creates a new user account.

[0137] In some implementations, users may unlink a vaporizer from an associated user account (e.g., if the user wants to give away the vaporizer or if the user loses the vaporizer). In one embodiment, the previous user's data (e.g., usage data) may be visible to a new user of the vaporizer. An associated vaporizer may be unlinked from the user account both when it is in range and when it is out of range via an application. The vaporizer may be configured to restore to factory settings, including unlocking the vaporizer if the vaporizer "locks up," and erasing the history but keeping the latest firmware, in response to an attempt to pair the vaporizer with the application again.

[0138] The evaporator may have a configuration in which, in response to a rewrite/update of the firmware (main/working image) of the evaporator, the evaporator may not function normally (e.g., may not generate vapor). A static LED pattern (or other indication) may be provided to alert the user that the evaporator is undergoing an update. In some embodiments, the basic function of the evaporator may be suspended in response to loading the firmware into the memory of the microcontroller. A static LED pattern (or other indication) may be displayed in the update state to alert the user that the evaporator is functioning and updating the firmware.

[0139] In some implementations, the usage data may be linked to the user account, so that if the user logs into the application account on another user device (or logs out of the account and then logs back in), the data may be retained. The usage data may include one or more of the vapor consumption experience, goal data (e.g., from user settings, adaptation workflow), targeted puffing results, location history, and/or other usage data.

[0140] In some implementations, if a user deletes an associated user account, according to the General Data Protection Regulation (GDPR), all data associated with that user must be permanently unlinked from that user account in an irreversible manner. The user application may be configured to unlink user data, provide user data (e.g., via CSV, etc.) based on a user request, provide terms and conditions pages to the user.

[0141] In some implementations, a user may complete age verification from one of a plurality of locations within an application, which results in associated updates to a set of features of the application. An account settings page of the application may display "age verification completed" for the country (or other geographic region) of the user and may include other information associated with the user and/or an account associated with the user. In response to age verification updates, the included features may include checkout, vaporizer replacement, external web pages, a mobile web site, and/or other features. Age verification may be required to checkout, vaporizer replacement, and other features. Age verification may be accessible from one or more of checkout (e.g., shopping), an account menu, a vaporizer replacement flow, account sign-in, an Internet connection, and/or other features of the application. The user's age verification status may be reflected in the account settings. The application may provide the age verification status and what country the verification applies to. The user may be provided with the option to complete age verification from within the application. In response to an unverified request, an external mobile web page may be provided.

[0142] User Age Verification

[0143] In some implementations, age verification procedures may include verification using database services. In some implementations, a user may undergo age verification using personal user information, such as a social security number, credit history, facial recognition, etc. In some implementations, the user's name and phone number may be verified using two-factor authentication (e.g., receiving a code via a text message). Other age-based authentication procedures may include a "passport" feature. For example, a user may create identity data for authorized use via a user interface of a user device. When the vaporizer moves out of proximity of an associated user device, the vaporizer may be configured to disable functionality. The functionality may be re-enabled in response to returning within a threshold proximity of the associated user device. In some implementations, the vaporizer may be configured such that the vaporizer remains on in response to being outside a threshold proximity of the user device for a limited duration (e.g., after a given period of time has elapsed, the vaporizer may be locked).

[0144] Age verification may also be correlated with location information to determine whether the user meets the age threshold. For example, the vaporizer and/or the application may receive global positioning system (GPS) information to identify the location of the vaporizer and/or the application. In some aspects, the age threshold may be based on a geographic location, such as a specific country, state, city, county, etc. If the age threshold is changed based on the location of the vaporizer and/or the application, the vaporizer and/or the application may re-authenticate the user based on the updated age threshold.

[0145] Performing such multi-factor authentication with proximity detection may reduce the likelihood of underage use and/or unauthorized use of the vaporizer. Additionally, correlating proximity and/or location information with age verification information and/or identity information may provide greater flexibility in preventing operation of the vaporizer in certain areas.

[0146] The vaporizer may be configured to accept vaporizer settings from a user via an application. The vaporizer settings may include changing the name of the vaporizer. The user account may be configured to save the user's vaporizer settings such that if the user logs into the user account on a new user device, the user's previous settings may be saved. The vaporizer settings saved by the user account may include brightness, lock state, low battery warning, vaporizer name, and/or other settings. The user account may be configured to unlink the vaporizer from the user account. As a non-limiting example, in response to a user selecting "unlink vaporizer", a message such as "Are you sure you want to unlink <JUUL JOHN> from your account? The vaporizer may be reset to factory settings and may be linked to any other user's account" may be provided. In response to the user selecting "Yes", the vaporizer may be unlinked. In response to the user selecting "No", unlinking may not remove usage data from the user's account, may remove all location data, and/or may remove the vaporizer from location features.

[0147] Additionally, the vaporizer settings may include the warranty and/or registration status of the vaporizer. In response to an unregistered vaporizer (e.g., when the vaporizer is not associated with an account because the user does not log into the account), a display of the warranty registration page may be provided in such a way that the vaporizer information is provided and the user is instructed to create or log into a user account. In some embodiments, the application may be configured such that the user can create a new account and/or log into an existing account using existing login information for a Google account, Facebook account, etc.

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

[0149] Monitoring - Health and Quitting. The vaporizer and/or applications running on a device that is part of the vaporizer system according to embodiments of the present invention may also be configured to monitor for use of a digital treatment course and/or smoking cessation, etc. For example, similar to weight loss monitoring devices, the vaporizer or application, or both, may be useful for people who want to reduce their nicotine intake and/or track how much nicotine is consumed over a certain amount of time. For example, the vaporizer and/or application may be configured to allow users who smoke both regular cigarettes and e-cigarettes to record how many cigarettes they consume and compare the total amount of HPHC and nicotine they receive on different days when they use different combinations.

[0150] The app and/or vaporizer may also provide additional incentives by providing messaging, such as generating messages regarding how much of compound X is being consumed, and may show how much money a former smoker saves by reducing or eliminating smoking. This should be most relevant for nicotine, although it may also be used for other substances. In some implementations, the user may enter their usual price per pack of cigarettes, which may be used as a baseline. This may also be relevant for THC, since vaping is a more efficient means of consumption. From anecdotal evidence, a 5-10x multiplier is envisaged between smoking and vaping; for example, someone who vapes x mg of THC would otherwise have to smoke 10x mg of THC in a given time interval. Based on dosage monitoring by the device, the vaporizer and/or app may report savings relative to how much the user would otherwise smoke.

[0151] In some embodiments of the present invention, the application may also allow the user to log other health-related activities, such as from a fitness application, and/or may offer correlations between nicotine or THC use and alcohol consumption, heart rate, blood pressure, exercise time, or weight changes, etc. For example, the user may enter a preferred unit dose (using presets or estimated/recorded/programmable data as described herein) and a dosing interval or overall daily goal. The vaporizer and/or the application may then lock after each dosing, and an alert may be displayed on a screen on the user's computing device (e.g., a phone, smartwatch, tablet computer, etc.) when it is time for the next dosing, and the vaporizer is automatically unlocked for that next dosing. This may be used as a user-selectable taper (lower or quit) approach or to maintain a prescribed treatment program (e.g., X mg of agent every Y hours, but not more than Z mg/day). In some aspects, the vaporizer and/or application may capture user and/or vaporizer usage information that may be returned to the application (e.g., via Bluetooth, Wi-Fi, etc.) such that the information may be recorded and recommendations regarding nicotine cessation programs may be provided based on the captured and/or recorded data (including device usage and additional information) and/or usage patterns determined therefrom. In some aspects, the recommendation may include a cessation plan based on the data and/or patterns that is implemented using the application and the device (e.g., by locking the device at certain times based on the plan).

[0152] In some implementations, the vaporizer and/or affiliated application may have a dashboard-style user interface in which users can record and tabulate their progress over time. The data may be based to some extent on individual and/or group data. For example, the group data may show as an aggregate what the frequency of switching between smoking and vaping is at any given time since the vaporizer was first used. The equipment may provide a view in which the user can select other users to define a cohort based on their initial conditions: for example, number of packs per day, age, gender, etc.

[0153] Control and customization of the device. As mentioned herein, the vaporizer may be controlled in part by user input to the affiliated application. For example, specific aspects of the vaporizer that may be controlled may include changing the temperature setpoint, such as allowing users to produce less vapor if they want to be less noticeable. This may also allow the user to reduce the harshness and consumption of active ingredients per puff.

[0154] The app may also provide more accurate indication of the battery level beyond what is displayed on the vaporizer. For example, while charging, the app may indicate the time remaining.

[0155] As mentioned in this document, the application may also provide firmware updates to the evaporator.

[0156] For a device that accepts both nicotine and THC cartridges, an affiliated (connected) application may also provide the ability for the user to switch between nicotine and THC use modes, which may likely have different temperature settings.

[0157] The vaporizer and/or a device that is part of the vaporizer system may use a received signal strength indicator (RSSI) to help the user find a lost vaporizer. In addition, the application may provide the ability for the user to instruct the vaporizer to vibrate, flash, and/or emit sound(s) as an alert, including to help find the lost equipment. For example, a change in temperature, vibration, or flashing light may also be an indication of whether or not the vaporizer is hidden nearby. In some implementations, the vaporizer may also help find a lost phone when connected by changing the colors of the LEDs depending on the distance between the vaporizer and the phone.

[0158] One or more network devices may be configured to receive, via one or more processors, information associated with the vaporizer, transmit the received information associated with the vaporizer to an application, and determine a unique identifier associated with the vaporizer. The network devices may include user devices of other users of the vaporizer. The application may be configured to determine whether or not the vaporizer is within communication range of the one or more network devices. The vaporizer may be configured to emit a signal in response to an indication transmitted by the network devices. For example, if the vaporizer is misplaced at a location outside the range of the user device, the one or more network devices may receive a "device lost" notification, and the misplaced vaporizer may emit a signal in response to being within communication range of the one or more network devices. The network devices may be configured to transmit location information to the user device in response to determining the location of the vaporizer. The evaporator may be configured to be switched off and/or blocked in response to an instruction transmitted via network devices.

[0159] The vaporizer and/or the application may be used to adjust the brightness and color of the vaporizer's LEDs. For example, for vaporizers with multiple LEDs, the user may be able to download customized indicator patterns to the device. In addition to providing greater personalization of the vaporizer, this may have improved utility as it makes it easier to identify which vaporizer belongs to a particular owner.

[0160] In some implementations, the temperature of the evaporator may be adjusted using a graphical user interface that provides both coarse and fine control of the temperature of the evaporator using a single finger. For example, the graphical user interface (GUI) may include a temperature display that visually indicates the current temperature and/or a target temperature of the evaporator; this temperature may be adjusted up or down (within a range). In this example, to adjust the temperature, the user may hold the tip of a finger at a location on/opposite the indicator, which causes the indicators to appear on either side of the temperature where the evaporation temperature may be adjusted up (on the right side) or down (on the left side). Quickly sliding the finger across adjacent indicators allows the temperature setting to be quickly moved in large intervals (e.g., by intervals of 3 degrees, 5 degrees, 10 degrees, 15 degrees, 20 degrees, 25 degrees, 30 degrees, 35 degrees, etc.). Larger range adjustments are indicated by large circles. Holding the fingertip on the temperature indicator or adjacent indicators for a predetermined longer period of time (e.g. 1 second, 2 seconds, 3 seconds, 4 seconds, 5 seconds, etc.) can open the fine temperature control; moving the finger along the fine temperature control can provide the ability to increase/decrease the selected temperature by precise amounts (e.g. 0.1 degree, 0.5 degree, 1 degree, 2 degrees, etc.). The temperature change is shown in the central temperature indicator.

[0161] Fig. 6 illustrates an example computing equipment 600, the features of which may be used in some example implementations. It should be understood that all of the components shown in Fig. 6 do not necessarily have to be in an identical single device or equipment. Certain functions, for example, may be split between the vaporizer and the user device. In other examples, a feature may be distributed between the user device and the vaporizer, which includes two or more separable components (e.g., a charging unit and a vaporizer). For example, at least a portion of the computing equipment 600 may be included as part of the vaporizer 100, the vaporizer 200, the user device 305, the remote server 307, the beacon 705, the user device 805 and/or one or more other parts of the evaporation system. The components of the computing equipment 600 may be implemented in addition to or alternatively to any of the illustrated and/or described components of the evaporation equipment 100, 200. The computing equipment 600 may be implemented with the ability to perform one or more of the processes described herein.

[0162] The computing equipment 600 may perform one or more processes described herein. For example, the computing equipment 600 may be used to execute an application that provides user control of an evaporator in communication with the computing equipment 600 and/or provide an interface for a user to participate in and interact with functions associated with the evaporator, in accordance with some example implementations.

[0163] As illustrated, the computing equipment 600 may include one or more processors, such as a processor 610, to execute instructions that may implement operations in accordance with the operations described herein. The computing equipment 600 may include a memory 620 to store executable instructions and/or information. The memory 620 may include a semiconductor memory device, solid-state disk drives, magnetic disk drives, or any other information storage device. The computing equipment 600 may include a network interface 640 with a wired network or a wireless network, such as the network described with reference to Fig. 5. To implement wireless communication, the network interface 640, for example, may use one or more antennas, such as an antenna 690.

[0164] The computing equipment 600 may include one or more user interfaces, such as a user interface 650. The user interface 650 may include hardware or software interfaces, such as a keyboard, mouse, or other interface, some of which may include a touch screen integrated with a display 630. The display 630 may be used to display information, such as information related to the functions of the evaporator, provide instructions to the user, receive user input, and the like. In various implementations, the user interface 650 may include one or more peripheral devices, and/or the user interface 650 may be configured to communicate with these peripheral devices.

[0165] In some aspects, the user interface 650 may include one or more sensors and/or may include an interface with one or more sensors, such as the sensors described herein. The operation of these sensors may be controlled at least in part by the sensor module 660. The computing equipment 600 may comprise an input/output filter 670 that may filter information received from the sensors or other user interfaces, received and/or transmitted via the network interface 640, and the like. For example, signals detected via the sensors may pass through the filter 670 to properly convert and condition the signals, and the filtered data may then be transmitted to the sensor module 660 and/or the processor 610 for validation and processing (e.g., before transmitting results or indications via the network interface 640). The computing equipment 600 may be supplied with power by one or more power sources, such as a power source 680. As illustrated, one or more components of computing equipment 600 may exchange data and/or receive power via system bus 699.

[0166] Any of the devices described in this document may include device locking as mentioned in this document. For example, the application (e.g., running on the user device 305) and/or the vaporizer 100, 200 may be authenticated to the mobile device (e.g., the user device 305) using encryption as an anti-counterfeiting mechanism. A similar scheme may be used to associate the vaporizer 100, 200 with the user device (e.g., a mobile communication device such as a phone, smart watch, tablet computer, computer, etc., owned or used by the user), so that in the event of theft, the vaporizer can be disabled to prevent its use by others. In some implementations, the vaporizer 100, 200 may periodically connect using the network interface 640 to the user device 305 to verify and/or authorize the use and/or age of the user. In some implementations, the user may connect to the application on the user device 305 or computer and provide authentication in order to ensure the operation of the vaporizer 100, 200. In some aspects, the authentication includes entering a password or PIN code, a given gesture (for example, quickly touching three times), selecting a confirmation button, voice authentication or biometric authentication (for example, facial recognition) entered into the application using the user interface 650.

[0167] The vaporizers 100, 200 described herein may also include a parental lock (e.g., child protection). For example, the vaporizer 100, 200 may be "locked" for parents who want to ensure that their children or other minor users cannot use the vaporizer. For parental lock, in addition to Bluetooth or other relatively long-range communication, the vaporizer 100, 200 may also implement a near field communication (NFC) tag in the vaporizer. The NFC tag may be implemented in the computing hardware 600 (e.g., using the sensor module 660, the network interface 640, the input/output filter 670, and/or the user interface 650). The NFC tag may be configured to store and transfer information. NFC readers are built into many smartphones. One feature of NFC is that it only works at a very short range, which may provide the ability to easily perform unlocking of the vaporizer for the user. For example, the user may only need to quickly touch an already authorized phone to the vaporizer, and the vaporizer may thereby receive one or more authorization codes from the phone to unlock the vaporizer (possibly after the phone itself is unlocked in some traditional way by its authorized user). In some aspects, the authorized user device may activate the NFC tag of the vaporizer 100, 200, and the NFC tag of the vaporizer 100, 200 may transmit information and / or an identifier via the network interface 640 and / or the antenna 690 to the user device 305 to enable unlocking of the vaporizer. NFC tags are extremely cheap and small and can be used in addition to or instead of other wireless communication modes, such as Bluetooth. NFC may be used to implement certain other features described in this document.

[0168] In some implementations, authentication may occur in the evaporator 100, 200. For example, the evaporator 100, 200 may include a thumbprint/fingerprint sensor (e.g., as part of the sensor module 660) that enables the evaporator to operate with a valid thumbprint/fingerprint. The evaporator may also include other biometric sensors (e.g., as part of the sensor module 660) for authentication purposes. For example, the evaporator 100, 200 may include sensors that enable iris recognition, face recognition, speech recognition, DNA recognition, and the like. In another example, the evaporator 100, 200 may require a specific action/gesture to operate. The specific action or gesture may include entering a password or PIN code, a predetermined gesture (for example, quickly touching three times), voice authentication, selecting a confirmation button, or biometric authentication (for example, facial recognition). In some aspects, the processor 610 may receive these inputs from the sensor module 660 or another component of the computing equipment 600 and determine whether or not the authentication is successful.

[0169] In some aspects, it may be advantageous to implement authentication/child lock procedures at different times or stages of use of the evaporator 100, 200 in order to better protect against unauthorized use. The authentication/child lock procedures may be identical at each time period/stage or may differ depending on the time period/stage or any combination of the authentication/child lock procedures described herein at the same or different times/stages.

[0170] For example, in some implementations, the vaporizer may require a first authentication at or around the time of the initial purchase of the vaporizer equipment 100, 200. In some aspects, the first authentication may include locking the vaporizer 100, 200 to prevent any use of the vaporizer equipment until the consumer's age is verified and meets an age threshold. In some aspects, the processor 610 may perform the first authentication and/or locking in response to inputs received from the sensor module 660 or another component of the computing equipment 600. The first authentication may comprise a single-step authentication or a multi-step authentication. The locking may occur at the manufacturer, at the retailer, or at any stage during the manufacturing, distribution, or retail process. The type or method of the first authentication may depend on the retailer, location, or method by which the device is purchased. In some aspects, the consumer may freely use the vaporizer for a certain period of time after purchase (e.g., 1 day, 7 days, 30 days, etc.) before the first authentication (e.g., age verification) is required. The vaporizer may be configured to lock (e.g., disable functionality) in response to the expiration of the threshold period of time without completing the first authentication or completing the registration of the device through the user interface by the user.

[0171] In some aspects, the first authentication and unlocking of the device may occur at a point of sale (POS) terminal or online or in a retail store. For retail stores, the first authentication may include verification by the retailer of the age and identity data of the consumer. Verification may include a visual inspection of the consumer's identity documents (driver's license, passport, etc.). Verification may also include the retailer swiping or scanning a barcode, QR code or other encryption code of the identity card to read and verify the age and/or identity data of the consumer.

[0172] In some implementations, the retailer may manually enter or scan age/identity data into a computer application that verifies the identity and/or age of the consumer. For example, the retailer may be equipped with a tablet computer, a laptop computer, a desktop computer or other computing device that runs an application associated with the vaporizer. In some implementations, the application may be specifically tailored to the retail store for the retailer to more accurately perform age verification and identify the consumer. The consumer or retailer may register the device using the application and provide its identity and age information to the application. The application may then perform a first authentication to verify the age and/or identity of the consumer. In some aspects, the application may communicate with a vaporizer application database or a third-party system to complete the first authentication. In some implementations, the application retrieves the phone number associated with the consumer to verify that the same phone number is associated with the phone running the application and that the vaporizer is registered. The application may store the consumer information for later use. The retailer application may also communicate with one or more servers and/or databases to determine whether the consumer is associated with suspicious activity (e.g., a large number of device purchases) in order to flag and/or block the transaction. Such tracking may advantageously identify consumers who may be attempting to resell devices to minors or other unintended users in order to bypass first-party authentication or other youth authentication/anti-use measures.

[0173] Online retailers may also perform first authentication. For example, in order to purchase a vaporizer online, a consumer may be required to enter personal identification information, including age. The retailer may verify that the entered information is correct by accessing databases containing the consumer's personal identification information (e.g., social security department, vehicle registration service, tax authority documents, etc.), or the retailer may contract with third parties who have access to this information and can verify that the entered consumer information is correct and the consumer meets any age threshold. The third parties may receive the consumer information on a server, and the server may respond to the retailer with a determination of the consumer's age/personal identification data. The first authentication may include a multi-step authentication process in which, after the consumer enters his or her information (e.g., contact information), the retailer, manufacturer, etc. sends a code to the consumer (e.g., via an app, text message, email, etc.) for the user to enter before the purchase can be completed. In some aspects, the consumer and/or the retailer enters the code when the vaporizer is paired with a smartphone, tablet, computer, or other computing device. If the consumer and/or the retailer enters the correct code, the sale can be authorized, if not, the sales transaction can be completed. In some implementations, the information that the consumer uses can be stored to create a user profile. The user profile can be stored on the vaporizer, in the app, on a server, or on another computing device.

[0174] In some implementations, a retailer (online or in-store) may be authorized to unlock the phone after the first authentication. For example, a manufacturer, vaporizer company, distributor, or other entity may provide the retailer with a code or PIN to unlock the vaporizer equipment after successful verification for the first authentication. The code may be provided to the retailer via a computer application, a text message, a mail message, a printed document, etc. In some aspects, the code may be predetermined or randomly generated. The predetermined code may be based on a unique characteristic of the vaporizer (e.g., a serial code, a manufacturer's code, etc.). The code may also be valid only for a certain period of time after being generated. In some aspects, the retailer may have access to an application that communicates wirelessly with the vaporizer equipment. The application may instruct the retailer to confirm the results of the first authentication, and the application may then send a code to unlock the device to the retailer via an application interface, text message, email message, etc. The retailer may then enter the code on the vaporizer equipment or in an application that communicates with the vaporizer equipment to unlock the vaporizer for consumer use. For example, after the retailer receives the code message, the retailer may enter the code in its vaporizer application. The application then transmits a signal to the vaporizer, which unlocks the vaporizer.

[0175] In some aspects, a code may be provided to the consumer to unlock the device. For example, the consumer, after receiving the vaporizing equipment, may register the vaporizer online via a web page or in an application running on a smartphone, tablet computer, laptop computer or other computing equipment of the consumer. After authorizing the consumer in some way (for example, by checking authorized identification data to ensure that the consumer is of legal responsibility), the web page or equipment may provide the code to the user via the web page or application interface, a text message, an email message, etc. The consumer may enter the code in the interface/input of the vaporizer to unlock the vaporizer. In other aspects, the consumer may enter the code on a web page or in an application that is operatively connected to the vaporizer, and the web page or application may unlock the vaporizer by sending a signal to the vaporizer to unlock it for use by the consumer. In some aspects, the consumer enters a code when the vaporizer is paired with the consumer's smartphone, tablet, computer, or other computing device.

[0176] In some implementations, the application or web page may require additional input to complete the first authentication. For example, the application may require fingerprints to launch the application and/or authorize use of the vaporizer. In some implementations, a fingerprint sensor on the vaporizer equipment may receive the consumer's fingerprints and send the received input to the application. In other examples, a fingerprint sensor on a smartphone, tablet computer, laptop computer, or other computing device may send fingerprint information to the application. In some aspects, the application may store the fingerprint information in a database for future retrieval. Although fingerprints are described in some examples, the concepts may equally apply to other biometric feedback, such as retinal scanning or facial scanning and analysis.

[0177] Additionally, the application and/or web page may perform additional verifications to complete the first authentication. For example, the application or web page, after receiving the age and/or identification information of the consumer, may perform a check to determine whether the user and/or user profile associated with the received consumer information are associated with suspicious activity. For example, the application or web page may communicate with a server and/or database to determine whether the number of vaporizer devices associated with the consumer meets a threshold. In some implementations, if the number of vaporizers meets the threshold, the application and/or web page may flag or identify the consumer as an unauthorized reseller of the vaporizer and block the transaction.

[0178] In some implementations, the application and/or web page may initiate a live chat in which the consumer may provide his/her identification documents (e.g., driver's license, passport, etc.) to a live person on the other side of the communication to verify the consumer's identification data and/or age. Additionally, the application and/or web page may be configured to accept scans of identification documents and/or a magnetic strip of identification documents to be analyzed by the application and/or web page or by a person examining the identification documents.

[0179] After the initial purchase of the vaporizer equipment, it may be desirable to ensure that the vaporizer 100, 200 is used only by its intended consumer. For example, if the vaporizer is lost or stolen after the first authentication (e.g., purchase authentication), a second authentication in order to use the vaporizer makes it possible to prevent unwanted users (e.g., a minor, thieves, etc.) from using the vaporizer. Accordingly, the vaporizer may require a second authentication after the first authentication in order to allow use of the vaporizer. The second authentication may occur at or around the time that the consumer attempts to use the vaporizer for the first time. In some aspects, the consumer may freely use the vaporizer for a certain period of time after purchase (e.g., 1 day, 7 days, 30 days, etc.) before a second authentication (e.g., age verification) is required. In some aspects, the processor 610 may perform the second authentication and/or blocking in response to inputs received from the sensor module 660 or another component of the computing equipment 600.

[0180] In some aspects, the second authentication may be performed in an application running on a user device communicating with the vaporizer. The application may be executed on a smartphone, tablet computer, laptop computer, watch, wearable device or other computing equipment of the consumer. For example, the second authentication may include fingerprint-based authentication. In some aspects, the vaporizer may be authorized if the fingerprint input during the second authentication matches the fingerprint analysis during the first authentication. The consumer may input his fingerprints using a fingerprint sensor on the vaporizer or a fingerprint sensor on the computing equipment communicating or executing the application (e.g., on a smartphone, tablet computer, etc.). In some implementations, the second authentication may include other biometric information of the consumer to confirm that the device is used by a user identical to the user during the first authentication.

[0181] In some aspects, the second authentication may be correlated with user information or a user profile created at or before the time of the second authentication. For example, during the first authentication, the consumer may enter his or her age information (e.g., scanning a driver's license, manually entering a birthday in an application, etc.) along with a first sample of fingerprints. During the second authentication, the consumer may enter a second sample of fingerprints. If the second sample of fingerprints matches the first sample of fingerprints, the vaporizer and/or the application may correlate the consumer's age information entered during the first authentication in order to verify the consumer's age during the second authentication.

[0182] In some implementations, the computing equipment running the application may be used to provide the second authentication. For example, the vaporizer may remain in a locked position if the vaporizer equipment is not within a certain proximity to the computing equipment running the application. In some aspects, the application may be running on the consumer's smartphone, and the vaporizer remains locked until the smartphone is within a proximity threshold with the vaporizer.

[0183] Additionally, the vaporizer may be in an unlocked state within a proximity threshold and may transition to a locked state when the distance between the vaporizer and the user device running the application moves beyond the proximity threshold. In some aspects, the transition to the locked state may be based on a time threshold during which the vaporizer and the smartphone are beyond the proximity threshold. The time threshold may include a preprogrammed time threshold or may include a user-selectable time threshold. For example, the user may enter a time threshold into an application running on the user's smartphone.

[0184] In some aspects, a user wearing a user device may move away (or otherwise move) in a direction away from the vaporizer. After the user and smartphone move beyond a proximity threshold, a timer may be started in the application and/or the vaporizer. After the timer satisfies the time threshold, the vaporizer may enter a locked state. In some aspects, the vaporizer and/or computing equipment may detect proximity via Bluetooth, near field communication (NFC), Wi-Fi, ultrasound, ZigBee, RFID, cellular communication, or any other wireless communication. In some implementations, the vaporizer may time out after a certain predetermined time of unlocked use after a second authentication and require a similar second authentication in order to begin authorized use again.

[0185] The proximity-based blocking and unblocking described in this document may comprise a step in multi-step authentication. For example, proximity detection may be correlated with additional identification information to verify that the vaporizer belongs to the user (e.g., is registered to the user) and/or the application on the smartphone is associated with the same user. Proximity detection may also be correlated with age verification information to verify that the user who owns the vaporizer and/or is associated with the application satisfies an age threshold. In some aspects, the application may store a user profile of the user that stores age verification information, such as date of birth and age threshold information.

[0186] The user profile may also include the maximum number of vaporizers that the user is authorized to use. For example, to prevent one user from authorizing multiple devices for subsequent resale to minors or other unwanted consumers, the user profile may specify that the user may only be associated with one vaporizer at a time. For example, if the user owns multiple vaporizers and the application on the smartphone is paired with the first vaporizer, the other vaporizers owned by the user may be blocked. In some aspects, the application on the smartphone may send a signal to the other vaporizers to block the vaporizers. In other aspects, each time the application and the vaporizer are paired, the application and/or the vaporizer may check to determine whether the user is associated with another vaporizer that is currently being unlocked. If so, the application may first block the other vaporizer and/or break the pairing with the other vaporizer before pairing with the current vaporizer.

[0187] In some implementations, the vaporizer may be pre-programmed to pair with a specific user account/profile. For example, a user may order a vaporizer using an application that verifies the user's age. The ordered vaporizer may be configured to pair with the user profile that orders the vaporizer. In some aspects, the vaporizer may be configured to pair only with a pre-programmed user profile, which may reduce or eliminate additional re-authentication.

[0188] Age verification may also be correlated with location information to determine whether the user meets an age threshold. For example, the vaporizer and/or application may receive global positioning system (GPS) information to identify the location of the vaporizer and/or application. In some aspects, the age threshold may be based on a geographic location, such as a specific country, state, city, county, etc. If the age threshold is changed based on the location of the vaporizer and/or application, the vaporizer and/or application may re-authenticate the user based on the updated age threshold.

[0189] Performing such multi-factor authentication with proximity detection may reduce the likelihood of underage use and/or unauthorized use of the vaporizer. Additionally, correlating proximity and/or location information with age verification information and/or identity information may provide greater flexibility in preventing operation of the vaporizer in certain areas.

[0190] In some aspects, the second authentication may be completed electronically without the need to download an application. For example, a user may visit a website to register a device and/or undergo age verification. In some aspects, the user may enter a serial number of his or her device and then be prompted to undergo age verification (e.g., entering identification information, live chat, scanning identification documents, or using any of the methods for authentication described in this document). After successfully verifying age, the user may receive a passcode from the website. In some implementations, each passcode is a random number associated with the serial number (such as a hidden additional 4 digits in the serial number). After receiving the passcode, the user may then pair the vaporizer with his or her user device, such as either via Bluetooth or via some other communication protocol. Pairing may require a web site passcode (such as a 4-digit or multi-digit passcode) or another passcode to complete pairing. If the correct passcode is entered and pairing is successful, the device may unlock.

[0191] In some aspects, a hardware key may be used to provide a second authentication. In some aspects, a hardware key may comprise any hardware that connects to the vaporizer or other computing equipment to provide additional functionality. For example, a hardware key may function as a communication bridge between the vaporizer and an application or other computing equipment. In some implementations, a hardware key may connect to computing equipment that is not running an application that communicates with the vaporizer. The user may then communicate with the vaporizer on the computing equipment using the hardware key. Additionally, in some aspects, an application running on the computing device may lose communication with the vaporizer. The application may then communicate with the hardware key, and the hardware key may communicate with the vaporizer. In other implementations, the hardware key may be configured to provide a code to authorize operation of the vaporizer and/or communication with the vaporizer. For example, the hardware key may be configured to provide a randomly generated number or pattern for the user to enter into the application and/or the vaporizer to authorize operation. In some aspects, the code generated by the hardware key may be set such that it expires after a certain period of time (e.g., after 60 seconds, 5 minutes, an hour, etc.). After that, additional use of the vaporizer should require an additional new authorization code.

[0192] In some implementations, the vaporizer and/or smartphone may provide an indication that the vaporizer is unlocking. For example, the vaporizer and/or smartphone may output an audio, visual, tactile, or other indicator that the vaporizer is unlocking and ready for use by the user. The audio indicator may include an intermittent beep, a click, a song, or any other sound. The visual indicator may include a light, a color, a pattern of changing lights, a sequence of flashing lights, or any other visual indicator. The tactile indicator may include a vibration pulse, a sequence of vibration pulses, a pattern of vibrations, or any other tactile indicator.

[0193] In some aspects of the present invention, the second authentication (or full authentication) may be based on the location of the evaporator. For example, certain locations may be equipped with hardware ("beacons") configured to change the operation of an evaporator located within communication range relative to the beacons. Fig. 7 illustrates a communication scheme 700 based on communication between evaporators 100A, 200A, 100B, 200B and a disable beacon 705, in accordance with some example implementations. As shown in Fig. 7, the beacon 705 comprises a transceiver 701, a processor 702, a memory 703, and a network interface 704. In some aspects, the processor 702 may be configured to execute instructions that may implement operations in accordance with the operations described herein. The memory device 703 serves to store executable instructions and/or information. The memory device 703 may include a semiconductor memory device, solid-state disk drives, magnetic disk drives, or any other information storage device. The network interface 704 may be configured to connect to a wired network or a wireless network. In order to implement wireless communication, the network interface 704, for example, may use one or more antennas and/or transceivers, such as the transceiver 701.

[0194] In some implementations, the beacon 705 may be installed in a location that may have increased sensitivity to unauthorized or unwanted use of the vaporizer (e.g., in a school, in areas with large concentrations of young people, inside restaurants, on a commercial aircraft or other public transportation vehicle, etc.). In some aspects, the beacon 705 may be configured to disable vaporizers within communication range 725 relative to the beacon 705. As shown in FIG. 7, the evaporators 100A, 200A, 100B, 200B are located within the communication range 725 and can be turned off by means of the beacon 705. In some implementations, the beacon 705 can be configured to transmit a broadcast message via the transceiver 701 and/or the network interface 704. The evaporators 100A, 200A, 100B, 200B can receive the broadcast message over the network, and the controller 105, 205 can be configured to turn off the operation of the evaporator in response to receiving the broadcast message.

[0195] In some implementations, the beacon 705 and/or the broadcast message that turns off the vaporizers 100, 200 may be overridden by subjecting the vaporizers 100, 200 to additional age verification (e.g., a second authentication, as described in various embodiments herein). For example, an adult consumer turns on his or her vaporizer, even if the vaporizer 100, 200 is within communication range 725, by performing any of the authentication procedures described herein (e.g., entering a code, using a phone application, biometric identification, etc.). For example, the beacon 705 may send a communication to the vaporizers 100A, 200A, 100B, 200B and/or a consumer application for the vaporizer, notifying the consumer that the vaporizers 100A, 200A, 100B, 200B are within communication range 725. In some aspects, the vaporizers 100A, 200A, 100B, 200B and/or the consumer application for the vaporizer may display an indicator indicating that the vaporizers 100A, 200A, 100B, 200B are blocked. After notification, the user of the vaporizers 100A, 200A, 100B, 200B may log in to an account in the vaporizer application and/or use the vaporizers 100A, 200A, 100B, 200B to perform a second authentication in order to re-enable the vaporizers 100A, 200A, 100B, 200B while still within the communication range 725.

[0196] In other aspects, the vaporizers 100A, 200A, 100B, 200B and/or the vaporizer application may detect the beacon 705 and notify the consumer for the consumer to complete a second authentication or any other authentication to enable use of the vaporizer within the communication range 725 relative to the beacon. For example, the vaporizers 100A, 200A, 100B, 200B and/or the vaporizer application may transmit a communication searching for other devices within the communication range relative to the vaporizers 100A, 200A, 100B, 200B and/or the vaporizer application. In some aspects, the beacon 705 may receive communication from the evaporators 100A, 200A, 100B, 200B and/or the evaporator application and respond with communication that turns off the evaporators 100A, 200A, 100B, 200B. The user may then perform a second authentication in order to re-enable the evaporators 100A, 200A, 100B, 200B within the communication range 725.

[0197] In some implementations, the beacon 705 may be subject to geofencing such that the beacon 705 operates in certain locations. Such geofencing may help prevent the beacon 705 from being transported to another location in which the shutdown of the vaporizers is not required. In some aspects, the processor 702 and/or the memory 703 may be configured to retrieve geolocation information in order to determine the location of the beacon 705 and whether or not the beacon 705 is authorized to operate in this location. If the beacon 705 is outside of an authorized region, the operating instructions of the processor 702 from the memory 703 may be configured to disable the operation of the beacon 705. The hardware beacon 705 may advantageously provide additional security/safeguards against the use of the vaporizer by a minor in high-risk areas (e.g., in school zones).

[0198] In some implementations, the beacons 705 may also be configured to track and/or report with respect to the vaporizers 100, 200 within the communication range 725 relative to the beacons 705. For example, an application that supports communication with one or more beacons 705 may be configured to show a list or a graphical representation of the vaporizers within the communication range 725 relative to the one or more beacons. For example, the graphical representation may comprise a map showing an indication of the vaporizers 100, 200 within the communication range 725. The map or user interface may also include additional information associated with the vaporizers 100, 200 (e.g., serial number, model number, etc.) and/or with a user associated with the vaporizers 100, 200 (e.g., date of birth, age, school attended, etc.). This tracking may enable an administrator of an application or facility (e.g., a school) to track which vaporizers are located within an area and whether or not anyone is authorized to use within the area. For example, a school principal may track vaporizers present within a communication range 725 relative to one or more radio beacons 705 in order to determine whether or not any vaporizers 100, 200 associated with a student of the school within the communication range 725 are used or activated. In some aspects, the application may enable a principal or authorized administrator to report any unwanted or unauthorized use of a vaporizer to authorities and/or the manufacturer in order to improve prevention of unintended use. Additionally, information regarding unauthorized use of a vaporizer in a region may also be transmitted to the actual authorized owner and/or user of such vaporizer (e.g., a parent).

[0199] In some implementations, the beacons 705 may be configured to unlock the vaporizers 100, 200 within the communication range 725. For example, the vaporizers 100, 200 may be configured to be locked in locations outside the communication range 725, and the beacon 705 communication may be configured to unlock the vaporizers 100, 200. Such an example may be used as designated "smoking areas" for areas in which vaporizer use is generally prohibited (e.g., schools, airports, etc.).

[0200] In some implementations, instead of hardware beacons 705 installed at specific locations, the beacon functionality may be installed in an application running on a smartphone, tablet, computer or other computing equipment of a user (in a "beacon application"). Similar to the hardware beacons 705, the beacon application may be configured to change the operation of a vaporizer within communication range of the beacon application. For example, all vaporizers within communication range of the beacon applications may be disabled or may require additional age verification (e.g., a second authentication) to unlock use of the vaporizer while within said communication range.

[0201] The vaporizers 100, 200 may include or be coupled to a youth prevention device (YPD) configured to disable the vapor generation function of the vaporizer in response to detection by a youth prevention beacon device (e.g., beacon 705 and/or beacon 805). The YPD may include the controller 105, 205, an application, or any other component of the vaporizers 100, 200, the user device 305, the remote server 307, and/or the computing equipment 600. For example, the vaporizers 100, 200 with a YPD may include a youth prevention feature (YPF), in which the vaporizers 100, 200 may be completely disabled (e.g., disable vapor generation) for 30 minutes (or another period of time) when the vaporizer comes within range of the youth prevention beacon device. The YPD may be configured with security to completely disable the vaporizer. Security measures may be implemented to ensure that unauthorized parties cannot arbitrarily use the YPD's complete disable feature to otherwise interfere with or disrupt service to users for whom use should not be deauthorized.

[0202] In some embodiments, the ability of the youth prevention device to respond to the vaporizers 100, 200 may depend on the age verification state of the vaporizers 100, 200. For example, a registered and age verified vaporizer 100, 200 may be "invisible" to the YPD. The youth prevention features may be enabled by default (e.g., after the device is reset), but may be changed and/or updated when the user passes age verification. The vaporizer 100, 200, when connected to an application in which the user passes age verification, may explicitly opt out of the youth prevention device programs (for a specific, limited number of devices: limited by the number of devices that can be associated with the user account). The complete youth prevention alert disable mode may include strict security to prevent third parties from hacking and disabling the youth prevention features.

[0203] The vaporizer 100, 200 may be configured such that in response to the user unlinking the vaporizer 100, 200 from the age-verified user account, the youth prevention device features may be reactivated. The vaporizer 100, 200 may be configured such that the security protocols for preventing hacking may not be disabled. In this regard, the youth prevention feature may be deactivated only by a challenge in the shared secret or other security/authentication measure.

[0204] The vaporizer 100, 200 may be configured to minimize the impact of the YPD battery by providing an alert at a low power level for detection by youth use prevention beacon devices. The vaporizer 100, 200 may be configured to, by default, broadcast an alert with specific vaporizer information, manufacturer information, and/or user information for reception by youth use prevention beacons. Youth use prevention beacons may be configured to monitor and record the broadcast alert so that administrators can identify underage users and provide counseling services.

[0205] The vaporizer may be configured such that if the user misplaces or otherwise no longer has the vaporizer 100, 200 that was previously authenticated (and therefore is not currently subject to the youth use prevention device (YPD) features), or otherwise wishes to deauthenticate the vaporizer 100, 200, the user may unlink the device from the user's associated account such that the device may be reset to factory settings such that it includes the YPD features enabled. The YPD features may optionally be disabled via a beacon in response to the user re-pairing the device with a different account. If the lost (unlinked) device is re-paired with the user's age-verified application, the device may be reset to factory settings and the YPD features may be enabled again unless the device is locked.

[0206] In some implementations, the vaporizer 100, 200 may be configured to authenticate in connection with the hardware beacons 705 and the application beacons 805 described herein. For example, the user device may be provided with indications when the vaporizer 100, 200 is located within communication range of the hardware beacon and/or the application beacon. In some aspects, the hardware beacons and/or the application beacons may be implemented in high-risk areas for underage or unauthorized use (e.g., in schools, playgrounds, youth centers, etc.). In other aspects, authentication may include proximity detection based on location information. For example, the user device and/or the vaporizer 100, 200 can receive GPS or other location information indicating that the vaporizer 100, 200 and/or the user are within a proximity threshold with respect to a certain location (e.g., schools, playgrounds, youth centers, etc.). If the vaporizer 100, 200 is within the proximity threshold, the vaporizer 100, 200 can be blocked, or the user device can be configured to block the vaporizer 100, 200. In some aspects, the user can re-authenticate to unlock the vaporizer 100, 200 within the proximity threshold. In other aspects, unlocking or ensuring operation of the vaporizer 100, 200 by the user can be limited within the proximity threshold.

[0207] In addition to blocking the vaporizer 100, 200, the YPD and/or the application may be configured to receive inputs from the user indicating that the vaporizer 100, 200 is lost, stolen, that the vaporizer 100, 200 is being used by a minor, etc. The user may also notify retailers regarding suspected sales to minors, locations where underage use is suspected, etc. The user may provide any other relevant information in the user interface field (e.g., counterfeit, location, retailer, serial number, pod/cartridge ID, people using, etc.). FIGS. 14A-14F illustrate screen views of an exemplary user interface that may appear in an application installed on a communication device. The user interface screen views of FIG. 14A-14F relate to message generation features that can be used on a mobile device that does not have to be paired with the vaporizer. It should be understood that although these types of screens have a shape and size in accordance with the dimensions of a mobile device, such as a smartphone, the specified user interface functionality can be implemented on any computing device, such as, for example, a tablet computer, desktop or portable devices, etc.

[0208] FIG. 14A and FIG. 14B show views of screens by which a person can generate messages about a vaporizer (referred to in the view as a "device" that is used by an unauthorized user (e.g., a minor)). The views provide the ability to enter a serial number and include a data entry option (here a drop-down or scrolling menu, but not necessarily any type of input, including free text entry) for the person generating the message to indicate his or her job title or other identifying information. For use of this functionality in a school setting (e.g., if the features are used to prohibit the use of vaporizers by minors in schools), the job title may be "school administrator" or "teacher" or "counselor" etc. The view also includes fields for entering identifying information about the school and a "submit" user interface element to provide the ability to transmit the entered data to a server for analysis, aggregation, etc. The views may include a user interface element to provide guidance to the user on how to find the serial number of the device and, optionally, instructions for sending the device to a location where it can be analyzed to determine its origin.

[0209] In Fig. 14C and Fig. 14D, the screen views show an example of entering an invalid serial number. Here, the user interface may prompt the user to recheck the serial number, and if it is verified as correct with respect to the confiscated vaporizer, the user may be instructed to report it as a counterfeit vaporizer, which may initiate other steps. If the device is identified as counterfeit, the screen view of Fig. 14E may prompt the user to enter further available information, such as the place and time of purchase, etc., and may add an indication of the need to request that the user send the device to the manufacturer or some other location for analysis and data collection. Fig. 14F is an example of a "thank you" screen view.

[0210] Such reported information may be combined, aggregated, and analyzed to track and determine where unauthorized and/or unwanted use of the vaporizer occurs and what people and/or objects are involved. For example, upon receiving a threshold number of messages associated with a certain retailer or a certain location, the vaporizer system may be configured to disable capsules sold from the retailer during a given period of time, send an alert to the retailer, block/disable one or more vaporizers 100, 200, and/or take any other corrective action. In some aspects, the disabling and aggregation of data may be performed by one or more servers in communication with the application, the user device, and/or the vaporizer 100, 200.

[0211] The vaporization system may also combine the reported data with information obtained from individual vaporizers in the population, information regarding users and user profiles, usage profiles, user accounts, social media accounts, websites, crime reports, etc. The combined information may be presented on a dashboard or other user interface on the user device and/or in an application. The dashboard may be accessed by administrators, parents, police, security agencies to monitor underage use, unauthorized use, counterfeit products, etc. For example, the vaporization system may retrieve information from a school reporting underage use of vaporizers. The vaporizer system may correlate this information with information from social media (e.g., tweets, Facebook posts, hashtags, etc.) associated with underage use (e.g., social media accounts mentioning vaporizers, capsule flavors, usage, locations, retailers, etc.). This combined data may be further analyzed to find trends, patterns, and/or indicators of underage use. By detecting and tracking underage youth back to the source, schools, parents, retailers, manufacturers, etc. may take action, initiate programs, block vaporizers 100, 200, etc. to prevent underage use.

[0212] Retailers may also have access to a toolbar indicating underage use messages associated with products sold by the retailer and/or its affiliates (e.g., a serial number, distributor, or employee). The toolbar may include a map or graphical object showing the location where the messages originate, the data source for the messages, the number of messages, the time of the message, the reputation of the data source, other messages submitted by the user or the data source, messages on social media, comments associated with the message, and the like. Figs. 15A-15E and 16A-16H (described below) illustrate example user interfaces for tracking messages and other data indicating underage use, retailers, locations, comments, intelligence gathering activities, prevention actions, blocking of vaporizers 100, 200, and the like.

[0213] Figs. 15A-16H show exemplary screen views that may be displayed on any computing device to visually display results in the form of data based on data reported through the approaches explained herein, as well as other approaches. It should be understood that these screen views may be displayed on any type of computing device.

[0214] The screen view of Fig. 15A shows a map view that includes school labels with various overlay options that allow the user to select the types of data to be shown on the map relative to one or more locations. The overlay may include a heat map view that illustrates the frequencies of various occurrences determined based on the collected data. Data sources for collection may include, but are not limited to, school report cards (e.g., which may be entered through the screen views described above), retailer data (e.g., number of sales at a given location, tracking information regarding the sources of sales of confiscated vaporizers, etc.), social media data (e.g., data related to the estimated ages and demographics of social media users discussing vaporizers and/or their use relative to the estimated locations of those social media users), mystery shopper data (e.g., data on unauthorized or insufficiently authorized sales to undercover intelligence gatherers attempting to purchase vaporizers at retail locations, regulatory reports (e.g., from the FDA, etc.), etc. A screen view may also include a display sub-view that may display information regarding recently added data, trends, etc. Clicking on a given school location allows drilling down into specific types of data. Screens of this type can be used to develop strategies to prevent underage vaporizer use, for example by simply displaying geographic correlations between school confiscations, social media, illegal sales activity, etc.

[0215] The screen view of Fig. 15B shows an example of a news feed for comments about a given school regarding vaporizers and/or underage use of such devices. The screen view of Fig. 15C shows a summary of reports of confiscated devices for a selected school location. The screen view of Fig. 15D shows maps with heat maps but no other data, and the screen view of Fig. 15E shows maps with social media information highlighted.

[0216] FIGS. 16A-16H show screen views illustrating example features for data-driven functionality regarding the use of data, such as the data discussed above, in tracking illegal use and/or sales of vaporizers. The data source control field allows the user to explore data from various sources as location-based overlays on a map. In FIG. 16A, a fictional retail outlet is highlighted and social media comments are overlaid. FIG. 16B shows an example of additional displays associated with that fictional retail outlet, along with statistics (e.g., 6 confirmed devices that were confiscated, sold here). FIG. 16C shows a map view without the data overlays, FIG. 16D shows an option for drilling down to additional retailer messages, and FIG. 16E shows an example of data in such messages, including details on confiscated devices, etc. FIG. 16F-16H display social media data with estimated locations to allow for inferring correlations with retail outlet data and other data sources.

[0217] In addition to the data sources illustrated above that can be used with existing vaporizers that may not include connectivity features, other data sources provided by such connected vaporizers may further augment the features of the present invention. For example, geofences may be established around school locations and/or other locations where underage vaporizer use is considered problematic. Vaporizers that have connectivity features may be detected when they are in such areas to allow potential illegal public use points to be mapped. In other examples, an application running on mobile devices may be provided to teachers or other school personnel. Such applications may allow mobile devices to become mobile detectors of vaporizers that are in the vicinity of the mobile device. Collection of serial number data or other data from such vaporizers may allow for better tracking of where vaporizers used by teenagers and other underage users originate.

[0218] Fig. 8A illustrates a communication scheme 800 based on communication between evaporators 100A, 200A, 100B, 200B, 100C, 200C and user devices 805A and 805B. As shown in Fig. 8A, user devices 805A and 805B can be configured with a beacon application having a communication range 825A and 825B, respectively. As shown in more detail, evaporator 100A, 200A is located within the communication range 825A, and evaporators 100B, 200B, 100C, 200C are located within the communication range 825B.

[0219] In some aspects, the user device 805A executing the beacon application may transmit a broadcast message such that all of the evaporators in 825A must be turned off. For example, the evaporator 100A, 200A may receive a broadcast message from the user device 805A (e.g., via the wireless circuit 117, 217), and the controller 115, 215 may turn off one or more components of the evaporator 100A, 200A to block the device. In response to blocking, the evaporator 100A, 200A may notify the user of the evaporator 100A, 200A that the device is being blocked. In some aspects, the vaporizer 100A, 200A uses the terminal 115, 215 (e.g., light, tactile signal, sound, etc.) to indicate that the vaporizer 100A, 200A is being locked. In other aspects, the vaporizer 100A, 200A can transmit to the vaporizer application that the device is being locked, and the vaporizer application can display a notification to the user regarding the device being locked. The notification can comprise text, sound, graphic image, etc. on the computing device (e.g., smartphone) of the user. In some implementations, the user device 805A can transmit the notification to the vaporizer 100A, 200A and/or the vaporizer application.

[0220] In response to the blocking and/or notification, the vaporizer 100A, 200A may receive information associated with a user of the vaporizer 100A, 200A. In some aspects, the user may enter age/identification information into the vaporizer 100A, 200A, an application for the vaporizer, and/or a website associated with the vaporizer 100A, 200A. After receiving this information, the vaporizer 100A, 200A, the application for the vaporizer, and/or the website associated with the vaporizer 100A, 200A may determine the age of the user. In some aspects, determining comprises transmitting the received user information to a third-party server for analysis and receiving the determined age of the user. In other aspects, the processor of the vaporizer 100A, 200A, the application for the vaporizer and/or the website associated with the vaporizer 100A, 200A may be configured to determine the age of the user based on the received information. The determined age may be compared with an age threshold (e.g., an age limit of legal responsibility) to determine whether the user is authorized to use the vaporizer 100A, 200A. If the age threshold is met, the vaporizer 100A, 200A may be unlocked for use. In some aspects, the application for the vaporizer and/or the website associated with the vaporizer 100A, 200A may transmit a result of the comparison and/or an indication that the user meets the threshold to the vaporizer 100A, 200A. The controller 105, 205 may then unlock the evaporator 100A, 200A to enable operation of the evaporator 100A, 200A.

[0221] In some implementations, the beacon applications on the user devices 805A and 805B may be set to be available to certain authorized administrators (e.g., teachers, principals, etc.). Additionally, the beacon applications may also optionally be configured to operate only in certain geographic locations (e.g., schools, youth centers, playgrounds, etc.). In some aspects, the locations in which the beacon applications may operate may be controlled by authorities (e.g., police, school officials, regulators, vaporizer manufacturers, etc.) and may advantageously adapt to changing demographics or areas that are determined to have an increased risk for use by minors. In some implementations, the beacon applications may be aggregated or combined to form a combined or clear communication range 825 or a limited area for vaporizer use. In some aspects, user devices 805A and 805B can also share information regarding evaporators 100A, 200A, 100B, 200B, 100C, 200C within respective communication ranges 825A and 825B relative to an application beacon. This dynamic use of application beacons can also provide the ability to track or manage a large number of locations using application beacons instead of installing hardware beacons at each location.

[0222] Similar to the hardware beacons 705, in some implementations, the beacon applications of the user devices 805A and 805B may also be configured to track and/or report on vaporizers within the communication ranges 825A and 825B. For example, an application that communicates with the user devices 805A and 805B may be configured to display a list or graphical representation of the vaporizers within the communication ranges 825A and/or 825B. This tracking may allow an administrator of the application or facility (e.g., a school or teachers) to track which vaporizers are located within the area and if anyone is authorized to use within the area. For example, a principal, teacher, or chaperone of a school may monitor vaporizers present within communication range of one or more beacon applications to determine whether or not any vaporizers associated with a student of the school within said communication range are used or activated. In some aspects, the application may provide the ability for an authorized user of the beacon application to report any unwanted or unauthorized use of the vaporizer to authorities and/or the manufacturer. This functionality for generating complaints or reports may provide the ability for parents, teachers, authorities to improve prevention of unintended use by warning communities of unwanted or illegal use.

[0223] In some implementations, the user devices 805 may be configured to unlock the vaporizers 100, 200 within the communication range 825. For example, the vaporizers 100, 200 may be configured to be locked in locations outside the communication range 825, and the user device 805 communication may be configured to unlock the vaporizers 100, 200. Such an example may be used as designated "smoking areas" for areas in which the use of a vaporizer is generally prohibited (e.g., schools, airports, etc.).

[0224] Fig. 8B illustrates a flow chart of an example method 850 for blocking an evaporator, according to some example implementations. In some implementations, the method 850 may be performed by the evaporators 100, 200, the beacon 705, and/or the user devices 805A and/or 805B.

[0225] At step 852, the evaporator 100, 200 may determine whether or not it is within communication range of the second device. In some aspects, the determination is based on receiving communication, by the evaporator 100, 200, from a second device (e.g., the beacon 705, the user device 805A and/or the user device 805B) to block or disable the evaporator 100, 200. In some aspects, the communication may comprise a broadcast message from the beacon 705, the user device 805A and/or the user device 805B, transmitted in response to detecting, by the beacon 705, the user device 805A and/or the user device 805B, that the evaporator 100, 200 is within a communication range 725 relative to the beacon 705 and/or within communication ranges 825A or 825B. In other aspects, the communication may be transmitted in response to receiving a communication, via the beacon 705, from the evaporator 100, 200 within the communication range 725. Similarly, the communication may be transmitted in response to receiving a communication, via the user device 805A and/or 805B, from the evaporator 100, 200 within the communication range 825A and/or 825B. Additionally, an application for the evaporator on a smartphone associated with the evaporator 100, 200 may also receive a communication from the beacon 705, the user device 805A and/or the user device 805B.

[0226] At step 854, the evaporator 100, 200 may be blocked, in response to determining that the evaporator 100, 200 is within communication range of a second device (e.g., the beacon 705, the user device 805A and/or the user device 805B), the evaporator 100, 200 to disable the operation of the evaporator 100, 200. For example, the wireless circuit 107, 207 may receive the communication, and the controller 105, 205 may turn off one or more components of the evaporator 100, 200 to block/disable the operation of the evaporator 100, 200. In some aspects, an application for the evaporator on the smartphone may block the evaporator 100, 200 in response to the communication. For example, the application for the evaporator may transmit communication to the evaporator 100, 200 in response to receiving communication from the beacon 705, the user device 805A and/or the user device 805B. The communication with the evaporator 100, 200 may be configured to disable the operation of the evaporator 100, 200.

[0227] At step 856, the vaporizer 100, 200 may notify the user of the vaporizer 100, 200 regarding the fact that the device is being locked. In some aspects, the output 115, 215 may provide an indication that the vaporizer 100, 200 is being locked. For example, the output 115, 215 may display a red light, vibration, or icon indicating that the device is being locked. In some implementations, the vaporizer 100, 200 may communicate with an application for the vaporizer in order to notify the user regarding the fact that the vaporizer 100, 200 is being locked. For example, the vaporizer 100, 200 may communicate with an application for the vaporizer, and the application for the vaporizer may provide an indication that the device is being locked on the display of the smartphone or computing equipment. In some aspects, the indication may comprise text, audio, graphics, tactile signals, etc. to indicate that the evaporator 100, 200 is being blocked.

[0228] At step 858, the vaporizer 100, 200, the vaporizer application, and/or the web page may receive information associated with a user of the vaporizer. In some aspects, the vaporizer 100, 200, the vaporizer application, and/or the web page may indicate to the user a need to enter information in response to a notification to the user regarding the fact that the vaporizer 100, 200 is being locked. For example, the user may enter personal information and/or age information (e.g., date of birth, driver's license number, telephone number, biometric information, address, etc.) in the user interface of the vaporizer 100, 200, the vaporizer application, and/or the web page. In some aspects, the vaporizer application and/or the web page may be configured to transmit the received information to the vaporizer 100, 200.

[0229] At step 860, the vaporizer 100, 200, the vaporizer application and/or the web page may determine the age of the user based on the received information. In some implementations, the determination may be based on any of the authentication steps/methods described in this document. For example, the vaporizer 100, 200, the vaporizer application and/or the web page may transmit the received information to a third-party server to verify the identity data and age of the user. The third-party server may then respond to the vaporizer 100, 200, the vaporizer application and/or the web page with the determined age. In another example, the vaporizer 100, 200 and/or the vaporizer application may comprise an age verification module configured to compare and analyze the received information in order to determine the age of the user. Additionally, the vaporizer 100, 200, the vaporizer application, and/or the web page may scan the user's identification documents to determine the age of the user.

[0230] At step 862, the vaporizer 100, 200, the vaporizer application and/or the web page may unlock, based on the age of the user satisfying the threshold, the vaporizer 100, 200 to enable operation of the vaporizer 100, 200. For example, the age verification module of the vaporizer 100, 200 and/or the vaporizer application is configured to compare the determined age of the user with a threshold (e.g., the legal age of smoking) to determine whether the threshold is satisfied. In some aspects, the vaporizer application and/or the web page may transmit, in response to satisfying the threshold, a communication to the vaporizer 100, 200 to unlock the device. In some implementations, the beacon 705, the user device 805A and/or the user device 805B may be configured to transmit a second communication to the evaporator 100, 200 to unlock the device. For example, the beacon 705, the user device 805A and/or the user device 805B may receive a communication indicating that the evaporator 100, 200 completes the second authentication and is authorized for use within the communication range 725, 825A and/or 825B. The beacon 705, the user device 805A and/or the user device 805B may then provide a second communication with the evaporator 100, 200.

[0231] It may also be desirable to re-authenticate the user after the initial use of the vaporizer. In some aspects, when the user has used up all of the cartridges and vaporizable material, he or she may purchase additional accessories from an online or in-store retailer. It may be useful to provide a third authentication to help ensure that such accessories and cartridges for the vaporizer are used by the intended consumers and not by an unintended user (e.g., a minor child). In some implementations, the third authentication may be identical or similar to the first authentication when the user completes the initial purchase of the vaporizer. In some aspects, the processor 610 may perform the third authentication and/or locking in response to inputs received from the sensor module 660 or another component of the computing equipment 600.

[0232] In some aspects, a user may purchase accessories and/or cartridges for a vaporizer from an online retailer. The purchase may include a third authentication in order to verify the age of the purchaser. For example, in order to purchase accessories and/or cartridges for a vaporizer online, the user may be required to enter personal identification information, including age. The retailer may verify that the entered information is correct by accessing databases containing the user's personal identification information (e.g., the Ministry of Social Protection, the vehicle registration service, tax authority documents, etc.), or the retailer may enter into a contract with third parties that have access to this information and can verify that the entered consumer information is correct and the user meets any age threshold. Additionally, the retailer may have access to the user profile created during the first authentication, which is associated with the user. The third authentication may include verifying that the information entered during the third authentication matches the information entered during the first and/or second authentication, or other information associated with the user.

[0233] The third authentication may include a multi-step authentication process in which, after the user enters his or her information (e.g., contact information), the retailer, manufacturer, etc. sends a code to the user (e.g., via an application, text message, email message, etc.) for the user to enter before the purchase can be completed. If the user enters the correct code, the sale can be authorized, if not, the sale transaction can be completed. In some implementations, the information that the user uses can be stored to create a user profile if it is not created during the first or second authentications. The user profile can be stored in the vaporizer, in the application, on the server, or in another computing device.

[0234] In some aspects, a user may purchase accessories and/or cartridges for a vaporizer through an application for a vaporizer. The application may store a user profile in a database that verifies the age of the user. If the user profile is not created, the application may indicate to the user the need to enter required information in order to verify the age of the user. In some aspects, the application may send this information to a third party service provider in order to verify the age and/or identity of the user. In some implementations, the application may require a third authentication in order to allow the purchase of accessories and/or cartridges for a vaporizer. The third authentication may include verification that the fingerprints match the fingerprints stored in the user profile (e.g., entered during the first and/or second authentication). The third authentication may also include any single- or multi-step authentication process. For example, the application may send a message to an email address, a phone number, or other contact address. The message may include a code that the user must enter into the app to complete the purchase. The third authentication may also include any other biometric verification (e.g., voice verification, facial recognition, etc.).

[0235] In other implementations, a user may purchase accessories and/or vaporizer cartridges from a retailer in a store. The retailer may perform a third authentication to verify the age and/or identification data of the user to complete the purchase. For example, the retailer may visually inspect the user's identification document (e.g., driver's license, passport, etc.) to verify the age and/or identification data of the user. The retailer may also swipe or scan a bar code, QR code, or other encryption code of the identification document to read and verify the age and/or identification data of the consumer. In some implementations, the retailer may manually enter or scan the age/identification data into a computer application that verifies the identification data and/or age of the consumer. For example, a retailer may be equipped with a tablet computer, a laptop computer, a desktop computer or other computing device that runs an application associated with a vaporizer. A user or a retailer may register the user through the application and provide his/her personal identification and age information to the application. The application may then perform a third authentication to verify the age and/or identification data of the consumer. In some aspects, the application may exchange data with a vaporizer application database or a third-party system to complete the third authentication. The third authentication may include verifying that the information entered during the third authentication matches the information entered during the first and/or second authentication, or other information associated with the user.

[0236] In some implementations, the third authentication may include authentication in connection with the hardware beacons and beacon applications described herein. For example, the third authentication may be indicated when the vaporizer is located within communication range of the hardware beacon and/or beacon application. In some aspects, the hardware beacons and/or beacon applications may be implemented in retail stores that sell accessories and/or cartridges for the vaporizer.

[0237] In addition to or instead of the authentication schemes described herein, it may be desirable to periodically verify or re-authenticate that the user of the vaporizer is authorized to use the vaporizer equipment and/or accessories. It may also be desirable to ensure that the re-authentication is not excessively cumbersome or time-consuming in a manner that detracts from the user's perception. Accordingly, it may be advantageous to include a fourth authentication to verify age and/or identification data and unlock the vaporizer for use. In some aspects, the processor 610 may perform the fourth authentication and/or locking in response to inputs received from the sensor module 660 or another component of the computing equipment 600.

[0238] In some implementations, the application and/or vaporizer may communicate with a hardware key that performs periodic re-identification and/or authorization. In some aspects, the vaporizer and/or application may require the user to enter a code in order to unlock the vaporizer. For example, the code may be pre-programmed as part of the user profile and/or device profile. Additionally, the code may be randomly generated and sent to a contact number associated with the user for input by the user through the vaporizer and/or application. The code may include any combination of numbers, letters, gestures, sounds, speech, biometric features, and the like. For example, the code may include inputting the user's fingerprints on a fingerprint scanner of the vaporizer or computing equipment. The code may also include inputting the user's iris scan using an iris scanner of the vaporizer or computing equipment.

[0239] In some aspects, the computing equipment running the application for the vaporizer may be used to provide a fourth authentication. For example, the vaporizer may remain in a locked position if the vaporizer equipment is not within a certain proximity to the computing equipment running the application. In some aspects, the application may be running on the consumer's smartphone, and the vaporizer remains locked until the smartphone is within a proximity threshold with the vaporizer. In some aspects, the vaporizer and/or the computing equipment may detect proximity via Bluetooth, near field communication (NFC), Wi-Fi, ultrasound, ZigBee, RFID, cellular communication, or any other wireless communication.

[0240] In some implementations, the fourth authentication may include authentication in connection with the hardware beacons and beacon applications described herein. For example, the fourth authentication may be indicated when the vaporizer is located within communication range of the hardware beacon and/or beacon application. In some aspects, the hardware beacons and/or beacon applications may be implemented in high-risk areas for underage or unauthorized use (e.g., schools, playgrounds, youth centers, etc.). In other aspects, the fourth authentication may include proximity detection based on location information. For example, the application and/or vaporizer may receive GPS or other location information indicating that the vaporizer and/or user is within a proximity threshold relative to a certain location (e.g., schools, playgrounds, youth centers, etc.). If the vaporizer is within the proximity threshold, the vaporizer may be blocked, or the application may block the vaporizer. In some aspects, the user may re-authenticate to unlock the vaporizer within the proximity threshold. In other aspects, the user may be restricted from unlocking or ensuring operation of the vaporizer within the proximity threshold.

[0241] Any of the described authentication technologies and mechanisms may be used alone or in combination to provide protection against unintended and unwanted users of the vaporizer and/or vaporizer accessories.

[0242] As explained elsewhere in this document, any equipment described herein (e.g., vaporizers and/or an affiliated application) may include location services (GPS).

[0243] For example, a user who purchases vaporizer cartridges directly from a source may use an application to understand exactly how many cartridges the user has and how many they have in stock. The retailer may use this information to prompt the user to automatically order more when they are running low.

[0244] In any equipment described herein, the application and/or vaporizer may include GPS or may communicate with GPS to determine the location of the vaporizer. The location information may be used to inform the user of the nearest retailer from which additional cartridges can be purchased, use a location-based service for delivery, order via a smartphone (e.g., a usage tracking tool combined with an auto-refill tool), and/or inform the user of relevant local laws regarding the use of e-cigarettes and marijuana for smoking.

[0245] The location information may also be used to disable vaporizers that are determined to be positioned in or located within one or more areas in which the use of the vaporizer is not permitted. For example, specific areas or zones may be established, and if the vaporizer enters such an area or enters within a predetermined range of the area, the vaporizer may be automatically disabled or turned off after a warning is issued. Such areas may include, for example, a specified perimeter around schools or within specific locations (such as stores) that do not permit the use of the vaporizer. Additionally, specific locations in which the use of the vaporizer is not permitted may be established by one or more people (for example, a person's home). In order to establish areas/zones/locations, physical beacon devices (for example, beacons 705 and/or 805) may be installed to identify areas/zones/locations. When the vaporizer is within range of the beacons, the vaporizer should not be able to turn on or should turn off. Alternatively, geofencing can be used to establish areas/zones/locations in which the use of vaporizers is not permitted. When the vaporizer is paired with the user's phone or mobile device, or through the use of the vaporizer's location services, the vaporizer can be turned off when it is within any of the specified areas/areas/locations as geofences.

[0246] Examples of application software with many of the features described herein for use with one or more evaporators are described with reference to Figs. 10A-12J. Each of the user interface (UI) screens described herein in Fig. 10A-12J, can be generated by means of a user interface 650 of a user device 305, 805 and/or a computing equipment 600. For example, a user device 305 can comprise a memory 620 storing instructions for executing an application for an evaporator running on the user device 305. A processor 610 can execute these instructions and can generate exemplary UIs using a display 630 and/or a user interface 650. Exemplary UIs can also be generated based on user input received via the display 630 and/or the user interface 650. Exemplary UIs can also be generated based on communication with the evaporator 100, 200, a remote server 307, a beacon 705, other user devices 305, 805 and/or other devices. The communication may be received using the network interface 640 and/or the antenna 690 of the user device 305, the evaporator 100, 200 and/or any other device.

[0247] As noted herein, embodiments of the present invention include various methods of using vaporizers and vaporizer systems that include a device that communicates with the vaporizer. Fig. 9 illustrates a flow chart of a method 900 for authenticating a user of a vaporizer, according to some example implementations. In various implementations, the method 900 (or at least a portion thereof) can be performed by one or more of the vaporizer 100, the vaporizer 200, the user access device 305, the remote server 307, the computing equipment 800, other related equipment, and/or some portion thereof.

[0248] The method 900 may begin at operation 910, at which the equipment 900, for example, may lock the vaporizer to disable operation of the vaporizer. The method 900 may proceed to operation 920, at which the equipment 900, for example, may receive information associated with a user of the vaporizer. In some aspects, the information may include age and/or identifying information (e.g., date of birth, address, social security number, license number, etc.). The method 900 may proceed to operation 930, at which the equipment 900, for example, may determine the age of the user of the vaporizer. In some implementations, the vaporizer may determine the age or receive an age determination from a server and/or an application. The method 900 may proceed to a functional step 940, in which the equipment 900, for example, may unlock the vaporizer to activate the operation of the vaporizer based on a certain age of the user satisfying a threshold value (e.g., the age of legal responsibility).

[0249] FIGS. 10A-10E show a user interface (UI) for an application (application) that can be used with a vaporizer as described herein, including an initial or subsequent age/identity-based authentication protocol for accessing the vaporizer and/or affiliated data analysis, data collection, and data processing systems of the vaporizer, including the application itself. FIG. 10A illustrates a user interface for an application configured to allow a user to enter age/identity information in one or more UI fields, and FIG. 10B illustrates a user interface screen for an application that allows a user to scan the front or first side of an identification card (e.g., a driver's license). FIG. 10C illustrates a user interface screen for an application that allows a user to scan the back or second side of an identification card. FIG. 10D illustrates a user interface screen for an application that indicates that the application is verifying entered/scanned user information. Fig. 10E illustrates a user interface screen for an application that indicates that the user is verified/authenticated to use the vaporizer.

[0250] Fig. 11A-11B illustrate UI screens that can be used as part of an application interface for locating, checking the reachability of, and/or checking the status of an evaporator. In Fig. 11A, the UI includes a name associated with the evaporator, a button for determining the location of the evaporator, and a button for checking the reachability of the evaporator. Fig. 11B shows the UI screen of Fig. 11A with an indication that the evaporator is being blocked.

[0251] Figs. 12A-12J illustrate UI screens that can be used as part of an interface of an application (e.g., connected to a smartphone) that can be used with a vaporizer as described herein, including an initial or subsequent beacon operation protocol for accessing the vaporizer and/or affiliated data analysis, data collection and data processing systems of the vaporizer, including the application itself within communication range of the beacon. Fig. 12A illustrates a user interface for an application configured to allow a user to create an account or log in to a user account. Fig. 12B illustrates a user interface screen for an application that enables a user to enter information (e.g., an email address, a password, etc.) in one or more fields to create an account. Fig. 12C illustrates a user interface screen for an application that represents an example input into UI fields to create an account. Fig. 12D illustrates a UI screen for an application that enables a user to send an invitation to other users to create an account or skip the process. Fig. 12E illustrates a UI screen for an application that indicates that the application is searching for beacons within communication range of the application and/or a beacon. Fig. 12F illustrates a UI screen for an application that indicates that the application finds a beacon within communication range of the application and/or a beacon and includes a field for assigning a name to the beacon. Fig. 12G illustrates a UI screen for an application that indicates that the application finds a beacon within communication range of the application and/or a beacon that is called a "girl's bathroom four". Fig. 12H illustrates a user interface screen for an application that indicates that it includes a map showing an indication of beacon locations and also includes a list of indicated beacons with the names and status of the listed beacons. Fig. 12I illustrates a user interface screen for an application that indicates that one beacon from a list of beacons has been selected and provides a user with the option to collect data or clean the vaporizer that is detected by the selected beacon (e.g., a girl's bathroom quad). Fig. 12J illustrates a user interface screen for an application that indicates options for the user to select after selecting the collection of data in Fig. 12I. The options include assigning the collection of data to a person (e.g., yourself, Jane Smith, Sharon Kim, Dave Rodriguez).

[0252] Any of the applications described herein may also be adapted for use with detection, including automatic detection, for a cartridge and/or vaporizable material. The application may provide instructions for detection/identification, or the operation of the application may be automatically adjusted/customized based on the detected cartridge, beacon, second device, etc.

[0253] Age verification . Figs. 17-31 illustrate example user interfaces that may appear in an application installed on a communication device in communication with a vaporizer (e.g., as part of an "app" or other software on a user's mobile device). The user interfaces of Figs. 17-31 relate to age verification features that may provide benefits in providing data, as well as vaporizer-specific controls to prevent unauthorized and/or underage use, purchase, etc. of the vaporizer. In one implementation, the vaporizer may be configured to initiate the functionality only upon successful completion of the age verification process via the user interface. In another implementation, the vaporizer may be configured to disable in response to failure to complete the age verification process within a threshold duration after purchase.

[0254] The screen view of the application of Fig. 17 or a similar approach may be used to indicate to the user of the vaporizer the need to implement an age verification feature to use the device. In one example, the user may be indicated the need to undergo an age verification process by agreeing to undergo age verification. Alternatively, in response to the user "explicitly opting out" of the age verification process and/or failing to reach a threshold age, the vaporizer may be configured to disable the functionality. The threshold age may be based on consumer laws in the user's geographic region and/or other factors.

[0255] The screen views of FIGS. 18-21 show a view that may be presented to the user after selecting and agreeing to an age verification feature. This screen may prompt the user to enter personal user information (e.g., the user's name and phone number). In some implementations, other user information may be required, such as a social security number, driver's license, identification card, credit history, facial recognition, and the like. 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, the user's name and phone number may be verified using two-factor authentication (e.g., receiving a code via a text message). The user may then receive an authentication message containing a unique or "one-time" numeric and/or alphanumeric security code, as shown in FIG. 22.

[0256] As shown in Fig. 23 and 24, the user may be instructed to enter a security code that he/she accepts. After the user enters the security code, the application screen view of Fig. 17 or a similar approach may be used to convey that the user information is being verified. 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., "about a minute" and/or other durations). In response to successful verification of the user information, the user may be notified via the application screen view of Fig. 26 or a similar approach. However, if the user information cannot be verified, the user may be notified via the application screen view of Fig. 27 or a similar approach, and the user may be instructed to provide additional user information in order to continue the age verification process.

[0257] In response to the unverified user continuing the verification process, the screen views of Figs. 28-31 or a similar approach may be used to indicate to the user the need to provide documentation with user information, such as a valid driver's license, state-issued identification card, passport, social security number and/or other information. The application may be configured to access one or more features of the user device, such as a camera feature, to capture, scan or otherwise document user information. In one implementation, facial recognition may be used to verify and authenticate the photo identification provided by the user. In response to submitting documentation with user information and/or images, the screen view of the application of Fig. 31 or a similar approach may be used to convey that the user information is being verified. In some implementations, an estimated verification time duration and/or a status bar may be displayed. In response to successful verification of the user information, the user may be notified via the application screen view of Fig. 26 or a similar approach.

[0258] After the age verification process is completed, the vaporizer may be configured to be activated by indicating, via the application screen view of Fig. 32 or a similar approach, one or more user actions, such as shaking the vaporizer and/or other user inputs. Confirmation of activation of the vaporizer may be provided as shown in Fig. 33.

[0259] In some implementations of the present invention, in response to a user exiting and returning to the application, a screen view may be provided, such as shown in Fig. 34. A new user may initiate an age verification process, or a verified returning user may "Log In" to his/her associated user account. The logged in, verified user may then access additional features of the application, including a process for pairing the vaporizer with a mobile or other user device, as shown in Fig. 35. A quick start guide and/or other onboarding instructions (e.g., user manuals and/or tutorials designed to familiarize the user with the vaporizer) may be provided through the application to the logged in, verified user. Additional training and habit management programs may also be provided, as described in more detail herein.

[0260] In some implementations, after activation, the device may periodically re-verify in the background with little or no action required from the user. For example, the vaporizer may need to connect to the user device periodically (e.g., once a week, every two weeks, and/or other durations), as shown in Fig. 36. In some implementations, the age verification process may only be required in response to inserting specific types of cartridges (e.g., flavor cartridges) into the vaporizer.

[0261] FIGS. 37-39 describe one or more methods of age verification to ensure age-appropriate use of a vaporizer. As shown in FIG. 37, a first purchase of a device made in a store may require one or more of the following steps to verify age and/or activate the device: (1) purchasing a deactivated device in a store; (2) unpacking and downloading a mobile application; (3) passing age verification against public documents; (4) activating the vaporizer by pairing with the user device via Bluetooth and/or other connection; and/or (5) automatically re-verifying the device. A subsequent purchase of a device made in a store may require one or more of the following steps to verify age and/or activate the device: (1) purchasing a deactivated device in a store; (2) activating the vaporizer by pairing with the user device via Bluetooth and/or other connection; and/or (3) automatically re-verifying the device. The first purchase of a device made online may require one or more of the following steps to verify age and/or activate the device: (1) creating and completing age verification for an online account and making an online purchase; (2) receiving a deactivated device, unpacking and downloading the mobile application; (3) logging into the application account using the online account credentials; (4) activating the vaporizer by pairing it with the user device via Bluetooth and/or other connection; and/or (5) automatically re-verifying the device.

[0262] As shown in Fig. 38A, another embodiment of the age verification method to ensure age-appropriate use of a vaporizer may include one or more of the following steps for age verification and/or unlocking the vaporizer: (1) unpacking the vaporizer and/or cartridge(s); (2) downloading an application; (3) passing age verification; (4) unlocking the vaporizer by pairing with a user device via Bluetooth and/or other connection; and/or (5) automatically re-verifying the device. In yet another embodiment, as shown in Fig. 38B, the age verification method to ensure age-appropriate use of a vaporizer may include one or more of the following steps for age verification and/or unlocking the vaporizer: (1) unpacking the vaporizer and/or cartridge(s); (2) reading provided youth use prevention information; (3) downloading an application; (4) passing age verification against public documents; (5) Activating the vaporizer by pairing it with the user device via Bluetooth and/or other connection.

[0263] As shown in Fig. 39, another embodiment of the age verification method for ensuring age-appropriate use of the vaporizer may include one or more of the following steps for age verification through a user interface: (1) providing a welcome screen; (2) providing adaptation information and instructions for obtaining age verification information; (3) verifying user information using authentication; and/or (4a) providing a notification regarding successful age verification; or (4b) requesting additional age verification information.

[0264] After the user passes age verification and their associated vaporizer is unlocked using one or more of the methods described herein, the user may be required to periodically re-authenticate themselves. Re-authentication may be required (e.g., based on firmware in the vaporizer) once a day, per a specific number of days, per week, per a specific number of weeks, per month, per a specific number of months, etc. In some implementations, the vaporizer may require re-authentication once every two weeks. Re-authentication may occur through the use of a user device running a specific application that allows communication with the vaporizer, such as described herein. For example, re-authentication may require the user to periodically electronically pair (e.g., via Bluetooth) their vaporizer with the user device through the application. In some aspects, the period of time required for re-authentication may begin after the vaporizer detects that it is no longer paired with the user device, may restart each time the vaporizer detects that it is paired with the user device, may start regardless of the last pairing (e.g., restart based on a specific re-authentication procedure implemented through the execution of the application), etc.

[0265] In some implementations, after a user passes age verification using one or more of the methods described herein, an application running on the user device may store credentials for the user indicating that the user passes age verification (e.g., user account information with a specific value for the "age verification passed" field associated with the user account). In some implementations, the credentials may be created as part of a registration process that is implemented using an application running on the user device. In some implementations, the user device may receive the credentials, or some portion thereof, from a server after the initial account establishment and/or age verification of the user. For example, if a user passes age verification using a web browser, a dedicated kiosk, two-step verification (e.g., via email, SMS, etc.) and/or other methods external to an application running on the user device, then a server configured to communicate with the user device may transmit the credentials, or some portion thereof, to the user device. In some aspects, the user may be allowed to (re-)authenticate him/herself for the purpose of unlocking the user device only if the credentials stored on the user device indicate that the user passes age verification. In some aspects, devices purchased using the user's age-verified account may be delivered activated, but may require (re-)authentication within a specified period of time.

[0266] In some aspects, the user may be limited to purchasing a specific number of vaporizers and/or cartridges for use with the vaporizer during a specific time. For example, in some aspects, the user may be limited to purchasing more than one, two, three, etc. devices during a month (e.g., a calendar or rolling month based on the last purchase of the vaporizer). In some aspects, the user may be limited to purchasing more than ten, fifteen, twenty cartridge sets, etc. (e.g., with two, three, four, five, etc. cartridges per set) during a month (e.g., a calendar or rolling month based on the last purchase of a cartridge set). In some implementations, the user's purchases may be tracked through more than one source. For example, a user's aggregate purchases over a specific period of time may be determined based on data received via the user's device(s), web browser(s), kiosk(s), retail store(s) (e.g., via point-of-sale systems), online retailer(s), server(s) capable of communicating with one or more of the foregoing, etc. In order to track a user's aggregate purchases, the user may be required to use an age-verified user account for each purchase.

[0267] To prevent a user from creating multiple accounts, the user may be limited to one account for each set of unique credentials (e.g., unique information that identifies only one individual). To determine whether a set of credentials is unique, the system (e.g., through a server) may require the user to provide a valid name, date of birth, permanent address, and the last four digits of a social security number. This information may be verified through a third party and/or cross-checked with publicly available documents to confirm that the person is of legal age in their location/jurisdiction. If the user's public documents do not match, or the user does not want to provide their social security number, the user may be required to upload or swipe (through a card reader) a valid government-issued identification document for matching. In some aspects, the user 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 provide a code sent to the phone number before continuing. In some aspects, the code may be sent to the phone only when the phone number is known to be associated with a person of legal age to purchase a vaporizer. In some aspects, the SIM card associated with the phone number may be verified, and the user may be allowed to use the code sent to the phone number only when the SIM card is verified (e.g., when the SIM card is associated with the provided phone number). Additionally or alternatively, the user may be required to upload or swipe (via a card reader) a valid government-issued identification document and scan his or her face via a facial recognition interface (e.g., provided via an application running on the user device used to create the account). To prevent a user from using multiple accounts from different users, the user may be required to verify himself/herself each time he/she uses the user account for a purchase, for example, through electronic verification of an identity document (e.g., a driver's license), facial recognition, etc.

[0268] In some implementations, a kiosk or other device may be configured to activate the device. For example, a kiosk may be configured to receive user input to perform age verification of the user according to the methods described herein. After the user passes age verification, the kiosk may provide the user with a receipt having a code (e.g., a bar code, a QR code, a numeric value, an alphanumeric string, etc.) for presentation to a merchant. The merchant may scan or enter the code into a system that indicates what the user can purchase before allowing the store to sell vaporizers or cartridges to the user. In some aspects, the kiosk may be connected (e.g., physically, electronically, and/or in communication) to a vending machine with vaporizers and/or cartridges. After the user passes age verification and makes a purchase, the vending machine may dispense the purchase to the user.

[0269] In some aspects, vaporizers stored in a vending machine may be deactivated and/or require authentication (e.g., via one or more device pairing methods described herein) before a user can use the vaporizer. In some aspects, the vaporizer may not be capable of wireless communication with a user device. Accordingly, activation of such vaporizers may be prevented based on information stored regarding the device, such as a register (e.g., 1 bit) in the vaporizer. To activate the device, the user may be required to place the device in an interface that communicates with the kiosk. After the user passes age verification and the vaporizer is placed in the interface, the kiosk may be configured to change the register value to unlock the device. In some implementations, the interface may include a cradle and/or a cable with an electronic interface capable of communicating with the vaporizer via an interface built into the vaporizer (e.g., via USB or another data interface, such as one or more pins). Once the device is unlocked, a serial number or other unique identifier associated with the vaporizer, activation date, purchase date, etc., may be associated with a user account for tracking purposes. Although a kiosk is described, any device capable of communicating with the device without using wireless communication may be used.

[0270] In some aspects, the user may be allowed to purchase vaporizers and/or cartridges beyond a specified limit, but the vaporizers and/or cartridges may be held until the current period of time during which the user exceeds the specified limit has expired. For example, if the user is limited to purchasing more than two vaporizers per month, and the user attempts to purchase a third vaporizer during the same month (a calendar month or a rolling month based on the purchase of the first vaporizer), then the vaporizer may be held until the month is completed. When the month is completed, the vaporizer may be released to the user (e.g., automatically shipped). Additionally or alternatively, the user may be limited to a number of activations per specified period of time (e.g., two activations per month). The activations may be tracked by a server configured to communicate with a plurality of devices configured to activate the vaporizer (e.g., user devices running a dedicated application, etc.). In an exemplary implementation, if a user is limited to activating more than two vaporizers per month, and the user attempts to activate a third vaporizer during the same month (a calendar month or a rolling month based on the activation of the first vaporizer), then a device configured to activate the vaporizer may not allow the user to activate the device until the month is over. The device may notify the user that he or she has exceeded his or her activation limit and/or provide the user with information indicating when he or she may activate the vaporizer. In the event that the user returns the device, the user's account may be credited with additional activations during the specified time period(s).

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

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

[0273] In some aspects, the requirements for satisfying age verification may additionally or alternatively be based on GPS information. For example, based on a certain GPS location, the user may be instructed to submit specific documents for age verification that are sufficient to establish identity based on the jurisdiction covering the GPS location, such as either a driver's license or a passport, only a passport, etc.

[0274] Another useful implementation of the identity verification system may be point of sale and/or cartridge tracking information. The location and/or date of when the cartridge was originally purchased, as well as the manufacturer's information, are useful from both a legal and security perspective, as well as from a marketing perspective. For example, if a cartridge is found to be in the possession of a minor, the cartridge purchase information may identify whether the manufacturer does or does not perform age verification at the point of sale, or if the cartridges are purchased by an adult and provided to the minor.

[0275] When a feature or element is referred to herein as being "in" another feature or element, it may be directly within the other feature or element, or intervening features and/or elements may also be present. In contrast, when a feature or element is referred to as being "directly within" another feature or element, intervening features or elements are not present. It should also be understood that when a feature or element is referred to as being "connected," "attached," or "connected" to another feature or element, it may be directly connected, attached, or connected to the other feature or element, or intervening features or elements may be present. In contrast, when a feature or element is referred to as being "directly connected," "directly attached," or "directly coupled" to another feature or element, intervening features or elements are not present.

[0276] Although described or shown with respect to a given example, the features and elements described or shown in this manner may be applicable to other implementations of the present invention. Those skilled in the art will also appreciate that references to a structure or feature that is "adjacent" to another feature may have portions that overlap or underlie the adjacent feature.

[0277] The terminology used herein is for the purpose of describing particular implementations and implementations only, and is not intended to be limiting. For example, as used herein, the singular forms are intended to include the plural forms as well, unless the context clearly dictates otherwise. It should be further understood that the terms "comprises" and/or "comprising," as used in this detailed description and in the claims, specify the presence of the recited features, steps, operations, elements, or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, or groups thereof.

[0278] In the descriptions herein and in the claims, phrases such as "at least one of" or "one or more of" may appear followed by a conjunctive list of elements or features. The term "and/or" may also appear in a list of two or more elements or features. Unless otherwise implicitly or clearly inconsistent with the context in which it is used, such phrase is not intended to mean any of the recited elements or features alone or any of the recited elements or features in combination with any of the other recited elements or features. For example, the phrases "at least one of A and B"; "one or more of A and B"; and "A and/or B" are intended to mean "A alone, B alone, or A and B together." A similar interpretation is also intended for lists including three or more elements. For example, the phrases "at least one of A, B, and C"; "one or more of A, B, and C"; and "A, B and/or C" are intended to mean "A only, B only, C only, A and B together, A and C together, B and C together, or A and B and C together." The use of the term "based on" in this document and in the claims is intended to mean "based at least in part on," so that an unrecited feature or element is also permissible.

[0279] Spatially relative terms such as "under," "below," "lower," "above," "upper," and the like may be used herein for ease of description to describe the relationship of one element or feature to another element(s) or feature(s) as illustrated in the drawings. It should be understood that spatially relative terms are intended to cover various orientations of the device in use or operation, in addition to the orientation illustrated in the drawings. For example, if the device in the drawings is turned over, elements described as "under" or "below" other elements or features would then be oriented "above" the other elements or features. Thus, the exemplary term "under" may cover both an above and below orientation. The device may be oriented in other ways (rotated 90 degrees or in other orientations), and spatially relative descriptors used herein are interpreted accordingly. Similarly, the terms "up", "down", "vertical", "horizontal", etc. are used in this document for explanatory purposes only, unless otherwise expressly stated.

[0280] Although the terms "first" and "second" may be used herein to describe various features/elements (including steps), these features/elements should not be limited by these terms unless the context indicates otherwise. These terms may be used to distinguish one feature/element from another feature/element. Thus, the first feature/element explained below may be referred to as the second feature/element, and similarly, the second feature/element explained below may be referred to as the first feature/element, without departing from the teachings provided herein.

[0281] In this detailed description and in the claims below, unless the context otherwise requires, the word "comprise" and variations such as "comprises" and "comprising" mean that various components can be used together in methods and articles of manufacture (e.g., in structures and equipment including the apparatus and methods). For example, the term "comprising" should be understood to imply the inclusion of any claimed elements or steps, but not the exclusion of any other elements or steps.

[0282] As used herein in the detailed description and claims, including when used in the examples, and unless otherwise expressly indicated, all numbers may be read as if preceded by the word "about" or "approximately," even if the term is not explicitly shown. The phrase "about" or "approximately" may be used when describing an absolute value and/or position to indicate that the value and/or position described is within a reasonably expected range of values and/or positions. For example, a numerical value may have a value that is +/- 0.1% of a stated value (or range of values), +/- 1% of a stated value (or range of values), +/- 2% of a stated value (or range of values), +/- 5% of a stated value (or range of values), +/- 10% of a stated value (or range of values), etc. Any numerical values given herein should also be understood to include about or approximately that value, unless the context indicates otherwise. For example, if the value "10" is disclosed, then "about 10" is also disclosed. Any range of numerical values set forth herein is intended to include all subranges included therein. It should also be understood that when a value that is "less than or equal to" a value is disclosed, "greater than or equal to the value" is also disclosed, and possible ranges between the values, as would be properly understood by those skilled in the art. For example, if the value "X" is disclosed, "less than or equal to X" is also disclosed, as well as "greater than or equal to X" (e.g., where X is a numerical value). It should also be understood that in this application, data is provided in a number of different formats, and that the data represents end points and start points and ranges for any combination of data points. For example, if a specific data point of "10" and a specific data point of "15" are disclosed, it should be understood that greater than, greater than or equal to, less than, less than or equal to, and equal to 10 and 15 are considered to be disclosed, as is between 10 and 15. It should also be understood that each unit between two specific units is also disclosed. For example, if 10 and 15 are disclosed, then 11, 12, 13, and 14 are also disclosed.

[0283] Although various illustrative implementations are described herein, any of a number of changes may be made to the various implementations without departing from the teachings herein. For example, the order in which the various described method steps are performed may often be varied in alternative implementations, and in other alternative implementations, one or more method steps may be omitted altogether. Optional features of various implementations of the apparatus and system may be included in some implementations and not included in others. Accordingly, the foregoing description is provided primarily for exemplary purposes and should not be interpreted as limiting the scope defined by the claims.

[0284] One or more aspects or features of the invention described herein may be implemented in a digital electronic circuit, an integrated circuit, a specially designed application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), computer hardware, firmware, software, and/or a combination of the foregoing. These various aspects or features may include implementation in one or more computer programs that can be executed and/or interpreted for a programmable system that includes at least one programmable processor, which may be special-purpose or general-purpose, coupled to receive data and instructions from and transmit data and instructions to a data storage system, at least one input device, and at least one output device. The programmable system or computing system may include client-servers. The client and server are generally remote from each other and typically communicate via a communication network. The relationship between the client and the server is carried out on the basis of computer programs running on the corresponding computers and having a client-server relationship with each other.

[0285] These computer programs, which may also be referred to as "programs," "software," "applications," "applications," "components," or "code," include machine instructions for a programmable processor and may be implemented in a high-level procedural language, an object-oriented programming language, a functional programming language, a logic programming language, and/or an assembly/machine language. As used herein, the term "machine-readable medium" means any computer program product, hardware, and/or device, such as, for example, magnetic disks, optical disks, storage, and programmable logic devices (PLDs), used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives the machine instructions as a machine-readable signal. The term "machine-readable signal" means any signal used to provide machine instructions and/or data to a programmable processor. The machine-readable medium may store such machine instructions in a non-volatile manner, such as a non-volatile semiconductor memory device or a magnetic hard disk, or any equivalent storage medium. The machine-readable medium may alternatively or additionally store such machine instructions in a volatile manner, such as a processor cache or other random access memory device associated with one or more physical processor cores.

[0286] In order to provide interaction with a user, one or more aspects or features of the subject matter of the invention described herein may be implemented on a computer having a display device, such as, for example, a cathode ray tube (CRT) or a liquid crystal display (LCD) or a light emitting diode (LED) monitor for displaying information to a user, and a keyboard and pointing device, such as, for example, a mouse or trackball, through which a user can enter input into the computer. Other types of devices may also be used to provide for interaction with a user. For example, feedback sent to the user may be any form of sensory feedback, such as, for example, visual feedback, acoustic feedback or haptic feedback; and input from the user may be received in any form, including, but not limited to, acoustic, speech or haptic input. Other possible input devices include, but are not limited to, touch screens or other touch devices such as single or multi-point resistive or capacitive touch panels, speech recognition hardware and software, optical scanners, optical pointers, digital image capture devices and associated interpretation software, and the like.

[0287] The examples and illustrations included herein show, by way of illustration and not limitation, specific implementations in which the invention may be practiced. As mentioned above, other implementations may be used and subtracted from them, and structural and logical substitutions and changes may be made without departing from the scope of this disclosure. Such implementations of the technical solution corresponding to the present invention may be referred to herein individually or collectively by the term "invention" merely for convenience and without the intention of intentionally limiting the scope of this application to any one invention or inventive concept where more than one is actually disclosed. Thus, although specific implementations are illustrated and described herein, any arrangement calculated to achieve the same purpose may be substituted for the specific implementations shown. This disclosure is intended to cover any and all adaptations or variations of the various implementations. Combinations of the above implementations and other implementations not specifically described herein should become apparent to those skilled in the art upon review of the above description.

Claims (29)

1. A method of operating an evaporation device comprising the steps of: determining by means of one or more processors whether the evaporation device is within the communication range of a radio beacon configured to disable evaporation devices within the communication range of the radio beacon, wherein the radio beacon is configured to transmit one or more broadcast messages while the radio beacon is within specific geographic locations, wherein the one or more processors are configured to respond to the receipt of a broadcast message from the radio beacon by at least disabling the evaporation device; blocking, by means of one or more processors, the evaporation device to deactivate the operation of the evaporation device in response to the evaporation device being within the communication range of the radio beacon; receive, through one or more processors, information relating to a user of the evaporation device; determine, by means of one or more processors and on the basis of the received information, the age of the user; and in response to a determination by one or more processors that the age of the user satisfies the threshold, bypassing the broadcast message received from the beacon to unlock the vaporizer and activate operation of the vaporizer. 2. The method according to claim 1, wherein the evaporation device is blocked by at least cutting off the power supply to the heating element of the evaporation device. 3. The method of any one of the preceding claims, further comprising the step of displaying in a user interface associated with the radio beacon a list or graphical representation of evaporation devices within the communication range of the radio beacon. 4. The method of any one of the preceding claims, further comprising the step of notifying a third party of the evaporation device in response to the evaporation device being within communication range of the radio beacon. 5. The method according to any of the preceding claims, wherein said receiving information comprises receiving user input through user interaction with a user interface. 6. The method according to any one of the preceding paragraphs, wherein said information comprises at least one of the following: date of birth, address, biometric information, driver's license number, passport number, birth certificate, social security number, and national identification card. 7. The method according to any of the preceding claims, further comprising the step of providing an indication that the evaporation device is blocked. 8. A method according to any of the preceding claims, wherein unblocking the evaporation device comprises the steps of: generate a code to unlock the evaporation device; transmit the code to the user; accept code input; activate the evaporation device in response to receiving the code. 9. An evaporation device comprising: at least one processor; at least one memory device storing instructions which, when executed by at least one processor, instruct the evaporation device to at least: determine whether the evaporation device is within the communication range of a radio beacon configured to disable evaporation devices within the communication range of the radio beacon, wherein the radio beacon is configured to transmit one or more broadcast messages while the radio beacon is within specific geographic locations, wherein the one or more processors are configured to respond to the receipt of a broadcast message from the radio beacon by at least disabling the evaporation device; block the evaporation device to disable the operation of the evaporation device in response to the evaporation device being within the communication range of the radio beacon; receive information relating to the user of the vaporizer device; and determine the user's age based on the information received; and in response to determining that the user's age meets the threshold, bypass the broadcast message received from the beacon to unlock the vaporizer and activate the operation of the vaporizer. 10. The evaporation device according to claim 9, wherein the evaporation device is blocked by at least disconnecting the power supply to the heating element of the evaporation device. 11. The evaporation device of claim 9, wherein the evaporation device is further instructed to at least receive user input through user interaction with the user interface. 12. An evaporation device according to any one of claims 9 to 11, wherein said information comprises at least one of the following: date of birth, address, biometric information, driver's license number, passport number, birth certificate, social security number, and national identification card. 13. An evaporating device according to any one of claims 9 to 12, wherein the evaporating device is additionally instructed to at least provide an indication that the evaporating device is blocked.

Images