Vaporizer control

Abstract

To provide a computer-implemented method for operating an e-vaporizer.SOLUTION: The method includes determining whether a vaporizer 100, 200 is within a communication range of a second device 305. The method further includes locking the vaporizer 100, 200 in response to the vaporizer 100, 200 being within the communication range. The method further includes receiving information associated with a user of the vaporizer 100, 200. The method further includes determining an age of the user based on the received information, and unlocking, by one or more processors and based on the age of the user satisfying a threshold, the vaporizer in order to activate the operation of the vaporizer 100, 200.SELECTED DRAWING: Figure 5

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims priority to U.S. Provisional Patent Application No. 62 / 609,289, titled "Vaporizer Device Locking", filed on December 21, 2017; U.S. Provisional Patent Application No. 62 / 690,947, titled "Connected Vaporizer Device System", filed on June 27, 2018; U.S. Provisional Patent Application No. 62 / 745,959, titled "Vaporizer Device Locking", filed on October 15, 2018; and U.S. Provisional Patent Application No. 62 / 760,918, titled "Connected Vaporizer Device System", filed on November 13, 2018, the entire disclosures of which are incorporated herein by reference.

[0002] Technical Field The devices, devices, systems, and methods described herein relate to vaporization devices such as electronic vaporizers, as well as methods of using such devices, controlling methods, and / or verifying methods of authorized use, manufacturing methods, etc.

Background Art

[0003] [[ID=十九]] [[ID=二十]]Vaporization devices, which may also be referred to as electronic vaporizer devices, e - vaporizer devices, electronic cigarettes or e - cigarettes, or simply "vaporizers", can be used to supply vapor containing one or more active ingredients by inhalation of the vapor by a user of the vaporization device. Electronic vaporizer devices are becoming increasingly popular for use in prescription medicine, drug delivery, as well as the consumption of tobacco and other plant - based smokable substances. Among other technical issues related to vaporization devices, the use of such devices by minors or other unauthorized use can cause a wide range of problems. Preventing such use can present many challenges.[[ID=二十一]] [[ID=二十二]]

Summary of the Invention

Means for Solving the Problems

[0004] [[ID=二十九]] The aspects covered by this document relate to the management of operation (e.g., one or more settings or operating parameters of a vaporizer).

[0005] Some embodiments relate to methods implemented on a computer for operating a vaporizer. Such methods include, by having one or more processors determine whether a vaporizer is within communication range of a second device, and, depending on whether the vaporizer is within communication range, lock or unlock the vaporizer. The method further includes, by having one or more processors receive information associated with the user of the vaporizer. The method further includes, by having one or more processors determine the user's age based on the received information. The method further includes, by having one or more processors unlock the vaporizer for activation of its operation based on the user's age meeting a threshold.

[0006] In another embodiment, a vaporizer is provided, which includes at least one processor. The vaporizer further includes at least one memory for storing instructions, which, when executed by the at least one processor, cause the vaporizer to determine at least whether the vaporizer is within communication range of a second device. The vaporizer further causes the vaporizer to lock in order to deactivate its operation, depending on whether the vaporizer is within communication range. The vaporizer further causes the vaporizer to receive information associated with the user of the vaporizer and to determine the user's age based on the received information. The vaporizer further causes the vaporizer to unlock in order to activate its operation, based on the user's age which meets a threshold.

[0007] Embodiments of this Subject Matter may include, but are not limited to, methods consistent with those provided herein, and articles including tangibly embodied machine-readable media capable of operating one or more machines (e.g., computers) such that operations resulting in one or more of the features described herein being performed. Similarly, computer systems may include one or more processors and one or more memories coupled to one or more processors. Memories, which may include non-temporary computer-readable or machine-readable storage media, may include encoding, storing, etc., one or more programs causing one or more processors to perform one or more of the operations described herein. Methods implemented on a computer consistent with one or more embodiments of this Subject Matter may be implemented by one or more data processors present in a single computing system or a multi-computing system. Such multi-computing systems may be connectable and exchange data and / or commands or other instructions, etc., via one or more connections, including but not limited to connections via networks (e.g., the Internet, a wireless wide area network, a local area network, a wide area network, a wired network, etc.), direct connections between one or more of the multi-computing systems, etc.

[0008] Details of one or more variations of the subject matter described herein are given in the accompanying drawings and the following description. Further features and advantages of the subject matter described herein will be apparent from the description and drawings, as well as from the claims. Certain features of the subject matter of this disclosure are described for illustrative purposes in relation to an electron vaporizer device, but it will be readily apparent that such features are not intended to be limiting. The claims following this disclosure are intended to specify the scope of the protected subject matter.

[0009] The accompanying drawings incorporated herein and constituting part thereof illustrate certain aspects of the subject matter disclosed herein and, together with the description, assist in explaining some of the principles relating to the disclosed embodiments. [Brief explanation of the drawing]

[0010] [Figure 1] Block diagram of a vaporizer according to some exemplary embodiments [Figure 2A] Explanatory exploded view of a vaporizer in Figure 1, according to some exemplary embodiments. [Figure 2B] Another exemplary diagram of the vaporizer in Figure 1, according to some exemplary embodiments. [Figure 2C] Another exemplary diagram of the vaporizer in Figure 1, according to some exemplary embodiments. [Figure 2D] An illustrative diagram of the vaporizer cartridge shown in Figure 1, according to some exemplary embodiments. [Figure 3] Block diagram of another vaporizer according to some exemplary embodiments [Figure 4A] An exemplary diagram of a vaporizer according to some exemplary embodiments, Figure 3. [Figure 4B] Another exemplary diagram of the vaporizer in Figure 3, according to some exemplary embodiments. [Figure 5] Block diagram of communication exchange between vaporizer, user device, and server according to some exemplary embodiments. [Figure 6] A diagram showing an exemplary device that may be used to implement one or more of the described features and / or components, according to some exemplary embodiments. [Figure 7] A diagram illustrating communication between one or more vaporizers and beacons, according to some exemplary embodiments. [Figure 8A] This figure illustrates communication exchange between one or more vaporizers and a user device in some exemplary embodiments. [Figure 8B] Flowchart of an exemplary method for authenticating a vaporizer user, according to some exemplary embodiments. [Figure 9] Flowchart of an exemplary method for locking a vaporizer, according to some exemplary embodiments. [Figure 10A]Figure showing the features of an exemplary user interface for an application that can be used with a vaporizer consistent with an embodiment of the subject matter [Figure 10B] Figure showing the features of an exemplary user interface for an application that can be used with a vaporizer consistent with an embodiment of the subject matter [Figure 10C] Figure showing the features of an exemplary user interface for an application that can be used with a vaporizer consistent with an embodiment of the subject matter [Figure 10D] Figure showing the features of an exemplary user interface for an application that can be used with a vaporizer consistent with an embodiment of the subject matter [Figure 10E] Figure showing the features of an exemplary user interface for an application that can be used with a vaporizer consistent with an embodiment of the subject matter [Figure 11A] Figure showing the features of an exemplary user interface for an application that can be used with a vaporizer consistent with an embodiment of the subject matter [Figure 11B] Figure showing the features of an exemplary user interface for an application that can be used with a vaporizer consistent with an embodiment of the subject matter [Figure 12A] Figure showing the features of an exemplary user interface for an application that can be used with a vaporizer consistent with an embodiment of the subject matter [Figure 12B] Figure showing the features of an exemplary user interface for an application that can be used with a vaporizer consistent with an embodiment of the subject matter [Figure 12C] Figure showing the features of an exemplary user interface for an application that can be used with a vaporizer consistent with an embodiment of the subject matter [Figure 12D] Figure showing the features of an exemplary user interface for an application that can be used with a vaporizer consistent with an embodiment of the subject matter [Figure 12E]A diagram showing the features of an exemplary user interface for an application that can be used with a vaporizer that conforms to an embodiment of the subject matter [Figure 12F] A diagram showing the features of an exemplary user interface for an application that can be used with a vaporizer that conforms to an embodiment of the subject matter [Figure 12G] A diagram showing the features of an exemplary user interface for an application that can be used with a vaporizer that conforms to an embodiment of the subject matter [Figure 12H] A diagram showing the features of an exemplary user interface for an application that can be used with a vaporizer that conforms to an embodiment of the subject matter [Figure 12I] A diagram showing the features of an exemplary user interface for an application that can be used with a vaporizer that conforms to an embodiment of the subject matter [Figure 12J] A diagram showing the features of an exemplary user interface for an application that can be used with a vaporizer that conforms to an embodiment of the subject matter [Figure 13A] A diagram showing the features of an exemplary user interface for an application that can be used with a vaporizer that conforms to an embodiment of the subject matter [Figure 13B] A diagram showing the features of an exemplary user interface for an application that can be used with a vaporizer that conforms to an embodiment of the subject matter [[ID=2​​​​​​​​​This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 13G] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 13H] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 14A] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 14B] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 14C] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 14D] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 14E] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 14F] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 15A] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 15B] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 15C]This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 15D] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 15E] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 16A] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 16B] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 16C] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 16D] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 16E] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 16F] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 16G] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 16H] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 17]This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 18] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 19] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 20] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 21] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 22] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 23] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 24] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 25] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 26] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 27] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 28]This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 29] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 30] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 31] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 32] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 33] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 34] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 35] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 36] This figure illustrates the features of an exemplary user interface for an application that may be used with a vaporizer corresponding to the embodiment described herein. [Figure 37] Figure illustrating an exemplary method consistent with the embodiment described herein. [Figure 38A] Figure illustrating an exemplary method consistent with the embodiment described herein. [Figure 38B] Figure illustrating an exemplary method consistent with the embodiment described herein. [Figure 39] Figure illustrating an exemplary method consistent with the embodiment described herein. [Modes for carrying out the invention]

[0011] In practical applications, similar reference numbers indicate similar structures, features, or elements.

[0012] Controlling and managing the use of vaporizer devices (hereinafter simply referred to as "control") is a critical consideration from several perspectives, including taking measures to prevent the misuse of such devices. The use of vaporizers by minors in uncontrolled circumstances can raise public health and legal issues. Furthermore, the latest commercially available vaporizers tend to be significantly smaller and easily used out of sight, which may lead to their use in places where uncontrolled use is undesirable or where it could violate local regulations, such as schools, hospitals, and other public indoor spaces. In other examples, counterfeit vaporizer components, such as consumable parts containing inhaled substances (such as replaceable cartridges), can lead to vaporizer malfunction and potentially cause health problems by circumventing quality control approaches regarding the purity of inhaled substances and / or other components of consumable parts that come into contact with inhaled air. Therefore, it is desirable to implement an approach that allows for one or more of the following: control over who is permitted to use the vaporizer, control over where the vaporizer can be used, and control over the consumables that can be used with the vaporizer.

[0013] The scope of this subject matter includes features that may be advantageously used in addressing these needs and / or one or more of these other needs. For example, embodiments of the scope of this subject matter include methods, devices, apparatus, articles, and systems relating to vaporizing and / or aerosolizing one or more substances for inhalation by a user, and approaches relating to creating additional barriers against misuse of such devices and / or consumables usable with such devices.

[0014] With regard to preventing use by minors, conventional vaporizers may leave the provision of age verification during the purchase of the vaporizer to a third party. For example, a retail store employee may perform some form of age verification (e.g., visual inspection of a driver's license) to authenticate the purchase, in a manner similar to the current approaches to reduce misuse / use by minors of other substances and / or supply systems such as alcoholic beverages, conventional tobacco, etc. However, authentication performed only at the point of sale in conjunction with these others may not prevent the purchaser from providing the purchased product (e.g., vaporizer, cartridge, or other consumables usable with the vaporizer) to an unintended party (e.g., a minor) or to unintended use by an unintended party if the vaporizer is lost or stolen. It may be desirable to provide additional security, authentication, or safety measures that help reduce or hinder undesirable use or use of the vaporizer. Such approaches may include technical features implemented at one or more stages of the vaporizer purchase and use cycle, as described herein.

[0015] With regard to controlling the use of a vaporizer in location control based on the use of a vaporizer, including one or more communication functions in the vaporizer may be advantageous in relation to one or more features described herein, for example.

[0016] Additionally, since many vaporizer devices, cartridges, or other consumables, and other age-controlled substances may be resold after age-controlled purchase or otherwise transferred to new users, it may also be desirable, or alternatively, to implement one or more approaches to correlate geographical clusters of misuse with locations where misuse may have occurred.

[0017] Various embodiments of the subject matter may be used in conjunction with one or more of various vaporizers and / or vaporizer systems. The term “vaporizer” is used generally herein and in the claims and refers to any self-contained device, a device comprising two or more separable components (e.g., a vaporizer body including a battery and / or other hardware, and a cartridge configured to contain and / or hold vaporizable material) and / or similar. A “vaporizer system” as used herein may also include one or more components such as a device that communicates with the vaporizer (e.g., wirelessly or via a wired connection) and optionally the vaporizer itself. One or more components of a vaporizer or vaporizer system consistent with the embodiments of the subject matter may be configured for user control and operation. As used herein, “aerosol” may refer to vapor (e.g., gaseous molecules of one or more substances) and / or particles (e.g., condensed droplets, solid particles, etc.) carried by a volume of air.

[0018] Examples of vaporizers consistent with the embodiments described herein include electronic vaporizers, e-cigarettes, and the like. Generally, such a vaporizer is a handheld device that heats vaporizable material (by convection, conduction, radiation, or a combination of some of these) to provide a dosage of inhalable material. The vaporizable material used in a vaporizer may be supplied in a cartridge (for example, this cartridge is part of a vaporizer that contains vaporizable material in a reservoir or other container and can be refilled with a new cartridge containing the same or different additional vaporizable material when empty or disposable). A vaporizer may be a cartridge-using vaporizer, a cartridge-less vaporizer, or a multi-purpose vaporizer that can be used with or without a cartridge. For example, a multi-purpose vaporizer may include a heating chamber (e.g., an oven) configured to receive vaporizable material directly into the heating chamber and also configured to receive a cartridge having a reservoir, etc., for holding the vaporizable material. In various embodiments, the vaporizer may be configured for use with a liquid vaporizable material (e.g., a carrier solution in which active and / or inactive components are suspended or held in a solution of the vaporizable material itself or in a liquid form) or a solid vaporizable material. The solid vaporizable material may contain plant material that releases a portion of the plant material as vaporizable material (e.g., such that a portion of the plant material remains as waste after the vaporizable material has been released for inhalation by the user), or optionally, the vaporizable material itself may be in a solid form so that all of the solid material can ultimately be vaporized for inhalation. The liquid vaporizable material may be such that it can be completely vaporized, or it may contain a liquid material in which a portion remains after all of the material suitable for inhalation has been consumed. In a given example, the vaporizable material may be one or more of the following: tobacco-based material, cannabis-based material, plant material, etc. In a given example, the vaporizable material may be nicotine, nicotine derivatives, nicotine salts, etc., or contain these. Alternatively or additionally, the vaporizable material may be one or more of the following, or may include them: nutritional supplements, cannabinoids, pharmaceutical compounds, etc.

[0019] In accordance with some embodiments of this subject matter, the vaporizer and / or vaporizer system may be configured to identify the vaporizable material to be vaporized and adjust the operation of the vaporizer accordingly. For example, the vaporizer may receive a cartridge or other pre-loaded container holding a vaporizable material (e.g., a solution of nicotine, cannabis, and / or other active ingredients as the vaporizable material) and be adapted to identify and / or determine one or more of the following information about the vaporizable material and / or the cartridge or other pre-loaded container, such as the type of vaporizable material, the concentration of the vaporizable material in the solution or other impure form of the vaporizable material contained in the cartridge reservoir or other container, the quantity (e.g., mass, volume, etc.) of the vaporizable material in the cartridge reservoir or other container, the configuration of the cartridge (e.g., heater power or heater configuration, one or more electrical characteristics, etc., what specific components or types of components are present in the cartridge), the lot number of the cartridge, the manufacturing date of the cartridge, the expiration date after which the cartridge should not be used, the manufacturing date or filling date of the cartridge, etc.

[0020] A vaporizer consistent with the embodiments of this Subject Matter may be configured to connect (e.g., via a wireless or wired connection) to a communication device (or an optional device) that communicates with the vaporizer. Such a device may be a component of a vaporizer system as discussed herein and may include first communication hardware capable of establishing a wireless communication channel with second communication hardware of the vaporizer. For example, a device used as part of a vaporizer system may include a general-purpose computing device (e.g., a smartphone, tablet, personal computer, smartwatch, or some other portable device) that runs software to generate a user interface for enabling the device's user to interact with the vaporizer. In other embodiments of this Subject Matter, such a device used as part of a vaporizer system may be a dedicated part of hardware such as a remote control or other wireless or wired device having one or more physical or software interface controls (e.g., configurable on a screen or other display device and selectable via user interaction with a touch-sensitive screen or some other input devices such as a mouse, pointer, trackball, or cursor buttons). The term “device” is used herein, but the term “apparatus” is intended and should be interpreted as such.

[0021] A device that is part of a vaporizer system as defined herein may be used for one or more functions such as: dosage control (e.g., dosage monitoring, dosage setting, dosage limiting, user tracking), session control (e.g., session monitoring, session setting, session limiting, user tracking), location information acquisition (e.g., other users' locations, retail / commercial location locations, vaping locations, relative or absolute location of the vaporizer itself), vaporizer personalization (e.g., vaporizer naming, vaporizer lock / password protection, adjustment of one or more parental controls, association of vaporizer with user groups, registration of vaporizer with manufacturer or warranty maintenance organization), and linking social activities with other users (e.g., social media communication, interaction with one or more groups). The terms “sessionization,” “session,” “vaporizer session,” or “vaporization session” are used generally in the following description and claims and refer to the period of time spent using the vaporizer. This period may include duration, number of doses, quantity of vaporizable material, and / or similar.

[0022] In some embodiments of this subject matter, the vaporizer may include a function for communicating with a cartridge containing vaporizable material. The vaporizer may also communicate with a device that is part of the vaporizer system, but this is not required. A vaporizer that is under the control of a device that is part of the vaporizer system, or that otherwise communicates with a device, or a vaporizer as a separate, independent unit from the vaporizer system, may be configured to modify, control, etc., its operation based on one or more parameters received from the cartridge, or based on one or more parameters accessed from a database or other information source based on the identification of the cartridge.

[0023] For example, a vaporizer corresponding to the embodiments described herein may be configured to recognize a cartridge and to repeat (and in some cases transmit) or otherwise acquire information about the cartridge. In other words, computing elements such as a controller associated with the vaporizer body may obtain information about the cartridge through some form of data exchange. Various methods of cartridge recognition by the vaporizer, including those described in more detail below, are within the scope of the rights described herein. While such wireless connections described herein are advantageously applicable as described in more detail below, any approach described herein is feasible with or without the addition of wireless communication / connections described herein.

[0024] The embodiments described herein also include methods of using a vaporizer and / or vaporizer system for functions such as determining and / or controlling the dosage, quantity, etc., of one or more chemical species of vaporizable material, or of the vaporizable material itself.

[0025] Figure 1 shows a block diagram of a vaporizer 100 according to some exemplary embodiments. As shown, the vaporizer 100 of Figure 1 includes a vaporizer body 101. This vaporizer body 101 may include a housing surrounding a power supply 103 (for example, a device or system that stores electrical energy for on-demand use). This power supply 103 may be a battery, a capacitor, a combination thereof, and may be rechargeable or non-rechargeable. The housing may also surround a controller 105, which may include a processor. In the illustrated example, the cartridge 114 may be mounted on top of, inside, or in part of the vaporizer body 101.

[0026] Figure 2A shows an exemplary vaporizer 100 that may include the features shown in Figure 1. As shown in Figure 2A, the vaporizer 100 may include a vaporizer body 101 and a cartridge 114 that is separable from the vaporizer body 101. Figures 2B and 2C show a front and side view of the exemplary vaporizer 100 of Figure 2A, respectively. Figure 2D shows an exemplary diagram of the cartridge 114 of Figure 2A separated from the vaporizer body 101. In some embodiments, the cartridge 114 may be able to hold and / or be configured to hold liquid vaporizable material. For example, if the vaporizer includes a cartridge (such as cartridge 114), the cartridge 114 may include one or more reservoirs 120 for and / or vaporizable material. Any suitable vaporizable material, including a solution of nicotine or other organic material, may be contained within the reservoirs 120 of cartridge 114.

[0027] The exemplary vaporizers shown in Figures 2A to 2D include a cartridge 114 that can be inserted into the vaporizer body 101, but other vaporizer configurations are also within the scope of the rights of this Subject Matter. For example, vaporizers can be used in this Subject Matter with or without a cartridge. In the case of vaporizers that use a cartridge, such a cartridge may be a consumable item (e.g., disposable after the provided volume of vaporizable material has been consumed) or reusable (e.g., refillable with vaporizable material).

[0028] The processor of the controller 105 may include a circuit for controlling the operation of a heater 118, which may optionally include one or more heating elements for vaporizing vaporizable material contained in the cartridge 114, for example, in a reservoir or container that is part of the cartridge 114. In various embodiments, the heater 118 may be located in the vaporizer body 101, or in the cartridge 114 (as shown in Figure 1), or both. The controller circuit may include one or more clocks (oscillators), charging circuits, I / O controllers, memory, etc. Alternatively or additionally, the controller circuit may include a circuit for one or more wireless communication modes, including Bluetooth®, near-field communication (NFC), WiFi, ultrasonic, ZigBee, RFID, etc. The vaporizer body 101 may also include a memory 125, which may be part of the controller 105 or otherwise be able to communicate data with the controller. Memory 125 may include volatile memory (e.g., random access memory) and / or non-volatile memory (e.g., read-only memory, flash memory, solid-state storage, hard drives, other magnetic storage, etc.) or data storage.

[0029] Referring further to Figure 1, the vaporizer 100 may optionally include a charger 133 (and a charging circuit that can be controlled by the controller 105) which may include an inductive charger and / or a plug-in charger. For example, a Universal Serial Bus (USB) connection may be used to charge the vaporizer 100 and / or to enable communication via a wired connection between a computing device and the controller 105. The charger 133 can charge the onboard power supply 103. The vaporizer 100 consistent with the embodiments of this subject may also include one or more input sides 117 such as buttons and dials, and / or sensors 137 such as accelerometers or other motion sensors, capacitive sensors, flow sensors, etc. These sensors 137 may be used by the vaporizer 100 to detect user handling and interaction. For example, detection of rapid movement of the vaporizer 100 (such as shaking motion) may be interpreted by the controller 105 (e.g., through reception of signals from one or more of the sensors 137) as a user command to initiate communication with a user device. The user device is part of the vaporizer system and can be used to control one or more operations and / or parameters of the vaporizer 100, as will be described in more detail below. Additionally or alternatively, detection of rapid movement of the vaporizer 100 (such as shaking motion) may be interpreted by the controller 105 (e.g., through reception of signals from one or more of the sensors 137) as a user command to circulate the vaporizable material held in the cartridge 114 through multiple temperature settings, which are heated by the action of the heater 118. In some optional variants, detection of removal of the cartridge 114 by the controller 105 (e.g., through reception of signals from one or more of the sensors 137) during circulation through multiple temperature settings may act to establish a temperature (e.g., when the cycle is at a desired temperature, the user can remove the cartridge 114 for a desired temperature setting).The cartridge 114 can then be refitted with the vaporizer body 101 by the user to enable the use of the vaporizer 100 with a heater controlled by the controller 105, matching the selected temperature setting. Multiple temperature settings may be indicated by one or more indicators on the vaporizer device body 101.

[0030] A vaporizer corresponding to the embodiments described herein may also include one or more output sides 115. As used herein, the output side 115 may refer to any optical (e.g., LED, display, etc.), tactile (e.g., vibration, etc.), or acoustic (e.g., piezoelectric, etc.) feedback component, or any combination thereof.

[0031] A vaporizer 100 consistent with the embodiments of this subject, including a cartridge 114, may include one or more electrical contacts on or inside the vaporizer body 101 (such as electrical contacts 109, 111, 113 shown in Figure 1) that can be fitted with supplemental cartridge contacts 119, 121, 123 (such as pins or receptacles) on the cartridge 114 when the cartridge is fitted into the vaporizer body 101. The contacts on the vaporizer body are generally also referred to as “vaporizer body contacts,” and the contacts on the cartridge are generally referred to as “cartridge contacts.” These contacts may be used to supply energy from the power supply 103 to the heater 118 in embodiments of this subject, where the heater 118 is contained within the cartridge 114. For example, if the cartridge contacts and vaporizer body contacts are fitted together by coupling the cartridge 114 to the vaporizer body 101, the power supply circuit may be configured to control the flow of power from the power supply 103 in the vaporizer body 101 to the heater 118 in the cartridge 114. The controller 105 inside the vaporizer body 101 can adjust the flow of power to control the temperature at which the heater 118 heats the vaporizable material contained in the cartridge 114.

[0032] Any suitable electrical contacts, including multiple pins (e.g., pogo pins), plates, etc., can be used. Furthermore, as described below, in some embodiments of this subject matter, unidirectional or bidirectional communication is provided between the vaporizer device body 101 and the cartridge 114 via one or more electrical contacts. These electrical contacts may include electrical contacts used to supply energy from the power supply 103 to the heater 118. The cartridge 114 and the vaporizer body 101 can be removably coupled together, for example, by mating a portion of the housing of the cartridge 114 to the vaporizer body 101 and / or the vaporizer housing via mechanical connections (e.g., snaps and / or friction fits). Alternatively or additionally, the cartridge 114 and the vaporizer body 101 may be coupled magnetically or via some other coupling or mating mechanism. In other words, coupling between the cartridge and the vaporizer can be achieved by any of several possible approaches, including but not limited to magnetic couplings, friction mating couplings, screw couplings, snap-in or snap-fit ​​couplings, etc.

[0033] Any of the cartridges described herein may include one or more identifiers 138. Identifiers 138 can be recognized, detected, and / or read by the vaporizer body 101 and can convey information about the vaporizable material contained in the cartridge and / or the cartridge 114 itself. Identifiers 138 may include a readable and / or read / writeable cartridge memory. Identifiers 138 may include a circuit for receiving and / or transferring information between the cartridge 114 and the vaporizer body 101. For example, a data exchange circuit may include a cartridge memory for storing information (e.g., data characterizing one or more parameters of the cartridge) and an additional circuit that, when the cartridge 114 is coupled to the vaporizer body 101, works in cooperation with other circuits on the vaporizer body 101 to form a data exchange circuit.

[0034] In some embodiments of this subject matter, the identifier 138 is passive and may include a code or marking (e.g., a barcode, a quick response (QR) code, etc.). In some examples, the identifier 138 may be a structure on the cartridge 114 (e.g., one or more pins, protrusions, etc.) that can be detected by the vaporizer body 101. Visual or mechanical identifiers may be directly identified by the vaporizer body 101 using an imaging device (e.g., a camera, etc.) or reading device (e.g., an optical reader) integrated into the vaporizer body (not shown in Figure 1), or via communication by a separate device such as a smartphone. For example, a user may take an image of the identifier 138 (e.g., a code, marking, etc.) and transmit the code or information derived from the code (e.g., information about the vaporizable material and / or cartridge) to the vaporizer body 101 via the wireless circuit 107, or optionally via a wired connection. A wireless connection (e.g., a wireless communication channel) may be established between the device's first communication hardware and the vaporizer's second communication hardware. The first and second communication hardware may each include, and are not limited to, transceivers for use with one or more wireless communication protocols, and examples thereof are described herein.

[0035] Figure 3 shows a schematic diagram of a vaporizer 200 that does not use a cartridge (although cartridge acceptance is still optional), but instead uses loose-leaf material. The vaporizer 200 in Figure 3 may include loose vaporizable material that can be placed inside an oven 220 (e.g., a vaporization chamber). Many of the same elements present in the vaporizer 100 using cartridges 114 shown in Figures 1 and 2A-2D may be included as part of the cartridge-less vaporizer 200. For example, the cartridge-less vaporizer 200 may include a vaporizer body 201 with a control circuit 205 that may include a power control circuit and / or a wireless circuit 207 and / or memory 225. A power source 203 (e.g., a battery, capacitor, etc.) may be charged by a charger 233 (which may also include a charging control circuit, not shown). This vaporizer 200 may also include one or more output sides 215 and one or more input sides 217, along with a sensor 237. Additionally, the vaporizer 200 may include one or more heaters 218 for heating an oven 220 or other heating chamber. These heaters 218 can be controlled using their resistance to determine the heater's temperature, for example, by using the temperature coefficient of the heater's resistivity. A mouthpiece 244 may also be included.

[0036] Figure 4A shows an exemplary side perspective view of a vaporizer 200 having a vaporizer body 201. In the bottom perspective view of Figure 4B, the lid 230 is shown away from the vaporizer body 201, and the oven / vaporization chamber 220 is exposed.

[0037] Figure 5 shows a schematic diagram of communication between vaporizers 100, 200, a digital device 305 that wirelessly communicates with vaporizers 100, 200, and a remote server 307 that can communicate with vaporizers 100, 200 directly or via the digital device 305. The digital device 305 may be a handheld mobile device such as a smartphone, smartwatch, or tablet, or a desktop or laptop computing device. As described herein, the digital device 305 may optionally be a dedicated remote control device.

[0038] Generally, as schematically shown in Figure 5, vaporizers 100,200 may communicate remotely with a remote server 307 and / or with a wearable electronic device (e.g., Google Glass, smartwatch, smartwear, etc.) and / or a digital device 305 such as a smartphone or smartwatch. Therefore, the vaporizer may include a communication interface (wireless circuitry 107,207) which may be implemented via a communication chip (e.g., second communication hardware) located inside or on top of the vaporizer. Exemplary wireless chips may include, but are not limited to, Bluetooth chips such as the Parani BCD 210 or Texas Instruments (TI) CC2650 Bluetooth single-chip solution, NFC-enabled chips that consider NFC communication (e.g., Qualcomm's QCA1990), or enhanced Wi-Fi or Bluetooth communication where NFC is used for link configuration. As described and explained in relation to the examples herein, one or more of these wireless circuits may be used for communication with or between the cartridges 114 in embodiments configured to read the cartridges 114 as schematically shown in Figure 1. For example, NFC may be used to read the identifier 138 (as an RFID tag) on ​​the cartridge 114.

[0039] The wireless communication chip may include a Wi-Fi enable chip such as TI's SimpleLink family CC3000, which can connect the vaporizer to a Wi-Fi network. In some embodiments, the wireless circuitry may include a subscriber identification module (SIM) card on the vaporizer's substrate, such as a Nano-SIM card (e.g., enabling 3G / 4G cellular network communication). Alternatively, alternative communication methods may be used to establish bidirectional communication between the vaporizers 100, 200 and the user device 305.

[0040] The connection between the vaporizers 100, 200 and the user device 305 may be automatic (for example, after initial setup), or it may be initiated by the user through various settings via user interaction with the vaporizer itself (for example, by shaking the vaporizer, tapping the vaporizer, or pressing one or more buttons on the vaporizer).

[0041] Vaporizers, vaporizer systems, and methods of using them for the use of active substances (e.g., nicotine, other drugs, etc.) based on user customization of vaporizer settings and activation patterns are also within the scope of the rights covered hereby. Vaporizers and / or vaporizer systems consistent with this description may allow users to personalize the vaporizer among other possible communication-related functions.

[0042] Vaporizers and / or vaporizer systems consistent with the embodiments covered herein may be configured to facilitate communication interactions via 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 and counselors specializing in dosage reduction), for better prescription and medical treatment management. The vaporizer and / or vaporizer system may be configured to communicate with third parties other than medical contacts (e.g., friends, colleagues) and unknown third parties (who make some or all of the information available). In some embodiments covered herein, the vaporizer described herein may, by itself or by communicating with one or more communication devices that are part of the vaporizer system, identify and provide information regarding operation, status, or user input from the vaporizer to a public or private network. In some embodiments covered herein, the vaporizer and / or vaporizer system may be configured to provide one or more interactive user interfaces for use by a single user and / or multiple users of different (or the same) vaporizers. Interaction via the user interface may be linked to the operation of the vaporizer and / or user operation of the vaporizer (e.g., operation based on accelerometer output, touch or lip sensing, drawing detection, etc.).

[0043] Vaporizers and / or vaporizer systems matching the embodiments described herein may also be configured to provide location information. This location information may include, in some cases, information about one or more locations of users near one or more of the following: other users (known or unknown, specific or unspecified users, etc.), retail stores, or specific locations (lounges, clubs, places suitable for vaporizers). Vaporizers and / or vaporizer systems may also be configured to facilitate ordering based on the use or operation of the vaporizer and / or vaporizer system.

[0044] The vaporizer may include a GPS function or may access GPS information from another device (e.g., user device 305) that communicates with the vaporizer as part of the vaporizer system.

[0045] In certain embodiments of the subject, a vaporizer including a cartridge may be configured to recognize and / or identify the cartridge, optionally including, but not limited to, characteristics relating to the cartridge and / or its contents. One or more recognition / identification approaches may be employed to enable the vaporizer (e.g., a controller, microprocessor, etc., which are part of the vaporizer body) to determine information about the cartridge and / or the vaporizable material held within the cartridge. This information may include, for example, one or more of the following: the type of vaporizable material (e.g., nicotine, cannabis-derived material, flavor, whether the vaporizable material is neat, in solution, solid or liquid, loose leaf, or otherwise plant-derived material), the concentration of the vaporizable material (e.g., in a carrier solution containing one or more of propylene glycol, vegetable glycerin, or other solvents), the quantity or volume of the vaporizable material, the configuration of the cartridge (e.g., heater characteristics, electrical characteristics), the lot number of the cartridge, the manufacturing date of the cartridge, the expiration date of the cartridge, and information for verifying the origin and authenticity of the cartridge.

[0046] This information may be encoded directly on the cartridge, or a reference indicator may be provided that the vaporizer (or a processor communicating with the vaporizer) 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.

[0047] In some embodiments of this subject matter, the cartridge may be recognized and / or identified by the fitting between the cartridge and the vaporizer. In some embodiments of this subject matter, the cartridge may be configured to include a keyed interaction with the vaporizer. For example, part of the shape or size of the cartridge may be detected by the vaporizer (wherein different variations in size, shape, etc., may indicate predetermined features of the cartridge and / or its contents). Alternatively or additionally, the cartridge may include n pins or protrusions that can be detected when the cartridge is inserted into or otherwise connected to the vaporizer body (e.g., by completion of electrical connection). In the case of n pins, there are 2 combinations of markings. n There are several possibilities. Each combination can indicate the function of the cartridge, or a combination of functions, and / or their contents.

[0048] In any further variation, the cartridge may be configured or identified based on electrical characteristics that the vaporizer can detect based on its electrical connection to the cartridge. For example, the electrical circuit may be completed by the combination of the cartridge and the vaporizer body by the coupling of two or more pairs of electrical contacts (e.g., some of each pair on the cartridge and the corresponding contacts on the vaporizer body). The heater or other components of the cartridge then become part of the completed circuit. One or more parameters of the heater or other cartridge components, such as characteristic resistance, inductance, time response (e.g., time constant, RC time constant, LC circuit resonance, etc.), may be detected after the circuit is completed. These one or more parameters may indicate characteristics or combinations of characteristics of the cartridge and / or the contents of the cartridge.

[0049] In some embodiments of this subject matter, cartridges can be recognized and / or identified by markings on the cartridge identified by a vaporizer. These markings may or may not be visible to the user. For example, a cartridge may be marked with a characteristic UV, IR, or other wavelength-specific ink that can be detected by a vaporizer, which may include, for example, an emitter / detector pair specific to the marker. For example, the marking may include an infrared scannable barcode located on the cartridge. In some embodiments, the marking may be a pattern such as a QR code or barcode that indicates information about the cartridge and / or the contents of the cartridge (vaporable material). The marking may be a symbol including alphanumeric characters. The marking may be directly “read” or detected by a vaporizer, which may include a camera or other optical detector. Alternatively, it may be detected indirectly via communication with a second device (e.g., a wearable, smartphone, etc.) having a camera, etc. For example, the marking on the cartridge may be detected by a user device 305 (e.g., via a camera or other sensor that is part of or otherwise controllable to provide input to the user device 305). For example, a smartphone functioning as a user device 305 can identify markings captured as images via its smartphone camera using an application (e.g., software) on the smartphone that can look up one or more properties from a lookup table, or it can communicate the markings directly to a vaporizer that can look up the properties, and / or communicate with a remote server that can look up the properties and communicate that directly to the vaporizer or via the smartphone.

[0050] In some embodiments of this subject matter, cartridges may be recognized by RFID (Radio-Frequency Identification) technology. RFID markers have been used in a wide variety of applications for inventory management. Some RFID technologies use active devices that include their own power supply, while others use passive RFID devices. These passive RFID devices interact with another powered device that causes data transfer without relying on power supply in the passive device itself. For example, a cartridge may include one or more RFID chips or components that can be detected and read by a reader on the vaporizer to identify and receive information about the cartridge.

[0051] In some embodiments of the present invention, the cartridge can be recognized and / or identified by communication with a memory (e.g., EEPROM) on the cartridge via an electrical connection to the vaporizer. In embodiments where a heater is located on the cartridge, such as the exemplary vaporizer shown in Figure 1, it may be advantageous to use one or more electrical connections (e.g., contacts 119, 121, 123) on the cartridge that are also used to power and / or control the heater for communication with the memory. However, this can be particularly difficult if the cartridge can be mated to the vaporizer in two or more orientations, and / or if the heater is controlled via the same contacts, and the electrical signals supplied / received between the cartridge and the vaporizer are changed, allowing the vaporizer to change the control and / or temperature determination of the heater. One or more additional electrical contacts may be used in addition to the contacts that control the heater. Generally, communication between the cartridge and the vaporizer may be unidirectional (e.g., the vaporizer reading information about the cartridge and / or vaporizable material from the cartridge), or it may be bidirectional (e.g., reading information about the cartridge and / or vaporizable material, and writing information about the device's operation, such as the number of uses, usage duration, and temperature setting). The information can be written to the cartridge, and this information can further be used to derive other information about the cartridge, including the amount of material remaining in the cartridge.

[0052] In general, any of the vaporizers described herein can estimate, measure, and / or predict the amount of vapor that can be supplied to the user and / or the amount of material (including the active ingredient) in the vapor. For example, as described in detail below, the devices described herein can be used to determine and / or control the dosage of vaporizable material. For example, this subject includes vaporizers and methods of using such vaporizers for the precise and controlled dosage supply of active ingredients in vaporizable material (e.g., nicotine, cannabis, and any other active ingredients / drugs) based on the medical switching or discontinuation needs specified by the user. Dosage control may include displaying dosage information per use, per session (multiple uses within predetermined durations, e.g., 1-15 minutes, 1-30 minutes, 1-60 minutes, 1-90 minutes, 1-120 minutes), per day, or per other predetermined and / or user-defined duration. This dosage control may also include dosage monitoring (e.g., the amount of one or more active ingredients supplied by the device). Similarly or alternatively, this dosage control may include controlling the operation of the vaporizer based on the amount of one or more active ingredients supplied by the device over time, including warning the user when the amount approaches or exceeds a predetermined (user-defined, factory-set, or third-party-set) amount or threshold (e.g., within 50%, 75%, 80%, 85%, 90%, 95%, 98%, 99% of the predetermined amount), and / or stopping (locking, disabling) the operation of the device when the predetermined threshold is reached or exceeded. A device including dosage control may include internal logic (circuits and / or programming including application-specific integrated circuit (ASIC) logic) for controlling the dosage and / or may communicate (via a wireless link) with an external processor that performs all or part of the dosage control.

[0053] Information regarding the cartridge and / or the vaporizable material held within the cartridge may optionally include one or more of the above types of information, which may be particularly helpful in quantifying the dosage of vaporizable material supplied to the user. In some embodiments of this subject, dosage and / or usage information may be stored (written) on the cartridge (e.g., in memory). For example, based on a calculation of the amount of vaporizable material supplied, data may be written to the cartridge and / or the data may be stored in a server in relation to a particular cartridge, so that by reconnecting the cartridge to the same or a different vaporizer body, the vaporizer body can consequently determine how much vaporizable material was previously dispensed from the cartridge.

[0054] Additional technologies that enable the vaporizer to perform cartridge recognition and / or communication include the use of markers (e.g., QR codes, IR or US markers), mechanical and / or electronic keying, etc. Generally, as described elsewhere in this specification, electronic communication between the cartridge and the vaporizer may include the transfer of information unidirectional or, in some embodiments, bidirectional (including dual or multiplex). Thus, information may be received from the cartridge by the vaporizer, and optionally, information may be written to the cartridge by the vaporizer. The information provided to the vaporizer may include information about the vaporizable material and / or cartridge, as discussed elsewhere in this specification.

[0055] A cartridge containing an identification circuit (also referred to herein as a cartridge identification circuit) may be configured to communicate and transfer such information from the cartridge to the vaporizer. The cartridge identification circuit may include memory (e.g., EEPROM). In a variant of the cartridge in which a heater (e.g., a resistive heating element such as a resistive coil or wire) is controlled by supplying energy to one or more (e.g., two, three, four, etc.) heater electrical contacts that communicate with corresponding contacts on the vaporizer, the cartridge identification circuit may communicate with the vaporizer via the same heater electrical contacts, despite the increased complexity and the potential for heater failure.

[0056] The cartridge identification circuit may be configured so that the cartridge can be inserted into the vaporizer in multiple orientations without interrupting the operation of the cartridge identification circuit.

[0057] The same cartridge identification circuit may also contain information about the cartridge, the vaporizable material, and the cartridge's history, including, for example, usage time and / or total energy supplied.

[0058] Information stored (read and / or written) in memory may be encoded, including the use of encryption, error-correcting coding (e.g., Hamming code). During operation, when a cartridge is first inserted into the vaporizer body, the vaporizer microcontroller may be configured to first determine whether it can read a signal of cartridge encoding information about the cartridge and / or whether the cartridge can be identified as compatible with the vaporizer. The information can be read using the vaporizer's measurement circuit. In some embodiments, if the cartridge cannot be read (e.g., if there is no cartridge identification circuit or if it cannot be read from the cartridge identification circuit), the vaporizer can use default settings.

[0059] During operation, the vaporizer can periodically write to the memory in the cartridge identification circuit (for example, after each stroke) if it is detected. The vaporizer can signal to the memory and request a read from it in the same way that the device writes to the memory, then cut off the battery voltage supplied to the heater contacts so that the memory (e.g., EEPROM) can control the I / O line, which is used to output data, providing a digital output (low / high switching of the I / O line) and transferring the output detected by the vaporizer via the resistance measurement circuit. Typically, if the memory is performing a transfer, the absolute accuracy of temperature control may be affected. Therefore, the vaporizer can be configured so that the device does not heat when the memory is performing a transfer (output), and so that normal heating operation does not trigger data transfer to the memory.

[0060] As will be described in more detail below, the information stored in the memory of a cartridge identification circuit as described herein will be useful for dosage control (e.g., calculation and storage of dosage information), as well as for storing security, communication, and operating parameters, especially in devices that include wireless capabilities. However, cartridge identification will also be useful even in the absence of wireless communication capabilities.

[0061] As discussed, memory (e.g., EEPROM) can store information about vaporizable materials and / or cartridges. Examples of information that can be stored include values ​​relating to specific characteristics of the heating element, such as the nominal heating resistance R (resistance) of the cartridge, including the cartridge's heating element. This value may be determined and stored at the factory when the device is manufactured / produced, and / or at a later date. Storing a specific R value for each cartridge in a memory associated with that cartridge, including determining the baseline resistance at ambient temperature, as described herein, can be useful for precise temperature control of the device. While resistance / baseline measurements on the production line may differ slightly from the measurements the device acquires for use, baseline adjustment (determined by an algorithm) can also be used. Alternatively or additionally, once a reliable baseline for a cartridge is determined, this baseline can be associated with an ID specific to that cartridge (e.g., in a remote database, on a remote server), so that when a cartridge is removed and reinserted, the same baseline value can be used (immediately after verifying the cartridge ID), which can be checked sooner than waiting for a stable baseline to be detected.

[0062] In general, storing cartridge characteristics such as heater resistance in the cartridge itself can also be useful in confirming that the connection between the vaporizer and the cartridge is good and that the vaporizer's resistance measurement circuit is functioning correctly. Therefore, in any of the methods and apparatus described herein, the nominal cartridge resistance may be stored in the cartridge's memory (or stored on a remote server / device and retrieved based on a unique cartridge ID) and may be used to confirm that the connection between the device and the pod is good, and / or that the device's resistance measurement circuit is functioning correctly, and / or that the cartridge resistance has not changed since the cartridge was assembled or filled.

[0063] As described herein, in some embodiments, the vaporizer may write usage information to the cartridge memory, which can be used to estimate the amount of vaporizable material removed from the cartridge and the amount of vaporizable material remaining. The usage information may include the number of puffs / inhalations, the amount supplied, and so on.

[0064] The vaporizer and / or vaporizer system may include software, firmware, or hardware that communicates wirelessly with the vaporizer, either separate from or separable from the vaporizer. For example, applications ("apps") may run on the processor of a portable and / or wearable user device, including smartphones, tablets, smartwatches, and personal data assistants. These are generally referred to herein as user devices (e.g., user device 305 in Figure 3) that are part of the vaporizer system. The user device may provide an interface for the user to connect with and interact with functions associated with the vaporizer, such functions including data communication to and from the vaporizer and / or data communication to an additional third-party processor (e.g., a server such as remote server 307 in Figure 3). For example, the user may control certain aspects of the vaporizer (temperature, dosage, etc.) and / or optionally, data transfer and reception to and from the vaporizer via a wireless communication channel between the device's first communication hardware and the vaporizer's second communication hardware. Data may be communicated in response to one or more user actions (including, for example, interaction with a user interface displayed on the device) and / or as a background operation that does not require the user to initiate or authorize the data communication process.

[0065] The user interface may be located on the user device and can assist the user in operating the vaporizer. For example, a user interface operating on a user device may include icons and text elements that can inform the user of various ways in which the vaporizer settings can be adjusted or configured by the user. In this way (or in other ways consistent with the scope of the present invention), information about the vaporizer can be presented using a user interface displayed on the user device. Icons and / or text elements may be provided so that the user can see information about the vaporizer status, such as battery information (charge level, vapor draw level, charging time, charging indicator, etc.), cartridge status (e.g., type of cartridge and vaporizable material, cartridge filling status, etc.), and similar device status. Icons and / or text elements may also be provided so that the user can perform updates to the internal software (also known as firmware) within the vaporizer. Furthermore, icons and text elements may be provided so that the user can configure security and / or authentication features of the vaporizer, such as setting a PIN code for vaporizer activation or using personal biometric information as an authentication means. Icons and / or text elements may be provided to allow users to configure foreground data sharing and associated settings.

[0066] The vaporizer may include or incorporate one or more authentication functions. For example, the user interface ("app") may include, for example, PIN-based authentication, biometric authentication (biometric authentication may include fingerprint-based authentication, iris scan-based authentication, facial recognition-based authentication, and / or similar). Authentication may include age analysis, such as estimation or calculation of the user's age based on analysis of facial features. Authentication may also be used to lock / unlock the vaporizer.

[0067] The authentication process can be implemented as a function of an application installed and running on a user device (e.g., part of the vaporizer system described herein) capable of data communication using wired or wireless methods. As described above, the user device may have an operating system on which the application can run. Alternatively, the vaporizer itself may include one or more user interface functions (e.g., PIN code input or some other user input-based authentication approaches) and / or sensors for performing fingerprint or iris scanning, facial recognition, etc.

[0068] In some embodiments of this subject matter, the vaporizer may connect (e.g., via communication) to an additional device (e.g., a portable, wearable, smartphone, desktop, or laptop) that allows the user to enable programmable dosage control, real-time usage monitoring, personalized usage settings, device lockout, and social features. For example, the vaporizer and / or vaporizer system may include features associated with security controls, including parental controls, user age controls / restrictions, and anti-theft controls. The vaporizer and / or vaporizer system may include anti-theft and / or authentication features that can lock or otherwise restrict the use / operation of the device when the vaporizer is stolen, misplaced, etc., and / or used with counterfeit parts, and may also be configured to allow locks (e.g., parental locks) to protect children or otherwise prevent operation by unauthorized third parties.

[0069] For example, this type of anti-counterfeiting or other lockout feature can be implemented using a cartridge identifier to prevent the use of counterfeit consumables, such as replaceable cartridges containing vaporizable material. For instance, a cartridge identifier from a verified source or supplier may include a hash or some other verification code as part of the identifier, and the vaporizer may lock out the use of the vaporizer if a cartridge lacking the required hash or verification code is coupled to the vaporizer body. Such a feature may also be used in a device communicating with the vaporizer to require user identity verification to be entered in order for the device to unlock the use of the vaporizer. For example, a cartridge may contain an identifier indicating that it contains a controlled substance, and the user may be required by an application on the device (depending on the application's decision regarding the cartridge via identifier information received from the cartridge) to verify their identity (e.g., via password entry, biometric authentication), and further, for the application, to verify that the identified user is authorized to use the controlled substance before the vaporizer can be used with a cartridge coupled to the vaporizer body. In another example, nicotine or cannabis-containing cartridges require user identity verification, and therefore the application on the device only permits the use of the vaporizer if the user's identity has been verified and the user is registered as being above the minimum age.

[0070] In some examples, security controls may be incorporated via 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 for the vaporizer itself or an alternative / additional identifier for the cartridge, and based on or using this identifier, it may determine whether security settings are included in the user profile or other settings related to the vaporizer or cartridge. In accordance with the embodiments covered herein, such functionality may be contained entirely or partially within the vaporizer (and / or cartridge) or distributed between the vaporizer and a user interface that may reside on an additional device that is part of the vaporizer system, such as a wearable and / or handheld device, laptop, or desktop, which operates the control logic. The control logic or other software functions for providing these features may include a user interface that may provide input / output and analytical capabilities for adjusting the operation of the vaporizer. Non-limiting options for first communication hardware of the device and / or second communication hardware of the vaporizer are described herein.

[0071] The vaporizer may be configured to switch to a locked mode or a “further authentication required” mode after a period of inactivity exceeds a predetermined (or optionally user-configurable) time threshold. In some examples, this locked mode may be a “sleep mode” or include a “sleep mode” when no use is detected for a predetermined and / or pre-configured duration. In some embodiments of this subject matter, the user must be authenticated as a prerequisite for the vaporizer to be activated and thereby available for use for the purpose of generating vapor, in order to ensure that the device is being used by the intended user, and thereby to prevent or deter unauthorized use of the device, accidental or unintentional activation, or use of the device by an individual who has not reached the legal age to ingest active ingredients, including nicotine or cannabis. Personal identification number (PIN) based authentication may apply a user-selected PIN code for end-use authentication. Biometric authentication may be used using one or more optional approaches. For example, a fingerprint-based authentication process may authenticate the end user. An iris scan-based authentication process may use an eye or iris scan, etc., for end-user authentication. Facial recognition-based authentication can use facial scanning or image processing algorithms to authenticate end users. Biometric authentication, including iris scanning and facial recognition, can be particularly useful if the personal digital device has a camera, such as a front-facing camera, or other sensors configured for such authentication to enable the use of the user device.

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

[0073] The vaporizer may include a heating element configured to heat a vaporizable material. The app may be configured to disable and / or lock the vaporizer by disabling the power supply to and / or use of the vaporizer's heating element. Disabling and / or locking the vaporizer may be based on user authentication and / or age verification. Disabling and / or locking the vaporizer may also be based on the vaporizer being within range of a disable / lock signal or disable / lock device (e.g., beacon 705), as described below in relation to Figures 7-9. The control system may be configured (e.g., via firmware) to allow the user to selectively disable the operation of the heating element consisting of a predetermined operation (e.g., standard heating). In some embodiments, the device may be configured to ignore readings from a pressure sensor and / or other indications of the user revving on the device. The app may be configured to provide a notification indicating that the vaporizer is operationally disabled and / or locked. Additionally or alternatively, the device may be configured to alert the user (e.g., using one or more LEDs, an audible method, a tactile method, etc.) that the device is locked if the user decides to perform a rev on the device. In some embodiments, the vaporizer may be configured to become operational in response to the vaporizer being within a threshold range of the user device. In some embodiments, the vaporizer may be configured to become operational in response to a vaporizer receiving a signal from the user device. In some embodiments, the vaporizer may be configured to remain inoperable in response to a vaporizer receiving a signal from the user device. For example, the user may lock and / or unlock the vaporizer by user input to an app, such as fingerprint recognition, facial recognition, and / or similar.

[0074] The vaporizer may be configured to be locked so that its primary function (e.g., vapor generation) is disabled to prevent unauthorized users from using the locked device. In some embodiments, the vaporizer, paired with an app or other software, may implement a lock / unlock function so that a given user can lock the device. Thus, unauthorized users are prevented from unlocking and / or accessing the vaporizer. The lock function may consist of strong security (such as encryption, a firewall, and / or similar) to prevent hacking from disabling the lock function.

[0075] The app can be configured to disable and / or lock the vaporizer in response to the vaporizer being outside the threshold communication range with the user device. For example, if the vaporizer is beyond the communication range of the user device, the vaporizer can be configured to deactivate its operation so that it does not operate until it returns to the communication range with the user device.

[0076] An app running on the user's device can be configured to disable and / or lock the vaporizer depending on location and / or time parameters such as the length of time the vaporizer was outside the user's device's range.

[0077] The app can be configured to enable and / or unlock the vaporizer depending on whether the vaporizer is within a threshold communication range with the user device. For example, the vaporizer can resume operation depending on whether it is within communication range with the user device.

[0078] The vaporizer can be configured to receive information associated with the first user of the first user device. Depending on the vaporizer to which it is communicably coupled, the vaporizer can be configured to activate and / or unlock vaporizer operation within a threshold communication range with the first user device associated with the first user. The vaporizer can be configured to deactivate vaporizer operation depending on the vaporizer to which it is outside the threshold communication range with the first user device. The vaporizer can be configured to deactivate vaporizer operation depending on the vaporizer to which it is communicably coupled with a second user and / or a second user device. For example, if the first user pairs the first vaporizer with the first user device, the first vaporizer can be deactivated and / or locked depending on the second user attempting to pair the first vaporizer with a second user device.

[0079] The user interface examples shown in Figures 13A-13H relate to data for preventing unauthorized use and / or use, purchase, etc., of the vaporizer, as well as lock and reporting functions that may be beneficial in providing specific control over the vaporizer.

[0080] The app screen view in Figure 13A or a similar approach can be used to prompt the vaporizer user to implement a device lock feature. In one example, this may be provided as an "opt-in" feature, such as having a default state where the vaporizer does not automatically enter a locked state. Alternatively, the lock feature may require the user to "opt out" to disable automatic locking. In yet another example, the automatic lock feature may not be a user-configurable option.

[0081] The screen views in Figures 13B and 13C illustrate the views that can be presented to the user when selecting the opt-in feature. This screen can be used to explain that the vaporizer automatically enters a locked state if there is no communication between the user's mobile device and the vaporizer for a period of time longer than a threshold time. Functionally, when this feature is enabled, the vaporizer controller (e.g., a microcontroller, PCB, software running on a programmable processor, or other computing hardware) can perform an operation to track the duration since the last successful communication between the vaporizer and the user's mobile device paired with it. If this duration exceeds a certain threshold, the vaporizer controller can interrupt the normal operation of the vaporizer, for example, by interrupting the supply of current to the heating element or by activating the atomizer, which would otherwise cause the generation of an inhalable aerosol.

[0082] The screen views in Figures 13D and 13E illustrate the transition from disabling or enabling the auto-lock function via the activation of user interface elements such as a slider control (upper left corner of the screen in Figures 13D and 13E). In one embodiment, the user may choose to opt in or opt out of making the auto-lock function available, for example, via the drawings in Figures 13A–13C. At any time, the user may choose to enable or disable the auto-lock function for their vaporizer using the on / off selection shown in Figures 13D and 13E. It may be desirable to disable this function if the user intends to use their vaporizer for a certain period of time when their mobile device is not nearby, or if the user's mobile device needs to be powered off or otherwise unable to communicate with the vaporizer. In some embodiments of this subject, it may be advantageous to have a time limit on the auto-lock disable function. This allows the vaporizer controller to return to the auto-lock enabled state after a fixed or user-configurable auto-lock disable duration has elapsed.

[0083] In some embodiments, the vaporizer device and / or user app may be configured to display a first notification for locked devices that are “in range” (e.g., the user device is within the threshold range of the vaporizer device). In some embodiments, the vaporizer device and / or user app may be configured to display a second notification for locked vaporizer devices that are “out of range” (e.g., the user device is outside the threshold range of the vaporizer device), as shown in Figure 13F. The vaporizer device and / or user app may be configured to display an option for the user to “opt in” to some or all of the “auto-lock” features. For example, the vaporizer device and / or user app may be configured to display a countdown timer for “auto-locked” vaporizer devices on a time basis while they are “in range” (e.g., the user device is within the threshold range of the vaporizer device). In some embodiments, the user may have the option to specify the length of time after which “auto-lock” will become responsive (e.g., a time different from the default time of 24 hours may be provided). In some embodiments, the vaporizer device may be configured to automatically lock the vaporizer device in response to a vaporizer device changing from an “in range” state to an “out of range” state. In some embodiments, the vaporizer device may be configured to automatically lock when the vaporizer device is "out of range" for a defined duration (e.g., 24 hours). In some embodiments, the vaporizer device may be configured to automatically unlock when it returns to a state within range. In some embodiments, the vaporizer device and / or user app may be configured to display an overlay description of the lock / unlock function, as well as images and / or animated GIF representations of the vaporizer device in and out of range.

[0084] In other words, Figure 13F shows a screen view that can indicate that auto-lock is enabled and the vaporizer is not within range of the mobile device (and therefore cannot be used until communication is re-established between the mobile device and the vaporizer). Figure 13G shows an optional screen view that can be included to require a password or some biometric authentication (e.g., fingerprint sensor ID, facial recognition, etc.) to be received by the device by the user's mobile in order to re-authenticate the use of the vaporizer, thereby allowing the mobile device to communicate with the vaporizer's controller and allowing the vaporizer to operate again. Such a cold feature would prevent minors or unauthorized users from using the vaporizer simply by being close enough to the user's mobile device (e.g., in an adjacent room) to allow communication between the mobile device and the vaporizer to be re-established. Figure 13H shows an example of a screen view that can indicate that the vaporizer remains disabled because proper authentication could not be received.

[0085] In some embodiments, a vaporizer lock function that locks (e.g., disables) or unlocks (e.g., enables) the vaporizer device from the user interface of a user device can be configured to be available when the vaporizer is within communication range of a communication device (e.g., when the user device is within threshold range of the vaporizer device). In response to the vaporizer device being locked, the vaporizer device can be configured to disable some or all of the functions of the vaporizer device. In various examples, locking the vaporizer may include disabling the power supply to the heater element, such as ignoring input from a pressure sensor or other switch configured to activate the vaporizer for aerosol generation. In response to detection of attempted intake / revving 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 locked. In some embodiments, locking the vaporizer device can change the state of the home screen on the user interface as follows: a “Locked” notification may be displayed when the vaporizer device is locked, and the user may be able to unlock the vaporizer device from the home screen. The vaporizer device can be configured so that the user can only unlock it through an app to which they are logged into their account. In some embodiments, the lock and / or unlock functionality may be available regardless of whether the user / device has Wi-Fi and / or data service receiving capabilities.

[0086] In addition to the automatic locking function described above, the vaporizer device may be configured to provide “access functionality” to registered app users for account login, with or without age verification (AV). The vaporizer device may optionally be configured so that the availability of access functionality is linked to the app and / or user login, rather than to a specific user mobile device. In some embodiments, a user device using the device app while a particular user is logged into a user account may be able to unlock / lock a particular device previously locked by that user using another instance of the device app.

[0087] Locking the device can be done by disabling the power supply to the heater element, pressure sensor, or other components of the vaporizer.

[0088] In some embodiments, a vaporizer lock function that locks (e.g., disables) or unlocks (e.g., enables) the vaporizer from the user interface of the user device can be configured to be available when the vaporizer is within communication range of the user device (e.g., the user device is within the vaporizer's threshold range). In response to the vaporizer being locked, the vaporizer can be configured to disable some or all of its functions. In response to detection of attempted inhalation / revving (or other attempts to use the vaporizer, such as tapping on the device to query the battery level and / or inserting or removing the pod) on a locked vaporizer, the vaporizer can be configured to display a "Locked" LED indicator, block airflow, and / or provide another indication that the device is locked. This "Locked" indicator may include a locked animation, a battery level animation, an LED animation, a sound, and / or similar. In some embodiments, locking the vaporizer can change the state of the home screen on the user interface as follows: a "Locked" notification may be displayed when the vaporizer is locked, allowing the user to unlock the vaporizer from the home screen. The vaporizer can be configured so that it can only be unlocked by the user via an app to which the user is logged in to their account. In some embodiments, the lock and / or unlock functionality may be available regardless of whether the user / device has Wi-Fi and / or data service receiving capabilities.

[0089] In some embodiments, the vaporizer and / or user app may be configured to display a first notification regarding locked devices that are “in range” (e.g., the user device is within the vaporizer’s threshold range). In some embodiments, the vaporizer and / or user app may be configured to display a second notification regarding locked vaporizer devices that are “out of range” (e.g., the user device is outside the vaporizer’s threshold range), as shown in Figure 28. The vaporizer and / or user app may be configured to display an option for the user to “opt in” to some or all of the “auto-lock” features. For example, the vaporizer and / or user app may be configured to display a countdown timer for “auto-locked” vaporizers on a time basis while they are “in range” (e.g., the user device is within the vaporizer’s threshold range). In some embodiments, the user may have the option to specify the length of time after which “auto-lock” will become responsive (e.g., a time different from the default time of 24 hours may be provided). In some embodiments, the vaporizer may be configured to auto-lock the vaporizer in response to a vaporizer changing from an “in range” state to an “out of range” state. In some embodiments, the vaporizer may be configured to automatically lock in response to the vaporizer being "out of range" for a defined duration (e.g., 24 hours). In some embodiments, the vaporizer may be configured to automatically unlock in response to returning to a state within range. In some embodiments, the vaporizer and / or user app may be configured to display an overlay explanation of the lock / unlock function, as well as images and / or animated GIF representations of the vaporizer device in and out of range.

[0090] The vaporizer can be configured to provide “access functionality” to app users registered for account login, with or without age verification (AV). The vaporizer can be configured so that the availability of access functionality is linked to the app and / or user login, rather than to a specific user device. In some embodiments, a user device using the device app while a particular user is logged into a user account may be able to unlock / lock a particular device previously locked by that user using another instance of the device app.

[0091] The vaporizer can be configured so that the access function operates on the user device without Wi-Fi, LTE, or other internet connectivity. The access function may respond when the device is within Bluetooth Low Energy (BLE) range of the user device and the user is currently logged into their account. In such embodiments, the app may request to unlock or lock the vaporizer without requesting an external server.

[0092] In some embodiments, pairing, locking, and / or unlocking of a vaporizer can be made accessible only through an app logged into a user account linked to the vaporizer. The vaporizer can be configured to self-lock after a prolonged period of disconnection from the user device and / or app. For example, if the vaporizer does not connect to the paired app within a set period (e.g., 1 second, 24 hours, 7 days, and / or other durations), the vaporizer may automatically lock to prevent misuse of a lost or stolen vaporizer.

[0093] The vaporizer can be configured so that the lock function can persist across power events. Configuration and state data for such a function must be retained in non-volatile storage on the vaporizer to withstand power-on resets (POR) and / or other reset conditions.

[0094] The vaporizer can be configured to prevent a locked device from being reset to its factory settings (lock retention function) and can provide an indication to the user that the vaporizer is locked. For example, if a user attempts to "reset a locked vaporizer to factory settings," the vaporizer will display a "locked" LED indicator and will not be reset.

[0095] The vaporizer can be configured so that the lock-holding function includes sufficient security to prevent hacking from disabling the lock function. In some embodiments, a shared private key is required to lock / unlock the vaporizer. The shared private key may be generated by the app and transferred to the vaporizer during a lock request. To unlock the device, the app may be configured to provide challenge / response authentication to the vaporizer using the private key to initiate the unlock sequence.

[0096] A vaporizer can be configured to authenticate links between authorized vaporizers and different user devices owned by the same user account holder. For example, if a user loses their user device, they can log into the app on a new user device and connect the vaporizer to this new device. For vaporizers previously paired with another user device and associated with the user account holder, this vaporizer may be able to pair with a new user device, provided that the app's user credentials are the same as the user credentials used to pair the vaporizer on the previously paired user device.

[0097] The vaporizer can be configured so that an authenticated user does not need to perform “shake-to-pair” (e.g., perform an electronic handshake communication exchange) for the same user device logged into the same user account after the initial pairing and / or linking to the user account. For example, if the vaporizer is linked to a user account (with or without age verification), the vaporizer may “remember” that pairing until it is unlinked from the user account. User credentials can be stored on the vaporizer so that linked app information is retained.

[0098] A vaporizer can be linked and authenticated so that a specific set of features may be provided to the user based on authentication and / or linking (e.g., linked to an account with or without age verification). A vaporizer can be configured so that authenticated and authorized devices are linked and a specific set (full set) of features may be provided to the user via an app.

[0099] The vaporizer can be configured, through authenticated ownership, to prevent a vaporizer owned by another account holder from being linked to another account without the device owner explicitly releasing the vaporizer from the original account. Thus, theft becomes more difficult by communicating that the vaporizer is paired with another account user. For a vaporizer that has been previously paired with another user device and associated with a user account, this vaporizer can only be paired with a new user device, provided that the app's user credentials are the same as the user credentials used to pair the vaporizer on the previously paired user device. In some embodiments, depending on whether the vaporizer is paired with a first user account and / or a first user device, this vaporizer can be configured not to be paired with a second user account and / or a second user device.

[0100] A vaporizer can be configured for authenticated ownership. For example, if a user attempts to link a vaporizer paired to a first user account to a second user account, the user interface can be configured to display the vaporizer and / or the name of the second user (for example, in a case where the user accidentally swapped it with a friend).

[0101] The vaporizer can be configured to communicate with only one user device at a time. For example, the vaporizer may be paired and coupled with only one Bluetooth central user device, such that subsequent pairings and couplings override previous connections.

[0102] The vaporizer can be configured to pair with a Bluetooth central user device when locked, thereby allowing the vaporizer to be unlocked by any Bluetooth central user device logged into the user's account.

[0103] The vaporizers linked to a user can be configured to allow only a specified number of vaporizers to be linked per duration to prevent misuse by minors (e.g., for activating / deactivating youth prevention devices). For example, matching e-commerce regulations allow linking a maximum of 5 devices every 90 days (e-commerce purchase limit). The app can be configured to communicate the date on which the user can link another vaporizer thereafter.

[0104] A vaporizer can be configured to perform "pairing by shake" for the initial pairing of the vaporizer to a user account (to prevent pairing with other vaporizers within range). The vaporizer may provide an indication that it has been shaken and is ready for pairing.

[0105] The vaporizer can be configured to prevent counterfeit vaporizers from connecting to the app and / or cloud during the initial pairing process with the user device. The app can be configured to verify that the vaporizer is not a counterfeit device before the device is linked to a user account and / or any app services (such as firmware updates) are provided. Such a process may utilize industry-standard security procedures to ensure that the service is secure and cannot be hacked.

[0106] The vaporizer can be configured to ensure that the original vaporizer pairs and links only with the manufacturer's official app and cloud for security purposes. The vaporizer can be configured to independently verify that the connected app and / or cloud is provided by the manufacturer and not a third-party service, in order to prevent fraud and other activities not authorized by the manufacturer. Such a process may utilize industry-standard security procedures to ensure that the service is secure and cannot be hacked.

[0107] The vaporizer can be configured so that the initial pairing (of unrelated devices) and linking of the user device must occur when the app has internet access. Internet access may also be required to verify the authenticity of the vaporizer (against counterfeits).

[0108] The vaporizer can be configured to allow users to pair additional devices to their account ("add device"), subject to a limit of five devices per 90 days. The app can be configured to verify such criteria and provide confirmation (or unconfirmed) notifications.

[0109] The vaporizer may be configured to perform a "factory reset" unless the device is locked. This factory reset may include resetting the vaporizer to its brand-new, out-of-the-box state, including clearing the logs, and resetting the data collection "research mode" to "standard mode." If a reset gesture is attempted while the vaporizer is locked (e.g., if the pod is removed and / or inserted), the vaporizer may be configured to indicate "locked" with an LED. The user must first unlock the device to enable the factory reset. Factory reset gestures may include orienting the device vertically so that the pod faces upward, removing the pod, orienting the device so that the pod end faces downward, inserting the pod, removing the pod a second time, orienting the device so that the pod end faces upward, reinserting the pod, and / or similar actions.

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

[0111] The vaporizer can be configured to allow devices not linked to an account (even if they were linked to a user device without authentication) to be re-paired and coupled with any user device and any user account. This allows the device to be restored and coupled with the app, and no ownership structure is imposed on this link until the device is connected to the vaporizer's user account.

[0112] In some embodiments, a vaporizer not linked to another user account may be paired and coupled to a user device and app without requiring the user to log in to the app (for example, in the case of a new vaporizer that the user has not yet logged in or authenticated). However, the app may be configured to provide a limited set of features until the user logs in with an existing user account or creates a new user account.

[0113] In some embodiments, a user may be able to unlink the vaporizer from the associated user account (for example, if the user wants to transfer ownership of the vaporizer or if the vaporizer is lost). In one embodiment, data from the previous user (e.g., usage data) may be visible to the new user of the vaporizer. A vaporizer linked to an account can be released ("unlinked") from that user account via the app, both within and outside of the scope. The vaporizer can be restored to factory settings, including unlocking the vaporizer when it is "locked" and clearing logs, but retains the latest firmware and can be configured to respond to attempts to re-pair the vaporizer with the app.

[0114] The vaporizer may be configured such that it may not function properly (e.g., not produce steam) depending on whether the vaporizer's firmware (main / running image) is overwritten / updated. A static LED pattern (or other indicator) may be provided to warn the user that the vaporizer is being updated. In some embodiments, basic vaporizer functionality may be suspended depending on the firmware loaded in the microcontroller's memory. A static LED pattern (or other indicator) may be displayed in the update state to warn the user that the vaporizer is functioning and updating its firmware.

[0115] In some embodiments, usage data can be tied to a user account so that the data is retained when the user logs into the app on a different user device (or logs out and then logs back in). This usage data may include one or more of the following: steam experience, goal data (e.g., from user preferences, onboarding flow), guided draw results, location history, and / or other usage data.

[0116] In some embodiments, if a user deletes their associated user account in accordance with the General Data Protection Regulation (GDPR), all data associated with that user must be irreversibly and irrevocably unlinked from that user's account. The user app may be configured to unlink user data, provide user data on a per-user request basis (e.g., via CSV and / or similar), and provide the user with a terms of service page.

[0117] In some embodiments, users may verify their age from one of several app locations, resulting in updates related to the app's feature set. The app's account settings page may display "Age Verified" for each user country (or other geographical area) and may include other information related to the user and / or the account associated with the user. Activated features may include checkout, vaporizer replacement, external web pages, mobile sites, and / or other features. Checkout, vaporizer replacement, and other features may require age verification. Age verification can be accessed from one or more of the following: checkout (e.g., shopping), account menu, vaporizer replacement flow, login, internet connection, and / or other app features. A user's age verification status may be reflected in account settings. The app may provide information about the age verification status and the countries where verification applies. Users may be offered options for age verification from the app. In response to unverified requests, external mobile web pages may be provided.

[0118] User age verification In some embodiments, the age verification procedure may include verification using a database service. In some embodiments, the user may be age-verified using personal user information such as a social security number, credit history, facial recognition, and / or similar. In some embodiments, the user's name and phone number may be verified using two-factor authentication (e.g., receiving a code via text message). Other age verification procedures may include a “passport” function. For example, the user may create authenticated usage identification information through the user interface of the user device. The vaporizer may be configured to deactivate its function if it moves away from the associated user device. The function can be re-enabled upon returning within the vicinity of the threshold of the associated user device. In some embodiments, the vaporizer may remain activated upon exceeding the user device threshold proximity for a limited duration (e.g., the vaporizer may lock once a given duration has been exceeded).

[0119] Age verification can also be correlated with location information to determine whether a user meets an age threshold. For example, a vaporizer and / or application may receive Global Positioning System (GPS) information to identify the location of the vaporizer and / or application. In some embodiments, the age threshold may be based on a geographical location, such as a specific country, state, city, county, and / or similar. When the age threshold changes 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.

[0120] Using proximity detection to implement such multi-factor authentication can reduce the likelihood of minors using and / or misusing vaporizers. Alternatively, correlating proximity and / or location information with age verification and / or identification information can provide greater flexibility in preventing vaporizer operation in designated areas.

[0121] The vaporizer can be configured to receive vaporizer settings from the user via the app. Vaporizer settings can include changing the vaporizer name. The user account can be configured to remember the user's vaporizer settings. This allows the user's previous settings to be saved when the user logs into the user account on a new user device. Vaporizer settings saved by the user account can include brightness, lock status, low battery alert, vaporizer name, and / or other settings. The user account can be configured to unlink the vaporizer from the user account. As a non-limiting example, depending on the user's selection of "Unlink Vaporizer," for example, "You can unlink from your account."<JOHN’S JUUL> A prompt such as "Do you really want to unlink it? The vaporizer will be reset to factory settings and may be linked to any other user's account" may be presented. If the user selects "Yes," the vaporizer can be unlinked. If the user selects "No," unlinking will not delete usage data from the user's account, but unlinking will delete all location data and / or may remove the vaporizer from the location feature.

[0122] Additionally, the vaporizer settings may include the vaporizer's warranty and / or registration status. Depending on the unregistered vaporizer (for example, if the vaporizer is not linked to the account because the user is not logged into the account), vaporizer information may be provided, and a warranty registration page may be displayed prompting the user to create or log in to a user account. In some embodiments, the app may be configured to allow the user to create a new account and / or log in to an existing account using existing Google, Facebook, and / or other account login information.

[0123] In some embodiments, the carburetor battery level can be displayed on the user device without enabling the carburetor app. For example, "Battery Service" can be configured to display the carburetor battery level as an icon through the user interface of the user device. Such carburetor information may be displayed depending on whether the carburetor is within a threshold range on the user device.

[0124] Monitoring - Health and Stoppage Applications running on a vaporizer and / or device, which are part of a vaporizer system consistent with the embodiments described herein, can also be configured to monitor usage for purposes such as digital health regimens and / or smoking cessation. For example, similar to weight loss monitoring devices, a vaporizer or an app, or both, can be useful for people who want to reduce their nicotine intake and / or track the amount of nicotine consumed within a given duration. For example, a vaporizer and / or app could be configured to allow dual users of cigarettes and e-cigarettes to log in and compare the total amount of HPHC and nicotine consumed each day when different combinations of cigarettes are used.

[0125] The app and / or vaporizer can provide additional motivation by offering messaging such as reporting how much of compound X is being consumed, and can also show how much money former smokers are saving by reducing or eliminating smoking. This is most relevant to nicotine, but can be used for other substances as well. In some embodiments, users can input the usual price of those per pack of cigarettes, which can be used as a baseline. This can also be relevant to THC, as vaping (hereinafter also referred to as e-smoking) is a more effective means of consumption. Case data shows that there can be a 5-10 times difference between smoking and e-smoking. For example, someone who e-smoks x mg of THC in a given time interval would otherwise be smoking 10 times the amount of THC in mg units. Based on dosage monitoring by the device, the vaporizer and / or app can report the amount of savings regarding how much the user smoked in other ways.

[0126] In some embodiments of this subject matter, the app may also allow the user to record other health-related activities, such as from a fitness app, and / or suggest correlations between nicotine or THC use and alcohol consumption, heart rate, blood pressure, exercise time, or weight changes. For example, the user may input preferred unit doses, dosing intervals, or total daily goals (using presets or estimated / recordable / programmable data as described herein). The vaporizer and / or app may be locked out after each dosing, and an alert may pop up on the user's computing device (phone, smartwatch, tablet, etc.) when it is time for the next dosing, and the vaporizer may also be automatically unlocked for this next dosing. This can be used as a reduction approach chosen by the user (gradual reduction or discontinuation) or to maintain a prescribed treatment regimen (e.g., X mg of the drug every Y hours, but not exceeding Z mg / day). In some embodiments, the vaporizer and / or app may capture and record user and / or vaporizer usage information that can be fed back to the app (e.g., via Bluetooth®, Wi-Fi, etc.), and may optionally provide recommendations regarding a nicotine withdrawal program based on the captured and / or recorded data (including device usage and additional information) and / or usage patterns determined therefrom. In some embodiments, the recommendations may include a withdrawal plan based on data and / or patterns implemented using the app and device (e.g., by locking the device at predetermined times according to a plan).

[0127] In some embodiments, the vaporizer and / or associated applications may have a dashboard-style user interface that allows users to log in and track their progress over time. The data may be based on individual and / or group data. For example, group data could represent the average smoking / e-smoking switch rate for the population at any point since starting to use the vaporizer. The device may provide a screen for users to select other users and define groups (cohorts) based on their starting conditions, such as the number of packs per day, age, gender, etc.

[0128] Device control and customization As described herein, the vaporizer may be partially controlled by user input to a related application. For example, certain embodiments of the vaporizer that can be controlled may include changing the temperature setpoint, for example, to allow the user to obtain less vapor when it needs to be inconspicuous. This, too, may allow the user to reduce frustration with each rev and consumption of active ingredients.

[0129] The app can also provide a more accurate display of the battery level than what is shown on the carburetor. For example, while charging, the app can display the remaining time.

[0130] As described herein, the app can also provide firmware updates to the vaporizer.

[0131] For devices that accept both nicotine and THC cartridges, the associated (connected) app may also allow the user to switch between nicotine mode and THC mode, which are likely to have different temperature settings.

[0132] A device that is part of a vaporizer and / or vaporizer system may use a received signal strength indicator (RSSI) to help a user find a lost vaporizer. Additionally, an app may cause the vaporizer to vibrate, flash, and / or emit a sound as an alarm to the user, including to help find a misplaced device. For example, temperature changes, vibrations, or flashing lights may also be indicators of whether or not a vaporizer is hidden nearby. In some embodiments, the vaporizer may also help find a misplaced phone when connected by changing the color of an LED depending on the distance between the vaporizer and the phone.

[0133] One or more network devices can be configured, with one or more processors, to receive information related to a vaporizer, communicate the received information related to the vaporizer to an app, and determine a unique identifier associated with the vaporizer. Network devices can include user devices of other vaporizer users. An app can be configured to determine whether a vaporizer is within communication range of one or more network devices. A vaporizer can be configured to emit a signal in response to prompts communicated by network devices. For example, if a vaporizer is left behind in a location beyond the range of a user device, one or more network devices can receive a "device lost" notification, and the lost vaporizer can emit a signal in response to being within communication range of one or more network devices. Network devices can be configured to transfer location information to the user device when the vaporizer is found. A vaporizer can be configured to disable and / or lock in response to prompts communicated by network devices.

[0134] The vaporizer and / or app can be used to adjust the brightness and color of the vaporizer's LEDs. For example, in the case of a vaporizer with multiple LEDs, the user can download personalized indicator patterns to the device. In addition to making the vaporizer feel more personalized, the vaporizer may have extended utilities that make it easy to identify which vaporizer belongs to a particular owner.

[0135] In some embodiments, the vaporizer temperature can be adjusted by using a graphical user interface that allows both overall and precise control of the vaporizer temperature with a single finger. For example, the graphical user interface (GUI) may include a temperature display that visually shows the current and / or target temperature of the vaporizer. This temperature can be adjusted up or down (within a range). In this example, to adjust the temperature, the user can hold their fingertip over or on the opposite side of the indicator, and the indicator will appear on either side of the temperature when the vaporization temperature can be adjusted up (to the right) or down (to the left). By quickly sliding a finger over adjacent indicators, the temperature setting can be moved rapidly in large increments (e.g., 3, 5, 10, 15, 20, 25, 30, 35 degrees, etc.). Large increment adjustments are indicated by large circles. Fine temperature control can be opened by holding a fingertip over the temperature indicator or an adjacent indicator for a predetermined duration (e.g., 1 second, 2 seconds, 3 seconds, 4 seconds, 5 seconds, etc.). By moving the diagram along this fine-grained temperature control, you can increase or decrease the selected temperature in small increments (e.g., 0.1°C, 0.5°C, 1°C, 2°C, etc.). The temperature change is displayed on the central temperature indicator.

[0136] Figure 6 shows an exemplary computing device 600, whose features can be used in some exemplary embodiments. It should be understood that not all of the components shown in Figure 6 need to be on the same single device or apparatus. A given function may be divided, for example, between the vaporizer and the user device. In other examples, the function may be distributed between the user device and the vaporizer, which includes two or more separable components (e.g., a charger unit and a vaporizer). For example, at least a portion of the computing device 600 may be included as part of vaporizer 100, vaporizer 200, user device 305, remote server 307, beacon 705, user device 805, and / or one or more other components of the vaporizer system. Components of the computing device 600 can be implemented additionally or alternatively from any component of the illustrated and / or described vaporizer apparatuses 100, 200. The computing device 600 can be implemented to perform one or more of the processes described herein.

[0137] The computing device 600 can perform one or more of the processes described herein. For example, the computing device 600 can be used to perform an application that provides user control of a vaporizer communicating with the computing device 600, and / or to provide an interface for the user to engage with and interact with functions associated with the vaporizer, according to some exemplary embodiments.

[0138] As shown in the figures, the computing device 600 may include one or more processors, such as a processor 610, to execute instructions that can perform operations consistent with those described herein. The computing device 600 may include memory 620 for storing executable instructions and / or information. Memory 620 may include solid-state memory, solid-state disk drives, magnetic disk drives, or any other information storage devices. The computing device 600 may include a network interface 640 to a wired network or a wireless network, such as the network described with reference to Figure 5. To enable wireless communication, the network interface 640 may utilize one or more antennas, such as an antenna 690.

[0139] The computing device 600 may include one or more user interfaces, such as user interface 650. User interface 650 may include hardware or software interfaces such as a keyboard, mouse, or other interfaces, some of which may include a touchscreen integrated with display 630. Display 630 can be used to display information such as information related to the function of the vaporizer, to prompt the user, to receive user input, and / or similar purposes. In various embodiments, user interface 650 may include one or more peripheral devices, and / or user interface 650 may be configured to communicate with these peripheral devices.

[0140] In some embodiments, the user interface 650 may include one or more sensors and / or an interface to one or more sensors as described herein. The operation of these sensors may be controlled at least in part by the sensor module 660. The computing device 600 may include input and output filters 670 that can filter information received from sensors or other user interfaces, information received and / or transmitted via the network interface 640 and / or similar, etc. For example, a signal detected by a sensor may pass through the filter 670 for appropriate signal conditioning, and the filtered data may then be passed to the sensor module 660 and / or processor 610 for validation and processing (e.g., before transmitting results or displays via the network interface 640). The computing device 600 can be powered by using one or more power sources, such as a power supply 680. As shown in the figures, one or more components of the computing device 600 are communicable and / or power-receiving via the system bus 699.

[0141] Any device described herein may include a device lock as described herein. For example, an app (e.g., running on user device 305) and / or vaporizers 100, 200 can authenticate to a mobile device (e.g., user device 305) using encryption as an anti-counterfeiting mechanism. A similar scheme can be used to link vaporizers 100, 200 to a user device (e.g., a mobile communication device such as a phone, smartwatch, tablet, or computer owned or used by the user), thereby allowing the vaporizer to be disabled so that it cannot be used by someone else if stolen. In some embodiments, vaporizers 100, 200 can periodically connect to user device 305 using a network interface 640 to verify and / or authenticate the user's use and / or age. In some embodiments, the user can connect to an application on user device 305 or a computer to provide authentication to enable the operation of vaporizers 100, 200. In some embodiments, authentication may include password or PIN entry, defined gestures (e.g., triple taps), selection of a confirmation button, voice authentication, or biometric authentication (e.g., facial recognition) entered into the application using the user interface 650.

[0142] The vaporizers 100,200 described herein may also include parental lockout (e.g., child protection). For example, the vaporizers 100,200 can be "locked" for parents who want to ensure that their children or other minor users cannot use the vaporizer. In the case of parental lockout, in addition to Bluetooth® or other relatively long-range communication, the vaporizers 100,200 may also have Near Field Communication (NFC) tags implemented on the vaporizer. The NFC tags can be implemented on the computing device 600 (e.g., using a sensor module 660, a network interface 640, an I / O filter 670, and / or a user interface 650). The NFC tags can be configured to store and transfer information. NFC readers are built into many smartphones. One characteristic of NFC is that it only works over a very short range. This makes it easy for the user to unlock the vaporizer. For example, a user can simply tap an already authenticated phone against the vaporizer, thereby allowing the vaporizer to obtain one or more authentication codes from the phone and unlock the vaporizer (in some cases, after the phone itself has been unlocked by an authenticated user in some conventional way). In some embodiments, an authenticated user device can activate an NFC tag on vaporizers 100,200, and the vaporizers 100,200, and the NFC tag can communicate information and / or identifiers to the user device 305 via the network interface 640 and / or antenna 690 to enable the unlocking of the vaporizer. NFC tags are very inexpensive and small and can be used in addition to, or instead of, other wireless communication modes such as Bluetooth. NFC can be used to perform some of the other functions described herein.

[0143] In some embodiments, authentication can be performed by vaporizers 100, 200. For example, vaporizers 100, 200 may include a thumbprint / fingerprint sensor (e.g., as part of sensor module 660). This thumbprint / fingerprint sensor enables the vaporizer to operate based on the authenticated thumbprint / fingerprint. The vaporizer may also include other biometric sensors (e.g., as part of sensor module 660) for authentication purposes. For example, vaporizers 100, 200 may include sensors capable of iris recognition, facial recognition, voice recognition, DNA recognition, etc. In another example, vaporizers 100, 200 may require a specific action / gesture to enable operation. Specific actions or gestures may include password or PIN entry, a defined gesture (e.g., triple tap), voice authentication, selection of a confirmation button, or biometric authentication (e.g., facial recognition). In some embodiments, processor 610 can receive these inputs from sensor module 660 or other components of computing device 600 and determine whether authentication was successful.

[0144] In some embodiments, it may be beneficial to implement authentication / child lock procedures at different points in time or stages of use of vaporizers 100,200 for better protection against misuse. The authentication / child lock procedures may be the same for each duration / stage, or may vary depending on the duration / stage, or depending on any combination of the authentication / child lock procedures described herein for the same or different durations / stages.

[0145] For example, in some embodiments, the vaporizer may require a first authentication at the time of initial purchase of the vaporizer device 100,200, or around that time. In some embodiments, the first authentication may include locking the vaporizer 100,200 to prevent any use of the vaporizer until the consumer's age is verified and the age threshold is met. In some embodiments, the processor 610 may perform the first authentication and / or lock in response to input received from the sensor module 660 or other components of the computing device 600. The first authentication may include single-step or multi-step authentication. The lock may occur at the manufacturer, retailer, or at any stage in the manufacturing, distribution, or retail process. The type or method of the first authentication may depend on the retailer, location, or method in which the device was purchased. In some embodiments, the consumer may be free to use the vaporizer for a certain period after purchase (e.g., 1 day, 7 days, 30 days, etc.) before the initial authentication (e.g., age verification) is required. The vaporizer can be configured to lock (for example, to disable its functionality) upon the expiration of a threshold period, without completing the first authentication or without completing device registration by the user via the user interface.

[0146] In some scenarios, the initial authentication and unlocking of a device may occur at a point of sale (POS), either online or in a retail store. In a retail store, initial authentication may include the retailer checking the consumer's age and identification information. This check may include a visual inspection of the consumer's identification document (such as a driver's license or passport). This check may also include the retailer swiping or scanning a barcode, QR code, or other encrypted code on the identification document to read and verify the consumer's age and / or identification information.

[0147] In some embodiments, the retailer may manually enter or scan age / identification information into a computer application that verifies the consumer's identity and / or age. For example, the retailer may equip a tablet, laptop, desktop, or other computing device running an application related to the vaporizer. In some embodiments, the application may be tailored to the retailer so that the retailer can more accurately verify and identify the consumer's age. The consumer or retailer may use the application to register a device and provide the application with their identification information and age-related information. The application can then perform initial authentication to verify the consumer's age and identity. In some embodiments, the application may communicate with a vaporizer application database or a third-party system to complete the initial authentication. In some embodiments, the application may retrieve a 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's information for later use. The retailer's app may also communicate with one or more servers and / or databases to determine whether the consumer is associated with suspicious activity (such as a bulk purchase of devices) in order to flag or block the transaction. Such tracking can be useful in identifying consumers who may be attempting to resell devices to minors or other unintended users, having circumvented initial authentication or other authentication / youth prevention measures.

[0148] Online retailers can also perform the first authentication. For example, to purchase a vaporizer online, a consumer may be asked to enter their identification information, including their age. The retailer can verify that the entered information has legitimate access to a database containing consumer identification information (such as social security, land transport, or tax records), or the retailer can contract with a third party that has access to such information to verify that the entered consumer information is correct and that the consumer meets the age threshold. The third party can receive the consumer information on a server, and the server can respond to the retailer along with a determination of the consumer's age / identification information. The first authentication may involve a multi-step authentication process in which, after the consumer has entered their information (e.g., contact information), the retailer, manufacturer, etc., sends a code to the consumer (e.g., via an application, text message, email message, etc.) to enter before the user can complete the purchase. In some embodiments, the consumer and / or retailer enter this code when the vaporizer is paired with a smartphone, tablet, computer, or other computing device. If the consumer and / or retailer enter the correct code, the sale may be authenticated. Otherwise, the sales transaction may be terminated. In some embodiments, consumer information can be stored for the creation of a user profile. This user profile may be stored in a vaporizer, application, server, or other computing device.

[0149] In some embodiments, a retailer (online or in-store) may authorize the unlocking of a phone after initial authentication. For example, a manufacturer, vaporizer company, distributor, or other entity may provide a retailer with a code or PIN to unlock the vaporizer device after the initial authentication check is successful. This code may be provided to the retailer by a computer application, text message, email message, printed document, etc. In some embodiments, the code may be predetermined or randomly generated. A predetermined code may be based on a unique characteristic of the vaporizer (e.g., serial code, manufacturer code, etc.). The code may be valid only for a predetermined period after generation. In some embodiments, the retailer may have access to an application that communicates wirelessly with the vaporizer device. This application may prompt the retailer to verify the result of the initial authentication, and further, this application may send the retailer a code to unlock the device via an application interface, text message, email message, etc. The retailer can then enter the code into the vaporizer device or the application that communicates with the vaporizer device to unlock the vaporizer for consumer use. For example, after a retailer receives a message containing a code, the retailer can enter the code into their vaporizer application. This application then transmits a signal to the vaporizer to unlock it.

[0150] In some embodiments, consumers may be provided with a code to unlock the device. For example, once a consumer receives a vaporizer device, they may register the vaporizer online via a webpage or through an application running on their smartphone, tablet, laptop, or other computing device. In some ways (e.g., by checking approved identification information to ensure the consumer is of legal age or older), after the consumer has been authenticated, the webpage or device may provide the user with a code via a webpage or application interface, text message, email message, etc. The consumer may enter the code into the vaporizer's interface / input to unlock the vaporizer. In other embodiments, the consumer may enter the code into a webpage or application communicatively coupled to the vaporizer, and the webpage or application may unlock the vaporizer by sending a signal to the vaporizer for the consumer to use. In some embodiments, the consumer enters the code when the vaporizer is paired with the consumer's smartphone, tablet, computer, or other computing device.

[0151] In some embodiments, an application or web page may request further input to complete a first authentication. For example, an application may request a fingerprint to start the application and / or to authorize the use of the vaporizer. In some embodiments, a fingerprint sensor on the vaporizer device may receive the consumer's fingerprint and transmit the received input to the application. In other examples, a fingerprint sensor on a smartphone, tablet, laptop, or other computing device may transmit fingerprint information to the application. In some embodiments, the application may store the fingerprint information in a database for future retrieval. While fingerprints are described in some examples, the concept can be similarly applied to other biometric feedback such as retinal scans or facial scans and analyses.

[0152] Additionally, the application and / or webpage may perform further verification to complete the first authentication. For example, after receiving the consumer's age and / or identity information, the application or webpage may perform a check to determine whether the user and / or user profile associated with the received consumer information is linked to suspicious activity. For example, the application or webpage 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 embodiments, if the number of vaporizers meets a threshold, the application and / or webpage may flag or identify the consumer as an unauthorized reseller of vaporizers and block the transaction.

[0153] In some embodiments, the application and / or webpage may initiate a live chat where the consumer can provide their identification (e.g., driver's license, passport, etc.) to the broadcaster on the other end of the communication to verify the consumer's identity and / or age. Additionally, the application and / or webpage may be configured to accept scanning of the identification and / or the magnetic stripe of the identification, as well as / or scrutiny of the identification by a person, which are analyzed by the application and / or webpage.

[0154] After the initial purchase of the vaporizer device, it may be desirable to ensure that the vaporizers 100,200 are used only by their intended consumers. For example, if a vaporizer is lost or stolen after the first authentication (e.g., purchase authentication), a second authentication for using the vaporizer can prevent its use by undesirable users (e.g., minors, thieves, etc.). Therefore, a vaporizer may require a second authentication after the first authentication that enables its use. This second authentication may occur when the consumer first attempts to use the vaporizer, or around that time. In some embodiments, the consumer may be free to use the vaporizer for a certain period after purchase (e.g., 1 day, 7 days, 30 days, etc.) before the second authentication (e.g., age verification) is required. In some embodiments, the processor 610 may perform the second authentication and / or lock in response to input received from the sensor module 660 or other components of the computing device 600.

[0155] In some embodiments, the second authentication may be performed by an application running on a user device communicating with the vaporizer. This application may reside on the consumer's smartphone, tablet, laptop, watch, wearable device, or other computing device. For example, the second authentication may include fingerprint authentication. In some embodiments, the vaporizer may permit fingerprint input during the second authentication if it matches the fingerprint analysis during the first authentication. The consumer may input their fingerprint using a fingerprint sensor on the vaporizer or a fingerprint sensor on a computing device (e.g., a smartphone, tablet) that is communicating with or running the application. In some embodiments, this second authentication may include other biometric information of the consumer to verify that the same user is using the device as during the first authentication.

[0156] In some embodiments, the second authentication can be correlated with user information or a user profile created at or before the second authentication. For example, during the first authentication, a consumer may enter their age information (e.g., by scanning a driver's license, manually entering their date of birth in an application) along with a first fingerprint sample. During the second authentication, the consumer may enter a second fingerprint sample. If the second fingerprint sample matches the first fingerprint sample, the vaporizer and / or application can correlate it with the consumer's age information entered during the first authentication to verify the consumer's age during the second authentication.

[0157] In some embodiments, the computing device running the application can be used to provide a second authentication. For example, a vaporizer can remain locked unless the vaporizer device is within a predetermined proximity range of the computing device running the application. In some embodiments, the application may run on a consumer's smartphone, and the vaporizer remains locked until the smartphone comes within a proximity threshold to the vaporizer.

[0158] Additionally, the vaporizer may be unlocked within a proximity threshold and may transition to a locked state if the distance between the vaporizer and the user device running the application moves outside the proximity threshold. In some embodiments, the transition to a locked state may be based on a time threshold while the vaporizer and smartphone are outside the proximity threshold. This time threshold may include a pre-programmed time threshold or a user-selected time threshold. For example, the user may input a time threshold into an application running on their smartphone.

[0159] In some embodiments, a user carrying a user device may walk away from the vaporizer (or otherwise move). Once the user and smartphone move outside the proximity threshold, a timer may run on the application and / or vaporizer. Once the timer reaches the time threshold, the vaporizer may enter a locked state. In some embodiments, the vaporizer and / or computing device may detect proximity via Bluetooth®, Near Field Communication (NFC), Wi-Fi, ultrasound, ZigBee, RFID, cellular communication, or any other wireless communication. In some embodiments, the vaporizer may time out after a predetermined set time has elapsed since the unlocked use following a second authentication, and a similar second authentication may be required to resume authenticated use.

[0160] The proximity locking and unlocking described herein may include steps in multi-step authentication. For example, proximity detection may be correlated with additional identification information to verify that the vaporizer is owned by a user (e.g., registered with the user) and / or that a smartphone application is associated with the same user. This proximity detection may also be correlated with age verification information to verify that the user who owns the vaporizer and / or the user associated with the application meets an age threshold. In some embodiments, the application may store a user profile of the user that stores age verification information such as date of birth and age threshold information.

[0161] A user profile may also include the maximum number of vaporizers a user is permitted to use. For example, to prevent a single user from authenticating multiple devices for the purpose of later resale to a minor or other undesirable consumer, a user profile may specify that a user is associated with only one vaporizer at a time. For example, if a user owns multiple vaporizers and a smartphone application is paired with a first vaporizer, other vaporizers owned by the user may be locked. In some embodiments, the smartphone application may send a signal to other vaporizers to lock them. In other embodiments, each time the application and a vaporizer are paired, the application and / or the vaporizer may perform a check to determine whether the user is associated with other vaporizers that are currently unlocked. If so, the application may first lock the other vaporizers and / or unpair them before pairing with the current vaporizer.

[0162] In some embodiments, 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 has verified their age. The ordered vaporizer can be configured to pair with the user profile that ordered the vaporizer. In some embodiments, the vaporizer can be configured to pair only with pre-programmed user profiles. This can reduce or eliminate further re-authentication.

[0163] Age verification can also be correlated with location information to determine whether a user meets an age threshold. For example, a vaporizer and / or application may receive Global Positioning System (GPS) information to identify the location of the vaporizer and / or application. In some embodiments, the age threshold may be based on a geographical location, such as a specific country, state, city, county, and / or similar. When the age threshold changes 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.

[0164] Using proximity detection to implement such multi-factor authentication can reduce the likelihood of minors using and / or misusing vaporizers. Alternatively, correlating proximity and / or location information with age verification and / or identification information can provide greater flexibility in preventing vaporizer operation in designated areas.

[0165] In some embodiments, the second authentication can be completed electronically without the need to download an application. For example, a user can access a website to register their device and / or age. In some embodiments, a user can enter the serial number of their device and then be prompted for age verification (e.g., by entering identity information, live chat, scanning an ID, or using any authentication method described herein). After successful age verification, the user can receive a passcode from the website. In some embodiments, each passcode is a random number associated with its serial number (e.g., a hidden 4-digit serial number). After receiving the passcode, the user can then pair the vaporizer with their user device, for example, by Bluetooth® or some other communication protocol. This pairing may require a website passcode (e.g., a 4-digit or multi-digit passcode) or another passcode to complete the pairing. If the correct passcode is entered and pairing is successful, the device can be unlocked.

[0166] In some embodiments, a dongle can be used to provide a second authentication. In some embodiments, the dongle may include any hardware device that connects to the vaporizer or other computing device to provide additional functionality. For example, the dongle can function as a communication bridge between the vaporizer and an application, or between the vaporizer and another computing device. In some embodiments, the dongle can be connected to a computing device that does not run an application that communicates with the vaporizer. The user can then communicate with the vaporizer on the computing device by using the dongle. Additionally, in some embodiments, an application running on the computing device may lose communication with the vaporizer. The application can communicate with the dongle, and the dongle can communicate with the vaporizer. In other embodiments, the dongle can be configured to provide code that allows the vaporizer to operate and / or communicate with the vaporizer. For example, the dongle can be configured to provide a randomly generated number or pattern for the user to enter the application and / or the vaporizer and allow it to operate. In some embodiments, the code generated by the dongle can be set to expire after a predetermined duration (e.g., 60 seconds, 5 minutes, 1 hour, etc.). Subsequently, additional use of the vaporizer will require a further new certification code.

[0167] In some embodiments, the vaporizer and / or smartphone may provide an indication that the vaporizer is unlocked. For example, the vaporizer and / or smartphone may output an audible, visual, tactile, or other indication that the vaporizer is unlocked and ready for use by the user. Audible indications may include beeps, clicks, songs, or any other sounds. Visual indications may include light, color, patterns of light, a series of flashing lights, or any other visual indications. Tactile indications may include vibration pulses, a series of vibration pulses, patterns of vibration, or any other tactile indications.

[0168] In some embodiments of this subject matter, the second authentication (or authentication as a whole) may be based on the location of the vaporizer. For example, a given location may include hardware ("beacon") configured to modify the operation of vaporizers located within the communication range of a beacon. Figure 7 shows a communication exchange between vaporizers 100A, 200A, 100B, 200B and a deactivated beacon 705, according to some exemplary embodiments. As shown in Figure 7, the beacon 705 includes a transceiver 701, a processor 702, a memory 703, and a network interface 704. In some embodiments, the processor 702 may be configured to execute instructions that can perform operations consistent with those described herein. The memory 703 stores executable instructions and / or information. The memory 703 may include solid-state memory, a solid-state disk drive, a magnetic disk drive, or any other information storage device. The network interface 704 may be configured to interface with a wired network or a wireless network. To enable wireless communication, the network interface 704 can utilize, for example, one or more antennas and / or transceivers such as transceiver 701.

[0169] In some embodiments, the beacon 705 may be installed in locations where sensitivity to unauthorized or undesirable use of vaporizers is likely to be increased (e.g., schools, youth areas, inside restaurants, commercial airplanes, or other public transport vehicles). In some embodiments, the beacon 705 may be configured to disable vaporizers within the communication range 725 of the beacon 705. As shown in Figure 7, vaporizers 100A, 200A, 100B, and 200B are located within the communication range 725 and can be disabled by the beacon 705. In some embodiments, the beacon 705 may be configured to forward broadcast messages via the transceiver 701 and / or the network interface 704. Vaporizers 100A, 200A, 100B, and 200B can receive broadcast messages via the network, and controllers 105 and 205 may be configured to disable the operation of the vaporizers in response to the reception of broadcast messages.

[0170] In some embodiments, the beacon 705 and / or broadcast message that disables vaporizers 100, 200 may be overridden by further age verification (e.g., a second authentication as described in various embodiments herein). For example, a general consumer may activate their vaporizers even though vaporizers 100, 200 are within communication range 725 by performing any authentication procedure described herein (e.g., entering a code, using a phone app, biometric information, etc.). For example, the beacon 705 may transmit a communication to vaporizers 100A, 200A, 100B, 200B and / or consumer vaporizer applications to notify consumers that vaporizers 100A, 200A, 100B, 200B are within communication range 725. In some embodiments, the vaporizer 100A, 200A, 100B, 200B and / or consumer vaporizer application may display an indication that the vaporizer 100A, 200A, 100B, 200B is locked. Once notified, the user of the vaporizer 100A, 200A, 100B, 200B can log in to the vaporizer application and / or use the vaporizer 100A, 200A, 100B, 200B to perform a second authentication while still within communication range 725, thereby reactivating the operation of the vaporizer 100A, 200A, 100B, 200B.

[0171] In other embodiments, vaporizer 100A, 200A, 100B, 200B and / or vaporizer application may detect beacon 705 and notify the consumer to complete a second authentication or any other authentication that enables the consumer to use the vaporizer within beacon communication range 725. For example, vaporizer 100A, 200A, 100B, 200B and / or vaporizer application may forward communications to search for other devices within the communication range of vaporizer 100A, 200A, 100B, 200B and / or vaporizer application. In some embodiments, beacon 705 may receive communications from vaporizer 100A, 200A, 100B, 200B and / or vaporizer application and respond with communications that disable vaporizer 100A, 200A, 100B, 200B. Next, the user can perform a second authentication to reactivate vaporizers 100A, 200A, 100B, and 200B within communication range 725.

[0172] In some embodiments, the beacon 705 can be geofencing to ensure it operates within a predetermined location. Such geofencing can help prevent the beacon 705 from being transported to another location where vaporizer deactivation is undesirable. In some embodiments, the processor 702 and / or memory 703 can be configured to retrieve geolocation information to determine the location of the beacon 705 and whether the beacon 705 is permitted to operate at that location. If the beacon 705 is outside its permitted area, the operation instruction from memory 703 to the processor 702 can be configured to deactivate the beacon 705. Hardware beacons 705 can beneficially provide additional security / protection against the use of vaporizers by minors in high-risk areas (e.g., school zones).

[0173] In some embodiments, the beacon 705 may also be configured to track and / or report vaporizers 100,200 within the communication range 725 of the beacon 705. For example, an application communicating with one or more beacons 705 may be configured to display a list or graphic representation of vaporizers within the communication range 725 of one or more beacons. For example, the graphic representation may include a map showing the vaporizers 100,200 within the communication range 725. This map or user interface may also include additional information about the vaporizers 100,200 (e.g., serial number, model number, etc.) and / or additional information about the user associated with the vaporizers 100,200 (e.g., date of birth, age, registered school, etc.). This tracking allows an administrator of an application or entity (e.g., a school) to monitor which vaporizers are located within the area and whether any vaporizers are authorized for use within that area. For example, a school principal can monitor vaporizers located within the communication range 725 of one or more beacons 705 to determine whether vaporizers 100,200 associated with students of the school have been used or activated within the communication range 725. In some embodiments, the application allows the principal or authorized administrator to report any unwanted or unauthorized use of vaporizers to the authorities and / or manufacturers in order to improve the prevention of unintended use. Additionally, information regarding the unauthorized use of vaporizers within a given area may also be forwarded to the actual authorized owner and / or user of such vaporizers (e.g., a parent or guardian).

[0174] In some embodiments, the beacon 705 can be configured to unlock vaporizers 100,200 within the communication range 725. For example, vaporizers 100,200 can be configured to lock in locations outside the communication range 725, and the beacon 705 communication can be configured to unlock the vaporizers 100,200. Such examples can be used as designated "smoking areas" in areas where the use of vaporizers is generally prohibited (e.g., schools, airports, etc.).

[0175] In some embodiments, the beacon functionality may be installed in an application running on a user's smartphone, tablet, computer, or other computing device, rather than a hardware beacon 705 installed in a predetermined location ("application beacon"). Similar to the hardware beacon 705, this application beacon can be configured to modify the operation of vaporizers within the communication range of the application beacon. For example, all vaporizers within the communication range of the application beacon can be disabled, or additional age verification (e.g., a second authentication) can be required to unlock the use of vaporizers while within the communication range.

[0176] The vaporizers 100,200 may include or be connected to a “Youth Prevention Device” (YPD) configured to lock out the vaporization function of the vaporizer in response to an encounter with a Youth Prevention Beacon Device (e.g., beacon 705 and / or beacon 805). The YPD may include a controller 105,205, an app, or any other component of the vaporizers 100,200, a user device 305, a remote server 307, and / or a computing device 600. For example, a vaporizer 100,200 with a YPD may enable a “Youth Prevention Function” (YPF), in which case the vaporizer 100,200 may be shut down (e.g., disable vaporization) for 30 minutes (or other duration) when the vaporizer enters the range of a Youth Prevention Beacon Device. The YPD may be configured to ensure that the vaporizer shutdown is reliably guaranteed. This security measure may be implemented to ensure that unauthorized users cannot arbitrarily develop a PD shutdown function in order to otherwise interfere with or interrupt services intended for users whose access permissions should not be revoked.

[0177] In some embodiments, the ability of the youth prevention device to act on vaporizers 100,200 can be made dependent on the age verification status of vaporizers 100,200. For example, registered and age-verified vaporizers 100,200 can be made "invisible" to YPD. Youth prevention features may be enabled by default (e.g., after a device reset), but can be changed or updated when the user's age is verified. Vaporizers 100,200 connected to an app where the user has been age-verified may be removed from the youth prevention device program (due to certain device limits, which are restricted by the number of devices that can be associated with a user account). Youth prevention ad shutdown mode may include strong security to prevent third-party hacking or disabling of youth prevention features.

[0178] Vaporizers 100,200 can be configured to allow the youth prevention device function to be restarted when a user unlinks vaporizers 100,200 from their age-verified account. Vaporizers 100,200 can be configured so that security protocols to prevent hacking are not disabled. In this way, the youth prevention function can only be disabled by shared secret challenges or other security / authentication means.

[0179] Vaporizers 100,200 can be configured to minimize the battery impact of the YPD function by providing low-power advertisements for detection by the Youth Prevention Beacon device. By default, vaporizers 100,200 can be configured to broadcast advertisements containing specific vaporizer information, manufacturer information, and / or user information for reception by the Youth Prevention Beacon. The Youth Prevention Beacon can be configured to monitor and record the broadcast advertisements so that administrators can identify underage users and provide counseling services.

[0180] The vaporizer can be configured to release the device from the user's associated account and perform a factory reset, including activating the YPD function, if the user misplaces a previously authenticated (and therefore no longer owns) vaporizer 100,200, or otherwise wishes to deauthenticate the vaporizer 100,200. The YPD function can be optionally disabled by a beacon depending on whether the user relinks the device to a different account. If a lost (unlinked) device is re-paired with a user app with age verification, the device may be factory reset and the YPD function may be re-activated, unless the device is locked.

[0181] In some embodiments, vaporizers 100,200 can be configured to connect to hardware beacons 705 and application beacons 805 described herein for authentication. For example, a user device may be prompted when vaporizers 100,200 are within communication range of the hardware beacons and / or application beacons. In some embodiments, the hardware and / or application beacons may be implemented in high-risk areas related to minors or misuse (e.g., schools, playgrounds, youth centers). In other embodiments, authentication may include proximity detection based on location information. For example, a user device and / or vaporizers 100,200 may receive GPS information or other location information indicating that vaporizers 100,200 and / or the user are within a proximity threshold of a given location (e.g., a school, playground, youth center). When vaporizers 100,200 are within the proximity threshold, vaporizers 100,200 may be locked, or the user device may be configured to lock vaporizers 100,200. In some embodiments, the user may be able to re-authenticate in order to unlock the vaporizers 100,200 within a proximity threshold. In other embodiments, the user may be restricted from unlocking or operating the vaporizers 100,200 within a proximity threshold.

[0182] In addition to locking vaporizers 100,200, the YPD and / or app can be configured to receive input from users reporting that vaporizers 100,200 have been lost, stolen, used by minors, and / or similar. Users can also report retailers suspected of selling to minors, locations suspected of use by minors, and / or similar. Users can provide any other relevant information in the user interface fields, such as counterfeit goods, locations, retailers, serial numbers, pod / cartridge IDs, personal information, and / or similar. Figures 14A–14F show exemplary user interface screen views that may appear in the app installed on a communication device. The user interface screen views in Figures 14A–14F relate to the reporting function that can be used on mobile devices that do not require pairing with a vaporizer. While these screen views are shaped and sized to match the dimensions of mobile devices such as smartphones, please understand that the user interface functions shown can also be implemented on any computing device, such as a tablet, desktop, or laptop.

[0183] Figures 14A and 14B show a screen view in which a person can report a vaporizer (referred to as a “device” in the view, being used by an unauthorized user, e.g., a minor). This view includes data entry options (in this case, any type of input, including optional free text input as well as pull-down or scroll menus) for the person to report their title or other identifying information, and allows for the input of a serial number. When this feature is used in a school setting (for example, if the feature is used to prohibit the use of vaporizers by underage users in a school), the title could be “School Administrator,” “Teacher,” or “Counselor,” etc. This view also includes fields for entering identifying information about the school and a “Submit” user interface element that allows the entered data to be sent to a server for analysis, aggregation, etc. This view may also include user interface elements to provide the user with guidance on how to find the device serial number and instructions to send to the device about locations that can be analyzed to determine its origin.

[0184] Figures 14C and 14D show a screen view with an invalid serial number entered. The user interface could then prompt the user to reconfirm the serial number, and if it is confirmed to be correct for the seized vaporizer, the user may be prompted to report it as a counterfeit vaporizer. This could trigger other steps. If the device is identified as counterfeit, the screen view in Figure 14E could prompt the user to enter any further available information, such as the place and date of purchase, and could also add a prompt asking the user to send the device to the top manufacturer or some other location for analysis and investigation. Figure 14F is an example of a “thank you” screen view.

[0185] Such reported information can be combined, aggregated, and analyzed to track and determine where misuse and / or undesirable use of vaporizers is occurring and which individuals and / or entities are involved. For example, after receiving a threshold number of reports associated with a given retailer or location, the vaporizer system may be configured to disable pods sold by that retailer for a given duration, send a warning to that retailer, lock / disable one or more vaporizers 100,200, and / or take any other corrective action. In some embodiments, disabling and data aggregation may be performed by one or more servers communicating with an app, a user device, and / or the vaporizers 100,200.

[0186] The vaporizer system can also combine reported data with information from individual vaporizers across the population, user and user profiles, usage profiles, user accounts, social media accounts, websites, crime reports, and / or similar information. This combined information can be presented on a dashboard or other user interface on user devices and / or apps. The dashboard is accessible to administrators, parents, police officers, and security personnel to monitor underage use, misuse, counterfeit products, and / or similar activities. For example, the vaporizer system can extract information from schools reporting underage use of vaporizers. The system can then correlate this information with information from social media (tweets, Facebook posts, hashtags, etc.) that associate underage use (e.g., social media accounts mentioning vaporizers, pod flavors, usage, locations, retailers, and / or similar activities). This combined data can be further analyzed to discover trends, patterns, and / or indicators of underage use. By tracking and tracing underage youth to the source, schools, parents, retailers, manufacturers, and / or similar entities may take action, initiate programs, lock vaporizers 100, 200, and / or similar actions to prevent use by minors.

[0187] Retailers may also have access to a dashboard that displays reports of minor use related to products sold by the retailer and / or its affiliates (e.g., serial numbers, distributors, or employees). This dashboard may include a map or graphic showing where the reports occurred, the data source for the reports, the number of reports, the time of the reports, the reputation of the data sources, other reports submitted by users or data sources, social media posts, comments associated with the reports, and / or similar information. Figures 15A–15E and 16A–16H (described below) show exemplary user interfaces for tracking reports and other data displaying minor use, retailers, locations, comments, investigations, preventive actions, lock vaporizers 100, 200, and / or similar information.

[0188] Figures 15A–16H show exemplary screen views that can be displayed on any computing device to visually represent data results based on data reported through the approaches described herein and other approaches. It should be understood that these screen views can be displayed on any type of computing device.

[0189] The screen view in Figure 15A shows a map diagram including school markings with various overlay options that allow the user to select the data types displayed on the map in relation to one or more locations. Overlays can include heatmap-type views showing different occurrence frequencies determined based on collected data. Data sources for collection can include (without limitation) school reports (e.g., those that can be entered via the screen view discussed above), retailer data (e.g., sales figures at a given location, tracking information on the origin of seized vaporizers), social media data (e.g., data on the estimated age and demographics of social media users discussing their use of vaporizers and / or their estimated locations), secret shopper data (e.g., data based on illicit or poorly certified sales to undercover agents attempting to purchase vaporizers from retail locations), regulatory reports (e.g., from the FDA, etc.), etc. The screen view can also include a data insights subview that can display information about recently added data and trends, etc. Clicking on a given school location allows drill-down based on a specific data type. This type of screen view can be used to develop strategies to prevent underage users from using vaporizers, for example, by easily displaying geographical correlations between school seizures, social media, and illegal sales activities.

[0190] The screen view in Figure 15B shows an example of a news feed regarding a given school mention in relation to the use of vaporizers and / or such devices by minors. The screen view in Figure 15C shows an overview of seized device reports for a selected school location. The screen view in Figure 15D shows a map with a heatmap but without other data, and the screen view in Figure 15E shows a map with highlighted social media information.

[0191] Figures 16A–16H show screen views illustrating exemplary features of data-driven functionality related to the use of data as discussed above when tracking the use and / or sale of illegal vaporizers. The data source control box allows users to view data from various sources as location-based overlays on a map. In Figure 16A, a hypothetical retail store is highlighted with social media mentions overlaid. Figure 16B shows an example of additional data insights related to this hypothetical retail store, along with statistics (e.g., six confirmed devices sold and seized here). Figure 16C shows a map view without data overlays, Figure 16D shows options to drill down into additional retailer reports, and Figure 16E shows an example of data from such a report, including details of seized devices. Figures 16F–16H show social media data along with estimated locations so that correlations with a given retail store and other data sources can be inferred.

[0192] In addition to the data sources indicated above that can be used with existing vaporizers that may not have connectivity, other data sources provided by such connected vaporizers can further enhance the capabilities of this subject. For example, geofencing can be set up around school locations and other locations where the use of vaporizers by minors is considered problematic. Vaporizers with connectivity can be detected when they are in such areas to enable mapping of potential illegal use hotspots. Another example is providing teachers and other school staff with apps that can run on mobile devices. Such apps would allow mobile devices to become mobile detectors for vaporizers near them. Collecting serial number data or other data from such vaporizers would allow for better tracking of where vaporizers being used by teenagers and other minor users are occurring.

[0193] Figure 8A shows a communication exchange diagram 800 between vaporizers 100A, 200A, 100B, 200B, 100C, and 200C and user devices 805A and 805B. As shown in Figure 8A, user devices 805A and 805B can be configured as application beacons having communication ranges 825A and 825B, respectively. Furthermore, as shown in the figure, vaporizers 100A and 200A are located within communication range 825A, and vaporizers 100B, 200B, 100C, and 200C are located within communication range 825B.

[0194] In some embodiments, a user device 805A running an application beacon can forward a broadcast message to disable any vaporizer in 825A. For example, vaporizers 100A, 200A can receive a broadcast message from user device 805A (e.g., via radio circuits 117, 217), and controllers 115, 215 can disable one or more components of vaporizers 100A, 200A to lock the device. In response to the lock, vaporizers 100A, 200A can notify the user of vaporizer 100A, 200A that the device is locked. In some embodiments, vaporizers 100A, 200A utilize an output side 115, 215 (e.g., light, tactile cue, sound, etc.) to indicate that vaporizers 100A, 200A are locked. In other embodiments, vaporizers 100A, 200A can communicate to a vaporizer application that the device is locked, and this vaporizer application can display a notification to the user that the device is locked. This notification may include text, audio, graphic images, etc., on the user's computing device (e.g., a smartphone). In some embodiments, a user device 805A can transmit the notification to vaporizers 100A, 200A and / or the vaporizer application.

[0195] In response to a lock and / or notification, the vaporizer 100A,200A may receive information associated with the user of the vaporizer 100A,200A. In some embodiments, the user may enter age / identification information on the vaporizer 100A,200A, the vaporizer application, and / or the website associated with the vaporizer 100A,200A. Upon receiving this information, the vaporizer 100A,200A, the vaporizer application, and / or the website associated with the vaporizer 100A,200A may determine the user's age. In some embodiments, this determination may include transferring the received user information to a third-party server for analysis and receiving the determined user age. In other embodiments, the processor of the vaporizer 100A,200A, the vaporizer application, and / or the website associated with the vaporizer 100A,200A may be configured to determine the user's age based on the received information. The determined age can be compared to an age threshold (e.g., legal age limit) to determine whether the user is permitted to use vaporizer 100A, 200A. If the age threshold is met, vaporizer 100A, 200A can be unlocked for use. In some embodiments, the vaporizer application and / or the website associated with vaporizer 100A, 200A can transmit the comparison results and / or a display indicating that the user meets the threshold to vaporizer 100A, 200A. Controllers 105, 205 can then unlock vaporizer 100A, 200A to activate its operation.

[0196] In some embodiments, application beacons on user devices 805A and 805B can be made available to a designated authenticated administrator (e.g., a teacher, principal, etc.). Additionally, the application beacons can optionally be configured to function only within a designated geographical location (e.g., a school, youth center, playground, etc.). In some embodiments, the locations where application beacons can function can be controlled by authorities (e.g., police, school officials, regulatory authorities, vaporizer manufacturers, etc.) and beneficially adapted to areas where demographic changes or increased risks of underage use are determined. In some embodiments, application beacons can be aggregated or pooled together to form a pooled range or network communication range 825 or restricted area for vaporizer use. In some embodiments, user devices 805A and 805B can also share information about vaporizers 100A, 200A, 100B, 200B, 100C, and 200C within the respective communication ranges 825A and 825B of the application beacons. The dynamic use of application beacons also allows for monitoring or controlling more locations by using application beacons rather than installing hardware beacons at each location.

[0197] Similar to the hardware beacon 705, in some embodiments, the application beacons of user devices 805A and 805B may also be configured to track and / or report vaporizers within the communication ranges 825A and 825B. For example, an application communicating with user devices 805A and 805B may be configured to display a list or graphic representation of vaporizers within the communication ranges 825A and / or 825B. This tracking allows the administrator of the application or entity (e.g., a school or teacher) to monitor which vaporizers are located within the area and whether their use is permitted within that area. For example, a school principal, teacher, or administrator may monitor vaporizers within the communication range of one or more application beacons to determine whether vaporizers associated with students of the school have been used or activated within the communication range. In some embodiments, the application may allow authorized users of the application beacon to report unwanted or unauthorized vaporizer use to authorities and / or manufacturers. This tutelage or reporting feature can enable parents, teachers, and authorities to improve prevention of unintended use by alerting communities of unwanted or illegal use.

[0198] In some embodiments, the user device 805 can be configured to unlock vaporizers 100,200 within the communication range 825. For example, vaporizers 100,200 can be configured to lock outside the communication range 825, and communication from the user device 805 can be configured to unlock vaporizers 100,200. Such examples can be used as designated "smoking areas" in areas where the use of vaporizers is generally prohibited (e.g., schools, airports, etc.).

[0199] Figure 8B shows a flowchart of an exemplary method 850 for locking a vaporizer, according to some exemplary embodiments. In some embodiments, this method 850 can be performed by vaporizers 100, 200, beacon 705, and / or user devices 805A and / or 805B.

[0200] In step 852, vaporizers 100,200 can determine whether they are within the communication range of a second device. In some embodiments, this determination is based on vaporizers 100,200 receiving communications from a second device (e.g., beacon 705, user device 805A, and / or user device 805B) to lock or disable vaporizers 100,200. In some embodiments, this communications may include beacon 705, user devices 805A and / or user device 805B forwarded in response to beacon 705, and broadcast messages from user devices 805A and / or user device 805B that have detected that vaporizers 100,200 are within the communication range 725 of beacon 705 and / or within the communication range 825A or 825B. In other embodiments, this communications may be forwarded in response to beacon 705 receiving communications from vaporizers 100,200 within the communication range 725. Similarly, this communication can be forwarded depending on user devices 805A and / or 805B that receive communications from vaporizers 100,200 within communication range 825A and / or 825B. Additionally, a vaporizer application on a smartphone associated with vaporizers 100,200 can also receive communications from beacon 705, user device 805A, and / or user device 805B.

[0201] In step 854, the vaporizers 100,200 can be locked to disable their operation in response to a determination that the vaporizers 100,200 are within the communication range of a second device (e.g., beacon 705, user device 805A, and / or user device 805B). For example, wireless circuits 107,207 can receive communications, and controllers 105,205 can disable one or more components of the vaporizers 100,200 to lock / disable their operation. In some embodiments, a vaporizer application on a smartphone can lock the vaporizers 100,200 in response to communications. For example, the vaporizer application can forward communications to the vaporizers 100,200 in response to receiving communications from beacon 705, user device 805A, and / or user device 805B. The communication to vaporizers 100 and 200 may be configured to disable the operation of vaporizers 100 and 200.

[0202] In step 856, the vaporizers 100,200 can notify the user of the vaporizers 100,200 that the device is locked. In some embodiments, the output sides 115,215 can provide an indication that the vaporizers 100,200 are locked. For example, the output sides 115,215 can display a red light, vibration, or icon indicating that the device is locked. In some embodiments, the vaporizers 100,200 can communicate with a vaporizer application to notify the user that the vaporizers 100,200 are locked. For example, the vaporizers 100,200 can communicate with a vaporizer application that can provide an indication on the display of a smartphone or computing device that the device is locked. In some embodiments, this indication may include text, audio, graphics, haptic cues, etc., to indicate that the vaporizers 100,200 are locked.

[0203] In step 858, the vaporizers 100, 200, the vaporizer application, and / or the webpage may receive information associated with the user of the vaporizer. In some embodiments, the vaporizers 100, 200, the vaporizer application, and / or the webpage may prompt the user to enter information in response to notifying the user that the vaporizers 100, 200 are locked. For example, the user may enter identification and / or age information (e.g., date of birth, driver's license number, telephone number, biometric information, address, etc.) into the user interface of the vaporizers 100, 200, the vaporizer application, and / or the webpage. In some embodiments, the vaporizer application and / or the webpage may be configured to communicate the received information to the vaporizers 100, 200.

[0204] In block 860, the vaporizers 100, 200, the vaporizer application, and / or web pages can determine the user's age based on the information received. In some embodiments, this determination can be based on any authentication step / method described herein. For example, the vaporizers 100, 200, the vaporizer application, and / or web pages can transfer the received information to a third-party server to verify the user's identity and age. The third-party server can then respond to the vaporizers 100, 200, the vaporizer application, and / or web pages with the determined age. In another example, the vaporizers 100, 200 and / or vaporizer application may include an age verification module configured to compare and analyze the received information in order to determine the user's age. Additionally, the vaporizers 100, 200, the vaporizer application, and / or web pages may scan the user's identification document in order to determine the user's age.

[0205] In step 862, the vaporizers 100,200, the vaporizer application, and / or web page may unlock the vaporizers 100,200 to activate their operation based on the user's age meeting a threshold. For example, the age verification module of the vaporizers 100,200 and / or the vaporizer application are configured to compare the user's determined age with a threshold (e.g., legal smoking age) to determine whether the threshold is met. In some embodiments, the vaporizer application and / or web page may forward communications to the vaporizers 100,200 to unlock the device depending on whether the threshold is met. In some embodiments, the beacon 705, user device 805A, and / or user device 805B may be configured to forward a second communication to the vaporizers 100,200 to unlock the device. For example, beacon 705, user device 805A, and / or user device 805B may receive a communication indicating that vaporizers 100,200 have completed the second authentication and are permitted to be used within communication ranges 725,825A, and / or 825B. The beacon 705, user device 805A, and / or user device 805B may then provide the second communication to vaporizers 100,200.

[0206] It may be desirable to re-authenticate the user after the first use of the vaporizer. In some embodiments, if the user runs out of cartridges and vaporizable material, they can purchase additional supplies from an online or in-store retailer. It may be beneficial to provide a third authentication to help ensure that such vaporizer supplies and cartridges are being used by the intended consumer and not by an unintended user (e.g., a minor child). In some embodiments, this third authentication may be the same as or similar to the first authentication when the user completes the initial purchase of the vaporizer. In some embodiments, the processor 610 may perform the third authentication and / or lock in response to input received from the sensor module 660 or other components of the computing device 600.

[0207] In some cases, users may purchase vaporizer supplies and / or cartridges from online retailers. This purchase may include a third authentication to verify the purchaser's age. For example, to purchase vaporizer supplies and / or cartridges online, a user may be required to enter identification information, including their age. The retailer may verify that the entered information has correct access to databases containing user identification information (e.g., social security bureau, land transport bureau, tax records, etc.). The retailer may also contract with a third-party organization that has access to such information to verify that the entered consumer information is correct and that the user meets any age thresholds. Additionally, the retailer may have access to a user profile created during the first authentication associated with the user. The third authentication may include verification 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.

[0208] A third authentication process may involve a multi-step authentication process in which, after the user enters their information (e.g., contact information), the retailer, manufacturer, etc., sends the user a code (e.g., via an application, text message, email message, etc.) to enter before the purchase can be completed. If the user enters the correct code, the sale is authenticated; otherwise, the sales transaction may be terminated. In some embodiments, the information used by the user may be stored for the creation of a user profile if one was not created during the first or second authentication. This user profile may be stored in a vaporizer, application, server, or other computing device.

[0209] In some embodiments, a user may purchase vaporizer supplies and / or cartridges through a vaporizer application. This application may store the user's profile in a database that verifies the user's age. If a user profile has not been created, the application may prompt the user to enter information necessary to verify the user's age. In some embodiments, the application may transmit such information to a third-party service provider to verify the user's age and / or identity. In some embodiments, the application may require a third authentication to enable the purchase of vaporizer supplies and / or cartridges. This third authentication may include verification that a fingerprint matches a fingerprint stored in the user profile (e.g., entered during the first and / or second authentication). This third authentication may also include a single or multi-step authentication process. For example, the application may send a message to an email address, phone number, or other contact address. The message may include a code that the user must enter into the application to complete the purchase. The third authentication may also include any other biometric authentication (e.g., voice authentication, facial recognition, etc.).

[0210] In other embodiments, a user may purchase vaporizer supplies and / or cartridges at a retail store within the store. The retailer may perform a third authentication to verify the user's age and / or identity in order 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 user's age and / or identity. The retailer may also swipe or scan a barcode, QR code, or other encrypted code on the identification document to read and verify the consumer's age and / or identification information. In some embodiments, the retailer may manually enter or scan the age / identity into a computer application that verifies the consumer's identity and / or age. For example, the retailer may have a tablet, laptop, desktop, or other computing device running an application associated with the vaporizer. The user or retailer may register the user through the application and provide the application with their identification information and information related to their age. The application can then perform a third authentication to verify the consumer's age and identity. In some embodiments, the application may communicate with a vaporizer application database or a third-party system to complete the third authentication. This third authentication may include verification 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.

[0211] In some embodiments, the third authentication may include authentication that connects to hardware beacons and application beacons as described herein. For example, the third authentication may be prompted when the vaporizer is within communication range of the hardware beacon and / or application beacon. In some embodiments, the hardware and / or application beacons may be implemented at a retail store selling vaporizer supplies and / or cartridges.

[0212] In addition to or as an alternative to the authentication schemes described herein, it may be desirable to periodically check or re-certify that vaporizer users are authorized to use the vaporizer device and / or supplies. It may also be desirable to ensure that this re-certification is not excessively cumbersome or time-consuming from the user's experience. Therefore, it may be beneficial to incorporate a fourth authentication that verifies age and / or identity and unlocks the vaporizer for use. In some embodiments, the processor 610 may perform the fourth authentication and / or lock in response to input received from the sensor module 660 or other components of the computing device 600.

[0213] In some embodiments, the application and / or vaporizer may communicate with a dongle that performs periodic re-identification and / or authentication. In some embodiments, the vaporizer and / or application may require the user to enter a code to unlock the vaporizer. For example, this code may be pre-programmed as part of the user and / or device profile. Additionally, the code may be randomly generated and sent to a communication address or number associated with the user for the user entering it through the vaporizer and / or application. This code may include any combination of numbers, letters, gestures, sounds, voices, biometric features, etc. For example, the code may include entering the user's fingerprint on a fingerprint scanner on the vaporizer or computing device. Alternatively, the code may include having the user scan their iris using an iris scanner on the vaporizer or computing device.

[0214] In some embodiments, a computing device running a vaporizer application can be used to provide a fourth authentication. For example, a vaporizer can remain locked unless the vaporizer device is within a predetermined proximity range of the computing device running the application. In some embodiments, the application can run on a consumer's smartphone, and the vaporizer remains locked until the smartphone enters a proximity threshold with the vaporizer. In some embodiments, the vaporizer and / or computing device can detect proximity via Bluetooth®, Near Field Communication (NFC), Wi-Fi, ultrasound, ZigBee, RFID, cellular communication, or any other wireless communication.

[0215] In some embodiments, the fourth authentication may include authentication that connects to hardware beacons and application beacons described herein. For example, the fourth authentication may be prompted when the vaporizer is within communication range of a hardware beacon and / or application beacon. In some embodiments, the hardware and / or application beacons may be implemented in high-risk areas for minors or misuse (e.g., schools, playgrounds, youth centers, etc.). In other embodiments, the fourth authentication may include proximity detection based on location information. For example, the application and / or vaporizer may receive GPS information or other location information indicating that the vaporizer and / or user is within a proximity threshold of a given location (e.g., a school, playground, youth center, etc.). If the vaporizer is within the proximity threshold, the vaporizer may be locked or the application may lock the vaporizer. In some embodiments, the user may be re-authenticated to unlock the vaporizer within the proximity threshold. In other embodiments, the user may be restricted from unlocking or operating the vaporizer within the proximity threshold.

[0216] Any of the certification technologies and mechanisms described may be used individually or in combination to provide protection for vaporizers and / or vaporizer accessories from unintended or unwanted users.

[0217] As discussed elsewhere in this specification, any device described herein (e.g., vaporizer and / or related applications) may include location services (GPS).

[0218] For example, a user who purchases vaporizer cartridges directly from a supplier can use an app to know exactly how many cartridges they have and how many are left. Retailers can use this information to offer users more automated orders when they are running low.

[0219] In any device described herein, the app and / or vaporizer may include or communicate with GPS to determine the location of the vaporizer. Location information may be used to notify the user of the nearest retailer where more cartridges can be purchased, to use location services for supply, to order via smartphone (e.g., in a usage tracking program combined with automatic refilling), and / or to inform the user of local laws applicable to the use of e-cigarettes and cannabis.

[0220] Location information can also be used to disable vaporizers located or determined to be located within one or more areas where vaporizer use is not permitted. For example, a specific area or zone may be established, and if a vaporizer enters such an area or within a predetermined range of such an area, the vaporizer may be automatically disabled or disabled after an alert is given. Such areas may include, for example, defined boundaries around a school or defined boundaries within a specific location where vaporizer use is not permitted (such as a store). Additionally, a specific location where vaporizer use is not permitted may be defined by one or more individuals (e.g., a private home). To establish an area / zone / location, physical beacon devices (e.g., beacons 705 and / or 805) may be installed to identify the area / zone / location. If a vaporizer is within range of these beacons, the vaporizer will not be turned on or will be turned off. Alternatively, geofencing can be used to establish an area / zone / location where vaporizer use is not permitted. By pairing the vaporizer with the user's phone or mobile device, or by utilizing the vaporizer's location services, the vaporizer can be disabled when it is in a arbitrarily defined geofenced area / zone / location.

[0221] Examples of application software having many of the features described herein for use with one or more vaporizers are illustrated with reference to Figures 10A to 12J. Each of the user interface (UI) screens described herein in Figures 10A to 12J can be generated by the user interface 650 of user devices 305, 805 and / or computing device 600. For example, user device 305 may include memory 620 that stores instructions for executing a vaporizer application running on user device 305. Processor 610 can execute these instructions and generate exemplary UI using display 630 and / or user interface 650. This exemplary UI can also be generated based on user input received via display 630 and / or user interface 650. This exemplary UI can also be generated based on communication with vaporizers 100, 200, remote server 307, beacon 705, other user devices 305, 805 and / or other devices. This communication can be received using the network interface 640 and / or antenna 690 of the user device 305, vaporizers 100, 200, and / or any other device.

[0222] As described herein, the embodiments covered hereby include various uses of a vaporizer system including a vaporizer and a device that communicates with the vaporizer. Figure 9 shows a flowchart of a method 900 for authenticating a user of a vaporizer, according to some exemplary embodiments. In various embodiments, method 900 (or at least a part thereof) can be performed by one or more of the vaporizer 100, vaporizer 200, user access device 305, remote server 307, computing device 800, other related devices, and / or parts thereof.

[0223] Method 900 can be initiated by operation step 910, in which the device 900 can lock the vaporizer to deactivate its operation, for example. Method 900 can proceed to operation step 920, in which the device 900 can receive information associated with the user of the vaporizer, for example. In some embodiments, this information may include age and / or identification information (e.g., date of birth, address, social security number, license number, etc.). Method 900 can proceed to operation step 930, in which the device 900 can determine the age of the user of the vaporizer, for example. In some embodiments, the vaporizer can determine the age or receive an age determination from a server and / or application. Method 900 can proceed to operation step 940, in which the device 900 can unlock the vaporizer to activate its operation based on the determined age of a user who meets a threshold (e.g., legal age).

[0224] Figures 10A–10E show user interfaces (UIs) for applications (apps) usable with the vaporizers described herein, including the app itself, and including initial or subsequent age / identity verification protocols for accessing the vaporizer and / or associated vaporizer data analysis, data collection, and data processing systems. Figure 10A shows a user interface for an app configured to allow a user to enter age / identity information into one or more fields of the UI, Figure 10B shows a user interface screen for an app that allows a user to scan the front or first side of an identification document (e.g., a driver's license), Figure 10C shows a user interface screen for an app that allows a user to scan the back or second side of an identification document, Figure 10D shows a user interface screen for an app that indicates the app is verifying the entered / scanned user information, and Figure 10E shows a user interface screen for an app that indicates the user has been verified / authenticated to use the vaporizer.

[0225] Figures 11A and 11B show UI screens that can be used as part of an app interface for vaporizer discovery, pinching, and / or status checking. In Figure 11A, the UI includes a name associated with the vaporizer, a button to find the vaporizer, and a button to pinch the vaporizer. Figure 11B shows the UI screen from Figure 11A with an indicator that the vaporizer is locked.

[0226] Figures 12A–12J show UI screens available as part of an app interface (e.g., connected to a smartphone) usable with the vaporizer described herein, including an initial or subsequent beacon protocol for accessing vaporizer and / or associated vaporizer data analysis, data collection, and data processing systems, and including the app itself within the beacon's communication range. Figure 12A shows a user interface for an app configured to allow a user to create an account or log in to a user's account. Figure 12B shows a user interface screen for an app that allows a user to enter information (e.g., email address, password, etc.) into one or more fields for creating an account. Figure 12C shows a user interface screen for an app with exemplary input to UI fields for creating an account. Figure 12D shows a UI screen for an app that allows a user to send an invitation to another user for that other user to create an account or skip this process. Figure 12E shows a user interface screen for an app indicating that the application is searching for a beacon within the communication range of the app and / or the beacon. Figure 12F shows a user interface screen for the app indicating that the application has detected a beacon within the communication range of the app and / or the beacon, and includes a field for naming the beacon. Figure 12G shows a user interface screen for the app indicating that the application has found a beacon named "Women's Bathroom: Courtyard" within the communication range of the app and / or the beacon. Figure 12H shows a user interface screen for the app indicating that it includes a map showing the location of the beacons, and also includes a list of beacons shown with their names and the status of the listed beacons. Figure 12I shows a user interface screen for the app indicating that one of the beacons in the beacon list has been selected, and provides the user with the option to investigate or clear the vaporizer detected by the selected beacon (e.g., Women's Bathroom: Courtyard).Figure 12J shows the app's user interface screen, which displays the options the user can choose after selecting to conduct a survey in Figure 12I. These options include assigning the survey to individuals (e.g., me, Jane Smith, Sharon Kim, Dave Rodriguez).

[0227] Any of the apps described herein can be adapted for use involving the detection (including automatic detection) of cartridges and / or vaporizable materials. The app can provide commands for detection / identification, or the app's operation can be automatically adjusted / customized based on detected cartridges, beacons, second devices, and / or similar items.

[0228] Age verification Figures 17–31 show exemplary user interfaces that may appear in an app installed on a communication device that communicates with the vaporizer (for example, as part of an "app" or other software on the user's mobile device). The user interfaces in Figures 17–31 relate to an age verification function that may be beneficial in providing data to prevent misuse and / or use, purchase, etc., of the vaporizer, as well as specific controls over the vaporizer. In one embodiment, the vaporizer may be configured to start functioning only after the age verification process has been successfully completed via the user interface. In another embodiment, the vaporizer may be configured to be deactivated if the age verification process has not been completed within a threshold period after purchase.

[0229] The app screen view in Figure 17 or a similar approach can be used to prompt the vaporizer user to complete the device's age verification feature. For example, the user may be prompted to enter the age verification process by consenting to be age-verified. Alternatively, the vaporizer can be configured to disable the feature depending on the user's "opt-out" of the age verification process and / or whether the user is below a threshold age. The threshold age may be based on consumer protection laws and / or other considerations in the user's geographical area.

[0230] The screen views in Figures 18–21 show screen views that may be presented to a user after they select and agree to the age verification feature. On this screen, the user may be prompted to enter personal user information (e.g., the user's name and phone number). In some embodiments, other user information such as a social security number, driver's license, identification card, credit history, facial recognition, and / or similar may be requested. Depending on the user's entry of user information, the age verification feature may be configured to verify the user's age using one or more authentication methods. For example, two-factor authentication may be used to verify the user's name and phone number (e.g., receiving a code via text message). The user may then receive an authentication message containing a unique or "one-time" numerical and / or alphanumeric security code, as shown in Figure 22.

[0231] As shown in Figures 23 and 24, the user may be prompted to enter a received security code. Once the user enters the security code, the app screen view in Figure 17 or a similar approach can be used to communicate that the user information has been verified. User information can be verified using one or more of the following: 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., "less than 1 minute," and / or other durations). Depending on whether the user information has been successfully verified, the user may be notified via the app screen view in Figure 26 or a similar approach. However, if the user information cannot be verified, the user may be notified via the app screen view in Figure 27 or a similar approach and may be asked to provide additional user information to proceed with the age verification process.

[0232] Depending on whether an unverified user proceeds with the verification process, the screen views in Figures 28–31 or similar approaches can be used to prompt the user to provide user information certificates such as a valid driver's license, state identification card, passport, social security number, and / or other information. The app can be configured to access one or more features of the user's device, such as the camera function, to capture, scan, or otherwise document the user's information. In some embodiments, facial recognition can be used to verify and authenticate the photoidentification information provided by the user. Depending on the submission of user information certificates and / or images, the app screen view in Figure 31 or similar approaches can be used to communicate that the user information has been verified. In some embodiments, an estimated duration of verification and / or a status bar can be displayed. Depending on the success of user information verification, the user can be notified via the app screen view in Figure 26 or similar approaches.

[0233] Once the age verification process is complete, the vaporizer can be configured to activate by prompting one or more user actions and / or other user inputs, such as shaking the vaporizer, via the app screen view shown in Figure 32 or a similar approach. Confirmation of vaporizer activation can be provided as shown in Figure 33.

[0234] In some embodiments of this subject matter, a screen view as shown in Figure 34 may be provided when a user leaves and returns to the app. A new user can initiate an age verification process, or a returning verified user can “log in” to their associated user account. A logged-in and verified user can access additional app features, including a pairing process from the vaporizer to a mobile device or other user device, as shown in Figure 35. A quick start guide and / or other onboarding instructions (e.g., a user manual and / or a usage tutorial configured to familiarize the user with the vaporizer) may be provided from the app to the logged-in verified user. Additional coaching and habit management programs may also be provided, as further described herein.

[0235] In some embodiments, after activation, the device may periodically re-verify in the background with little to no action requested by the user. For example, the vaporizer may periodically (e.g., once a week, every two weeks, and / or at other intervals) request a connection with the user device, as shown in Figure 36. In some embodiments, the age verification process may only be required in response to the insertion of a specific cartridge type (e.g., a flavored cartridge) into the vaporizer.

[0236] Figures 37 to 39 illustrate one or more age confirmation methods to ensure the use of an appropriate vaporizer for the age. As shown in Figure 37, the initial device purchase made in the store requires the following steps for age confirmation and / or device activation, namely, (1) Purchasing a non-activated device in the store, (2) Unpacking and downloading the mobile app, (3) Conducting an age check against public records, (4) Activating the vaporizer by pairing it with the user device via Bluetooth and / or other connections, and / or (5) Automatically re-verifying the device, One or more of which may be required. For subsequent device purchases made in the store, one or more of the following steps, namely, (1) Purchasing a non-activated device in the store, (2) Activating the vaporizer by pairing it with the user device via Bluetooth and / or other connections, and / or (3) Automatically re-verifying the device, May be required. The initial device purchase made online requires one or more of the following steps for age confirmation and / or device activation, namely, (1) Creating an online account, performing an age check, and making an online purchase, (2) Receiving the non-activated device, unpacking it, and downloading the mobile app, (3) Logging in to the app using the online account qualification information, (4) Activating the vaporizer by pairing it with the user device via Bluetooth and / or other connections, and / or (5) Automatically re-verifying the device, May be required.

[0237] As shown in FIG. 38A, another embodiment of the age confirmation method for ensuring the use of an age-appropriate vaporizer includes the following steps for age confirmation and / or unlocking the vaporizer, namely, (1) The step of unpacking the vaporizer and / or cartridge, (2) The step of downloading the app, (3) The step of confirming age, (4) The step of unlocking the vaporizer by pairing with a user device via Bluetooth and / or other connections, and / or (5) The step of automatically re-verifying the device, One or more of which may be included. In yet another embodiment of the age confirmation method for ensuring the use of an age-appropriate vaporizer, as shown in FIG. 38B, the following steps for age confirmation and / or unlocking the vaporizer include, namely, (1) The step of unpacking the vaporizer and / or cartridge, (2) The step of reading the provided youth prevention information, (3) The step of downloading the app, (4) The step of confirming age against public records, (5) The step of activating the vaporizer by pairing with a user device via Bluetooth and / or other connections, One or more of which may be included.

[0238] As shown in FIG. 39, another embodiment of the age confirmation method for ensuring the use of an age-appropriate vaporizer includes the following steps for age confirmation via a user interface, namely, (1) The step of providing a welcome screen, (2) The step of providing onboarding information and prompting for age confirmation information, (3) The step of verifying user information by authentication, and / or (4a) The step of providing a notification of successful age confirmation, or (4b) A step of requesting additional age verification information, It may include one or more of the following.

[0239] After a user's age has been verified and the vaporizer associated with the user has been unlocked using one or more of the methods described herein, the user may be required to periodically re-authenticate themselves. This re-authentication may be required once a day, once a certain number of days, once a week, once a certain number of weeks, once a month, once a certain number of months, etc. (for example, based on firmware in the vaporizer). In some embodiments, the vaporizer may be required to re-authenticate every two weeks. This re-authentication may occur through the use of a user device running a specific application that can communicate with the vaporizer, as described herein. For example, this re-authentication may require the user to periodically electronically pair their vaporizer with the user device (for example, via Bluetooth) through the application. In some embodiments, the duration required for re-authentication may begin once the vaporizer detects that it is no longer paired with the user device, and may restart each time the vaporizer detects that it is paired with the user device, regardless of the most recent pairing and / or similar (for example, a restart based on a specific re-authentication procedure performed through the application).

[0240] In some embodiments, after a user has been age-verified 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 has been age-verified (e.g., user account information with a specific value for the “age-verified” field associated with the user account). In some embodiments, these credentials may be created as part of a registration process performed using an application running on the user device. In some embodiments, the user device may receive the credentials or a portion thereof from a server after the user's initial account setup and / or age verification. For example, if the user themselves verifies their age using a method other than a web browser, a dedicated kiosk, two-factor authentication (e.g., via email, SMS, and / or similar), and / or an application running on the user device, a server configured to communicate with the user device may transfer the credentials or a portion thereof to the user device. In some embodiments, the user may only be able to (re)authenticate themselves for the purpose of unlocking the user device if the credentials stored on the user device indicate that the user has been age-verified. In some cases, devices purchased using an age-verified user account may be activated at the time of shipment, but may still be required to (re)authenticate within a certain period of time.

[0241] In some embodiments, users may be restricted from purchasing a certain number of vaporizers and / or cartridges for use with a vaporizer within a specific time period. For example, in some embodiments, users may be restricted from purchasing more than one, two, three, etc., devices within a month (e.g., based on a calendar month or last purchase of a vaporizer). In some embodiments, users may be restricted from purchasing more than 10, 15, or 20 sets of cartridges, etc. (e.g., with 2, 3, 4, 5, etc., cartridges per set) within a month (e.g., based on a calendar month or last purchase of a cartridge set). In some embodiments, a user's purchases may be tracked through more than one source. For example, a user's total purchases within a specific time period can be determined based on data received through user devices, web browsers, kiosks, retail stores (e.g., via POS), online retailers, servers configured to communicate with one or more of these, and / or similar. To track a user's total purchases, users may be required to use an age-verified user account for each purchase.

[0242] To prevent users from creating multiple user accounts, users may be limited to one account per set of unique credentials (e.g., unique information that identifies only one person). To determine whether a set of credentials is unique, the system may require users to provide a valid name, date of birth, place of origin, and the last four digits of their Social Security number (e.g., via a server). This information may be verifiable by a third party and / or cross-referenced with publicly available records to verify the user's age within that location / jurisdiction. If the user's public records do not match, or if the user does not wish to provide their Social Security number, the user may be required to upload or swipe a valid government-issued ID (via a card reader) for compliance review. In some embodiments, users may be required to verify themselves through multi-factor authentication. For example, to create a user account, a user may be required to provide a phone number and then provide a code sent to that phone number before proceeding. In some embodiments, this code may only be sent to the phone number if it is known that the phone number is associated with a person of legal age for the purchase of a vaporizer. In some cases, the SIM card associated with the phone number may be verified, and only if this SIM card is verified (e.g., if the SIM card is associated with the provided phone number) may the user be permitted to use the code sent to that phone number. Additionally or alternatively, the user may be required to upload or swipe a valid government-issued ID (via a card reader) and scan their face via a facial recognition interface (e.g., provided by running an application on the user's device used for account creation). To prevent one user from using multiple user accounts from different users, the user may be required to verify themselves each time they use their user account for a purchase, using electronic verification of ID (e.g., a driver's license), facial recognition, and / or similar methods.

[0243] In some embodiments, a kiosk or other device may be configured for device activation. For example, a kiosk may be configured to receive user input to verify the user's age in accordance with the methods described herein. Once the user's age has been verified, the kiosk may provide the user with a receipt having a code (e.g., a barcode, QR code, numbers, alphanumeric strings, and / or similar) for presentation to a store employee. The employee may scan or enter the code into a system indicating what the user can purchase before the store is authorized to sell vaporizers or cartridges to the user. In some embodiments, the kiosk may be connected (e.g., physically, electronically, and / or by communication) to a vending machine containing vaporizers and / or cartridges. Once the user's age has been verified and a purchase has been made, the vending machine may deliver the purchase to the user.

[0244] In some embodiments, a vaporizer stored in a vending machine may be deactivated and / or require authentication (e.g., via one or more of the device pairing methods described herein) before a user can use it. In some embodiments, the vaporizer may not be configured for wireless communication with a user device. Therefore, such a vaporizer may be prevented from being activated based on information stored on the device, such as a register (e.g., 1 bit) within the vaporizer. To activate the device, the user may be required to place the device on an interface that communicates with the kiosk. The kiosk may be configured to change the value of the register to unlock the device after the user's age has been verified and the vaporizer has been placed on the interface. In some embodiments, the interface may include a cradle and / or cable with an electronic interface that can communicate with the vaporizer through an interface built into the vaporizer (e.g., USB or other data communication interface such as one or more pins). Once the device is unlocked, a serial number or other unique identifier associated with the vaporizer, the activation date, the purchase date, and / or similar information may be associated with the user account for tracking purposes. Although a kiosk is used as an example, any device capable of communicating with the device without using wireless communication may be used.

[0245] In some embodiments, users may be permitted to purchase vaporizers and / or cartridges beyond the set limits, but the vaporizers and / or cartridges may be retained until the expiration of the current duration while the user is exceeding the set limits. For example, if a user is limited to purchasing more than two vaporizers per month, and the user attempts to purchase a third vaporizer within the same month (viewed in calendar month or deployment month based on the purchase of the first vaporizer), the vaporizer may be retained until the end of that month. Once the month has passed, the vaporizer will be released to the user (e.g., through automatic shipping). Additionally or alternatively, users may be limited to the number of activations per specified period (e.g., two activations per month). Activations may be tracked by a server configured to communicate with multiple devices configured for vaporizer activation (e.g., user devices running a dedicated application and / or similar). In an exemplary embodiment, if a user is limited to activating more than two vaporizers per month, and this user attempts to activate a third vaporizer within the same month (calendar month or deployment month based on the activation of the first vaporizer), the device configured for vaporizer activation may prevent the user from activating the device until the end of that month. The device may notify the user that they have exceeded their activation limit and / or provide the user with information indicating when they can activate a vaporizer. In cases where the user returns the device, additional activations within a certain period may be credited to the user's account.

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

[0247] In some embodiments, if 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, and / or similar information may be associated with the user account for tracking purposes. In cases where a user account is determined to be associated with inappropriate activation (e.g., providing a vaporizer to a minor, shipping a vaporizer to another jurisdiction), the user account may subsequently be blocked / prevented from making any further purchases or activations.

[0248] In some embodiments, the requirement to meet age verification requirements may be additionally or alternatively based on GPS information. For example, based on the determined GPS location, the user may be prompted to provide a specific document for age verification that is sufficient for identification based on the jurisdiction covering the GPS location, such as either a driver's license or a passport, or a passport only.

[0249] Another useful embodiment of the identification system could be purchase time and / or cartridge tracking information. The location and / or date the cartridge was first purchased, as well as vendor information, is useful from both legal and security and / or marketing perspectives. For example, if a cartridge is found to be in the possession of a minor, the purchase information of this cartridge can identify whether the vendor performed age verification at the time of purchase, or whether the cartridge was purchased by someone “of the age” and provided to a minor.

[0250] If a particular feature or element is referred to herein as being "above" another feature or element, that feature or element can be directly above the other feature or element, or intervening features and / or elements may be present. In contrast, when a particular feature or element is referred to as being "immediately above" another feature or element, no intervening features or elements are present. Also, when a particular feature or element is referred to as being "connected to", "attached to", or "coupled to" another feature or element, it will be understood that that feature or element can be directly connected, attached, or coupled to the other feature or element, or intervening features or elements may be present. In contrast, when a particular feature or element is referred to as being "directly connected to", "directly attached to", or "directly coupled to" another feature or element, no intervening features or elements are present.

[0251] Although described or illustrated with respect to a given example, the features and elements so described or illustrated can be applied to other embodiments of the subject matter. Also, it will be understood by those skilled in the art that a reference to a structure or feature being "adjacent" to another feature may sometimes have a portion that overlaps or is beneath the adjacent feature.

[0252] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. For example, the singular forms of indefinite and definite articles used herein are intended to include the plural forms as well, unless the context clearly dictates otherwise. Further, the terms "comprises" and / or "comprising", when used in this specification and the claims, specify the presence of the stated features, steps, acts, elements, and / or components, but do not preclude the presence or addition of one or more other features, steps, acts, elements, components, and / or groups thereof.

[0253] In this specification and in the claims, phrases such as “at least one of ~” or “one or more of ~” may appear following a conjunctive list of multiple elements or features. Similarly, the term “and / or” may appear in a list of two or more elements or features. Unless otherwise implicitly or explicitly negated by the context in which they are used, such phrases are intended to mean any of the enumerated elements or features individually, or any combination of any of the enumerated elements or features with any of the other enumerated 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 only,” “B only,” or “A and B together,” respectively. A similar interpretation applies to lists containing three or more items. 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, B, and C together.” The use of the term “based on” in this specification and in the claims is intended to mean “at least partially based,” so as to allow for features or elements that are not enumerated.

[0254] Spatially relative terms such as "below," "further down," "lower," "above," "higher," and similar terms may be used herein to facilitate descriptions of the relationship between one element or feature and another, as shown in the drawings. It will be understood that spatially relative terms are intended to encompass various orientations of the device in use or operation, in addition to the orientation depicted in the drawings. For example, if the device in the drawing were inverted, an element described as "below" or "directly below" another element or feature would then be oriented "above" the other element or feature. Thus, the exemplary term "below" may encompass both upward and downward orientations. The device may be oriented in a different orientation (rotated 90 degrees or in another orientation), and the spatially relative descriptors used herein may be interpreted accordingly. Similarly, terms such as "upstream," "downstream," "vertically," "horizontally," and similar terms are used herein for illustrative purposes only, unless otherwise specified.

[0255] In this specification, the terms “first” and “second” may be used to describe various features / elements (including steps), but these features / elements are not limited by these terms unless otherwise specified in the context. These terms may also be used to distinguish one feature / element from another. Thus, without departing from the teachings provided herein, the first feature / element described below may be referred to as the second feature / element, and similarly, the second feature / element described below may be referred to as the first feature / element.

[0256] Throughout this specification and the subsequent claims, unless otherwise required by context, the word “includes,” its third-person singular form “includes,” and its inflections such as the present participle “containing,” mean that various components can be used together in methods and things (e.g., articles and apparatus including devices and methods). For example, the term “containing” will be understood to mean the inclusion of any element or step mentioned, but not the exclusion of any other element or step.

[0257] Unless otherwise specified, all numbers used in this specification and in the claims, including those used in the examples, can be interpreted as if preceded by the words "approximately" or "nearly," even if not specifically noted as such. When describing size and / or location, these "approximately" or "nearly" phrases may be used to indicate that the stated value and / or location is within a reasonable expected range. For example, a number may have values ​​such as ±0.1% of the stated value (or range), ±1% of the stated value (or range), ±2% of the stated value (or range), ±5% of the stated value (or range), ±10% of the stated value (or range). Any numbers appended herein, unless otherwise specified in the context, should be understood to include a "approximately" or "nearly" nuance in their value. For example, if the value "10" is disclosed, it also means that it is disclosed in the sense of "about 10". Any numerical range given herein is intended to include all subranges contained therein. Furthermore, if a single value is disclosed, it will be understood, as a person skilled in the art would understand, that "less than or equal to that value," "greater than or equal to that value," and possible ranges between those values ​​are also disclosed. For example, if the value "X" is disclosed (where X is, for example, a single number), then "less than or equal to X" and "greater than or equal to X" are also disclosed. Furthermore, it will be understood throughout this application that data is provided in many different formats, and that this data represents start and end points and extends to ranges relating to any combination of these data points. For example, if one specific data point "10" and another specific data point "15" are disclosed, it will be understood that the values ​​greater than 10 and 15, 10 and 15 or greater, less than 10 and 15, 10 and 15 or less, and equal to 10 and 15 are also considered to be disclosed, as are the values ​​between 10 and 15. It will also be understood that each unit between two specific units is disclosed.For example, if 10 and 15 are disclosed, then 11, 12, 13, and 14 are also disclosed.

[0258] While various exemplary embodiments are described herein, any number of modifications can be made in various embodiments without departing from the teachings herein. For example, the order in which various method steps are performed may often be changed in alternative embodiments, and in yet another alternative embodiment, one or more method steps may be skipped entirely. Optional features of various device and system embodiments may be included in some embodiments and omitted in others. Therefore, the foregoing description is provided primarily for illustrative purposes and should not be construed as limiting the scope of the claims.

[0259] One or more embodiments or features of the subject matter described herein can be implemented in digital electronic circuits, integrated circuits, specially designed application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments or features may include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor. The at least one programmable processor may be coupled, for dedicated or general-purpose use, to receive data and instructions from a storage system, at least one input device, and at least one output device, and to transfer data and instructions to the storage system, at least one input device, and at least one output device. The programmable system or computing system may include clients and servers. Clients and servers are generally remote from each other and typically interact over a communication network. The client-server relationship is generated by computer programs that run on individual computers and have a client-server relationship with each other.

[0260] These computer programs (which may also be referred to as programs, software, software applications, applications, components, or code) contain machine instructions for a programmable processor and can be implemented in high-level procedural languages, object-oriented programming languages, functional programming languages, logic programming languages, and / or assembly / machine language. As used herein, the term “machine-readable medium” means any computer program product, apparatus and / or device, such as magnetic disks, optical disks, memory, and programmable logic devices (PLDs), which are used to supply machine instructions and / or data to a programmable processor and include machine-readable medium that receives machine instructions as machine-readable signals. The term “machine-readable signal” means any signal used to supply machine instructions and / or data to a programmable processor. Machine-readable medium can store such machine instructions non-temporarily, for example, in non-temporarily solid-state memory or magnetic hard disk drives or any equivalent storage medium. Alternatively or additionally, machine-readable medium can store such machine instructions in a temporary manner, for example, in a processor cache or other random-access memory associated with one or more physical processor cores.

[0261] To provide user interaction, one or more aspects or features of the subject matter described herein may be implemented on a computer having a display device, such as a cathode ray tube (CRT), liquid crystal display (LCD), or light-emitting diode (LED) monitor, for displaying information to the user, and a pointing device, such as a keyboard or a mouse or trackball, to which the user can provide input to the computer. Other types of devices may be used in the same way to provide user interaction. For example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback, and the input from the user may be received in any form, but is not limited to acoustic input, voice input, or tactile input. Other possible input devices include, but are not limited to, touchscreens, other contact-sensitive devices such as single-point or multi-point resistive or capacitive trackpads, hardware and software for speech recognition, optical scanners, optical pointers, digital image capture devices, and associated interpretation software, and similar devices.

[0262] The examples and drawings included herein illustrate, not limiting, specific embodiments in which the subject matter may be implemented. As stated above, other embodiments are available and can be derived from them, allowing for structural and logical substitutions and modifications without departing from the scope of this disclosure. Such embodiments of the subject matter of the invention may be referred to individually or collectively in this specification by the term “invention” for convenience only, even if two or more are actually disclosed, but this is not intended to spontaneously limit the scope of this application to any single invention or inventive concept. Thus, while specific embodiments have been illustrated and described herein, any arrangement configuration aimed at achieving the same objective is interchangeable with the specific embodiments shown. This disclosure is intended to cover any and all adapted or modified forms of various embodiments. Combinations of the embodiments described above and other embodiments not specifically described herein will be apparent to those skilled in the art upon careful examination of the above description.

Claims

1. A method for operating a vaporizer, The steps include establishing a connection between the vaporizer and the user device, The steps include: confirming that the user's age related to the vaporizer meets the age threshold based on the user information entered on the user device, and unlocking the device; The steps include determining whether the vaporizer is within the vicinity of the threshold of the user device, The steps include: disabling the vaporizer in response to a determination that the vaporizer is outside the vicinity of the threshold of the user device during a predetermined period of time immediately following the unlocking; A method that includes [a certain feature].

2. The method according to claim 1, further comprising the step of periodically or continuously monitoring the connection between the vaporizer and the user device to determine whether the vaporizer is within the vicinity of the threshold of the user device.

3. The method according to claim 1 or 2, wherein the vaporizer is enabled to operate in response to a determination that the user device is within the vicinity of the threshold.

4. The method according to any one of claims 1 to 3, further comprising the step of displaying vaporizer information via the user interface of the user device in response to a determination that the vaporizer is within the vicinity of the threshold of the user device.

5. The method according to any one of claims 1 to 4, further comprising the step of receiving Global Positioning System (GPS) information for identifying an updated age threshold in relation to the current geographical location of the vaporizer.

6. The method according to claim 5, further comprising the step of re-verifying whether the user's age meets the updated age threshold, and locking the vaporizer in accordance with the determination that the user's age does not meet the updated age threshold.

7. A vaporizer configured to wirelessly connect to a user device, At least one processor and Equipped with, The aforementioned at least one processor, Based on the user information entered on the user device, the system confirms that the user's age associated with the vaporizer meets the age threshold, and unlocks the device. Determine whether the vaporizer is within the vicinity of the threshold of the user device. A vaporizer system configured to disable the vaporizer in response to a determination that the vaporizer is outside the vicinity of the threshold of the user device during a predetermined period of time immediately following the unlocking.

8. The vaporizer system according to claim 7, wherein the processor is configured to periodically or continuously monitor the vaporizer to determine whether the vaporizer is within the vicinity of the threshold of the user device.

9. The vaporizer system according to claim 7 or 8, wherein the processor is configured to enable the vaporizer to operate in response to a determination that the vaporizer is within the vicinity of the threshold of the user device.

10. The vaporizer system according to any one of claims 7 to 9, wherein the processor is configured to display vaporizer information via the user interface of the user device in response to a determination that the vaporizer is within the vicinity of the threshold of the user device.

11. The vaporizer system according to any one of claims 7 to 10, wherein the processor is configured to receive Global Positioning System (GPS) information for identifying an updated age threshold in relation to the current geographical location of the vaporizer.

12. The vaporizer system according to claim 11, wherein the processor is configured to re-verify whether the user's age meets the updated age threshold and, in response to a determination that the user's age does not meet the updated age threshold, lock the vaporizer.

13. The vaporizer system according to any one of claims 7 to 12, wherein the at least one processor is located within the vaporizer and is configured to determine whether the vaporizer is within the vicinity of the threshold of the user device.

14. The vaporizer system according to any one of claims 7 to 12, wherein the at least one processor is located within the user device and is configured to determine whether the vaporizer is within the vicinity of the threshold of the user device.

Images