Engagement Index System

Abstract

A system configured to output an indicator of engagement with a device, the system including at least one processor and a memory coupled to the at least one processor, the memory configured to store instructions, the at least one processor configured to execute the instructions to cause the system to monitor usage of the device, determine an indicator of engagement with the device based on the usage of the device, and output the indicator of engagement with the device.

Description

[Technical Field]

[0001] The present disclosure relates to heated nanotube (HNB) aerosol generators and capsules configured to generate aerosols without substantial thermal decomposition of the aerosol-generating material. [Background technology]

[0002] Some electronic devices are configured to heat plant material to a temperature sufficient to release components of the plant material, while maintaining the temperature below the plant material's combustion point to avoid substantial thermal decomposition. Such devices are called aerosol generating devices (e.g., heated aerosol generating devices), and the heated plant material is tobacco and / or cannabis. In some examples, the plant material is introduced directly into the heating chamber of the aerosol generating device. In other examples, the plant material is pre-packaged in individual containers for easy insertion and removal from the aerosol generating device. Summary of the Invention

[0003]

[0009] Novel and useful systems, apparatus, and methods for refrigeration warning systems for aerosol generating devices are set forth in the accompanying claims. Exemplary embodiments are also provided to enable one skilled in the art to make and use the claimed subject matter.

[0004] For example, some exemplary embodiments describe a system configured to output an indication of engagement with a device. The system may include at least one processor and a memory coupled to the at least one processor. The memory may be configured to store instructions. The at least one processor may be configured to execute the instructions to cause the system to monitor usage of the device, determine the indication of engagement with the device based on the usage of the device, and output the indication of engagement with the device.

[0005] In some exemplary embodiments, the indicator of engagement with the device may include a hexadecimal representation. The hexadecimal representation may include two columns of five hexadecimal digits. The hexadecimal representation may encode at least one of a number of capsules used, an average number of puffs per capsule, an exact number of flight recorder events, or a data integrity check. In some exemplary embodiments, the at least one processor may be configured to execute the instructions to cause the device to output the indicator of engagement with the device on a communication screen of the device. In some exemplary embodiments, the at least one processor may be configured to execute the instructions to cause the device to output the hexadecimal representation in response to engagement with the device. In some exemplary embodiments, the last element of the hexadecimal representation may be a single digit. The single digit may represent overall engagement with the device.

[0006] In some exemplary embodiments, the indicator of engagement with the device may include a one-digit code. The one-digit code may be the last digit of a hexadecimal representation. In some exemplary embodiments, the one-digit code may represent overall engagement with the device. In some exemplary embodiments, the at least one processor is configured to determine the overall engagement with the device based on at least one of a number of capsules used, an average number of puffs per capsule, or an exact number of flight recorder events. In some exemplary embodiments, the at least one processor may be configured to execute the instructions to cause the device to output the one-digit code on a communication screen of the device. In some exemplary embodiments, the at least one processor may be configured to execute the instructions to cause the device to output the one-digit code on the communication screen of the device in response to an engagement with the device. The engagement with the device may include holding a button on the device, opening a lid on the device while the button is held, closing the lid on the device while the button is held, and releasing the button. In some exemplary embodiments, the one-digit code may be a number between 1 and 5, inclusive.

[0007] In some exemplary embodiments, the indicator of engagement with the device is configured to be remotely monitored.

[0008] In some exemplary embodiments, the at least one processor is configured to execute the instructions to cause the engagement indicator for the device to be adjusted as additional data is collected by the system.

[0009] In some demonstrative embodiments, the at least one processor is configured to execute the instructions to cause the indicator of engagement with the device to be adjusted to a period of usage, wherein the period of usage may be at least one of two days of usage or seven days of usage. [Brief explanation of the drawings]

[0010] Various features and advantages of the non-limiting embodiments herein will become more apparent from a consideration of the detailed description in conjunction with the accompanying drawings. The accompanying drawings are provided for illustrative purposes only and should not be construed as limiting the scope of the claims. The accompanying drawings are not to be considered as drawn to scale unless explicitly stated. Various dimensions of the drawings may be exaggerated for clarity.

[0011] [Figure 1] FIG. 1 is a top right front perspective view of an apparatus according to at least one exemplary embodiment.

[0012] [Figure 2] FIG. 1 is a top right front perspective view of the device with the lid open and the device containing a capsule.

[0013] [Figure 3] FIG.

[0014] [Figure 4] FIG.

[0015] [Figure 5] FIG. 1 is a block diagram of a device engagement index system according to an illustrative embodiment;

[0016] [Figure 6] 10 is a single-digit icon representing an indicator of engagement with a device according to an exemplary embodiment.

[0017] [Figure 7A] 10 is a hexadecimal icon representing an indication of engagement with a device according to an exemplary embodiment;

[0018] [Figure 7B] FIG. 7B is a diagram showing the bit code transition of the hexadecimal icon of FIG. 7A.

[0019] [Figure 8A] 10 is a chart sorting consumer data into single-digit icons according to an exemplary embodiment.

[0020] [Figure 8B] 10 is another chart sorting consumer data into single-digit icons according to an exemplary embodiment.

[0021] [Figure 9] 1 is a method of operating an engagement index system of a device according to an exemplary embodiment.

[0022] [Figure 10] 1 is a first step of a method for associating a device with displaying an icon representing an indication of engagement with the device according to an exemplary embodiment.

[0023] [Figure 11] 10 is a second step of a method for associating a device with displaying an icon representing an indication of engagement with the device according to an exemplary embodiment.

[0024] [Figure 12]10 is a third step of a method for associating with a device to display an icon representing an indication of engagement with the device according to an exemplary embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0025] Although several detailed exemplary embodiments are disclosed herein, the specific structural and functional details disclosed herein are merely representative for purposes of describing the exemplary embodiments, however, the exemplary embodiments may be embodied in many alternative forms and should not be construed as being limited to only the exemplary embodiments set forth herein.

[0026] Accordingly, while exemplary embodiments are susceptible to various modifications and alternative forms, exemplary embodiments thereof are shown by way of example in the drawings and will be described in detail herein. It should be understood, however, that there is no intention to limit the exemplary embodiments to the particular forms disclosed, but on the contrary, the exemplary embodiments are intended to encompass all modifications, equivalents, and alternatives falling within the scope of the exemplary embodiments. Like numbers refer to like elements throughout the description of the figures.

[0027] When an element or layer is referred to as "on," "connected to," "coupled to," or "covering" another element or layer, it is understood that it can be directly on, connected to, coupled to, or covering the other element or layer, or there can be intervening elements or layers. In contrast, when an element is referred to as "directly on," "directly connected to," or "directly coupled to" another element or layer, there are no intervening elements or layers. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0028] Although terms such as first, second, and third are used herein to describe various elements, regions, layers, and / or sections, it should be understood that these elements, regions, layers, and / or sections are not limited by these terms. These terms are used only to distinguish one element, region, layer, or section from another region, layer, or section. Thus, a first element, region, layer, or section described below could be referred to as a second element, region, layer, or section without departing from the teachings of the exemplary embodiments.

[0029] For convenience of description, spatially relative terms (e.g., "below," "lower," "lower side," "upper," "upper," etc.) may be used herein to describe the relationship of one element or feature to another element or feature as shown in the figures. It should be understood that spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. For example, if the device in the figures were inverted, elements described as "below" or "below" other elements or features would now be oriented "above" the other elements or features. Thus, the term "below" encompasses both an orientation of above and below. The device may be otherwise oriented (rotated 90 degrees or at other orientations), and the spatially relative descriptors used herein would be interpreted accordingly.

[0030] The terminology used herein is for the purpose of describing various exemplary embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It will be further understood that the terms "comprise," "include," "comprises," "consist," and / or "consisting of" specify the presence of stated features, integers, steps, operations, and / or elements, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, and / or groups thereof.

[0031] When the terms "about" or "substantially" are used in connection with numerical values ​​herein, it is intended that the associated numerical values ​​include a manufacturing or operating tolerance (e.g., ±10%) around the stated numerical value. Furthermore, when the terms "approximately" or "substantially" are used in connection with geometric shapes, it is intended that precision in the geometric shape is not required, but that freedom in shape is within the scope of the present disclosure. Furthermore, regardless of whether a numerical value or shape is modified by "about," "approximately," or "substantially," it will be understood that these numerical values ​​and shapes should be understood to include a manufacturing or operating tolerance (e.g., ±10%) around the stated numerical value or shape.

[0032] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the exemplary embodiments belong. Furthermore, terms, including those defined in commonly used dictionaries, should be interpreted as having a meaning consistent with the meaning in the context of the relevant art, and will not be interpreted in an idealized or overly formal sense unless expressly defined as such in this specification.

[0033] As used herein, "bonded" includes both removably bonded and permanently bonded. For example, if an elastic layer and a support layer are removably bonded to one another, the elastic layer and the support layer can be separated upon application of sufficient force.

[0034] Hardware may be implemented using processing or control circuitry such as, but not limited to, one or more processors, one or more central processing units (CPUs), one or more microcontrollers, one or more arithmetic logic units (ALUs), one or more digital signal processors (DSPs), one or more microcomputers, one or more field programmable gate arrays (FPGAs), one or more systems on a chip (SoCs), one or more programmable logic units (PLUs), one or more microprocessors, one or more application specific integrated circuits (ASICs), or other devices capable of responding to and executing instructions in a specified manner.

[0035] 1-4 are diagrams of a device 100 according to some exemplary embodiments. In some embodiments, the device 100 is an aerosol generating device (e.g., a heated nitrogen (HNB) aerosol generating device). Referring to FIG. 1, a top perspective view of the device 100 is shown. In some embodiments, the body of the device 100 has a generally rectangular or rounded pebble shape. The body of the device 100 includes a housing 102 and a lid mechanism or lid 104. The housing 102 has a first end 106 and a second end 108 opposite the first end 106. The lid has a first end 110 and a second end 112 opposite the first end 110. The first end 110 of the lid 104 is fixedly coupled to the second end 108 of the housing 102 at a first point 114 and removably coupled to the second end 108 of the housing 102 at a second point 116. A first point 114 of the housing 102 is on a first side 118 of the device 100. A second point 116 of the housing 102 is on a second side 120 of the device 100.

[0036] In some exemplary embodiments, device 100 further includes a mouthpiece 122. In at least some exemplary embodiments, mouthpiece 122 includes a first end 124 and a second end 126 opposite first end 124. Second end 126 of mouthpiece 122 is coupled to second end 112 of lid 104. In some embodiments, second end 126 of mouthpiece 122 is removably coupled to second end 112 of lid 104. In at least one exemplary embodiment, mouthpiece 122 tapers between first end 124 and second end 126. For example, the diameter or average length / width dimension of first end 124 is smaller than the diameter or average length / width dimension of second end 126. Toward first end 124, the taper has a slight inward curvature 128 configured to receive the lips of an adult consumer and improve comfort and experience. In some embodiments, first end 124 has an oval or elliptical shape and includes one or more outlets 130. For example, first end 124 may include four outlets 130 to engage four or more different areas or quadrants of an adult consumer's mouth during use of device 100. In other embodiments, mouthpiece 122 has fewer than four outlets 130 or more than four outlets 130.

[0037] In some exemplary embodiments, the housing 102 includes a consumer interface panel 132 disposed on the second side 120 of the device 100. For example, the consumer interface panel 132 is an oval-shaped panel extending along the second side 120 of the device 100. The consumer interface panel 132 includes an unlatch button 134, as well as a communication screen 136 and / or control buttons 138. For example, in at least some exemplary embodiments, the consumer interface panel 132 includes the communication screen 136 disposed between the unlatch button 134 and the control buttons 138. As shown, the unlatch button 134 is disposed toward the second end 108 of the device 100, and the control buttons 138 are disposed toward the first end 106 of the device 100. The unlatch button 134 and the control buttons 138 are adult consumer relationship buttons. The unlatch button 134 and control button 138 have a substantially circular shape with a central indentation or depression configured to direct pressure applied by an adult consumer, although exemplary embodiments are not limited in this respect. The control button 138 powers the device 100 on and off. While only two buttons are shown, it should be understood that more or fewer buttons may be provided depending on the available functionality and desired adult consumer interface.

[0038] Communication screen 136 is a user interface such as a human-machine interface (HMI) display. In at least one exemplary embodiment, communication screen 136 is an integrated thin film transistor ("TFT") screen. In other exemplary embodiments, communication screen 136 is an organic light-emitting diode ("OLED") or light-emitting diode ("LED") screen. Communication screen 136 is configured for adult consumer engagement and has a generally rectangular shape.

[0039] In some embodiments, the exterior of the housing 102 and / or lid 104 is formed from metal (e.g., aluminum, stainless steel, etc.), an aesthetically pleasing food-contact plastic (e.g., polycarbonate (PC), acrylonitrile-butadiene-styrene (ABS) material, liquid crystal polymer (LCP), copolyester plastic, or any other suitable polymer and / or plastic, etc.), or any combination thereof. The mouthpiece 122 is similarly formed from metal (e.g., aluminum, stainless steel, etc.), an aesthetically pleasing food-contact plastic (e.g., polycarbonate (PC), acrylonitrile-butadiene-styrene (ABS) material, liquid crystal polymer (LCP), copolyester plastic, or any other suitable polymer and / or plastic, etc.), and / or a plant-based material (e.g., wood, bamboo, etc.). One or more interior surfaces of the housing 102 and / or lid 104 are formed from or coated with a high-temperature plastic (e.g., polyetheretherketone (PEEK), liquid crystal polymer (LCP), etc.).

[0040] 2 is another top perspective view of the device 100 with the lid 104 in an open configuration. The lid 104 is fixedly coupled to the housing 102 at a first point 114 by a hinge 202 or other similar connector that allows the lid 104 to move (e.g., swing and rotate) from an open position to a closed position. In some embodiments, the hinge 202 is a torsion spring. In at least some exemplary embodiments, the housing 102 includes a recess 204 at the first point 114. The recess 204 is configured to receive a portion of the lid 104 to allow easy and smooth movement of the lid 104 from the open position to the closed position (and vice versa). The recess 204 has a structure that corresponds to a corresponding portion of the lid 104. For example, as shown, the recess 204 includes a substantially curved portion 206 having a generally concave shape that corresponds to the curvature of the lid 104, which has a generally convex shape.

[0041] The lid 104 is removably coupleable to the housing 102 at the second point 116 by a latch 208 or other similar connector that allows the lid 104 to be anchored or secured in a closed position, and is easily detachable to allow the lid 104 to move from the closed position to the open position. In at least one exemplary embodiment, the latch 208 is coupled to an unlatching mechanism disposed within the housing. The unlatching mechanism is configured to move the latch 208 from a first or closed position to a second or open position.

[0042] 2, when the lid 104 is in the open position, a capsule receiving cavity 210 in the housing 102 is exposed. A capsule connector 212 defines the capsule receiving cavity 210 in the housing 102. In some embodiments, the capsule connector 212 is mounted or otherwise secured to a printed circuit board (PCB) within the housing 102.

[0043] As shown in FIG. 2 , capsule 214 is received by capsule-receiving cavity 210. Although not shown herein, in some embodiments, a gasket is disposed around capsule 214 to help secure capsule 214 in place within housing 102. Capsule 214 includes housing 216 configured to contain the aerosol-generating material and heater. In some embodiments, housing 216 is in the form of a cover, such as a shell or box sleeve. In some embodiments, capsule 214 may include first end cap 217 and second end cap. The second end cap faces first end cap 217, thereby positioning capsule 214 within housing 102 when capsule 214 is received by capsule-receiving cavity 210.

[0044] As described herein, an aerosol-generating material or consumable is a material or combination of materials that generates an aerosol. Aerosol refers to a substance generated or produced by the disclosed and claimed devices, and equivalents thereof. The material includes a compound (e.g., nicotine, cannabinoids) that, when heated, generates an aerosol containing the compound. The heating is below combustion temperatures to generate an aerosol without substantial thermal decomposition of the aerosol-generating material or substantial generation of combustion by-products, if any. Thus, in exemplary embodiments, no thermal decomposition occurs during heating and the resulting generation of the aerosol. In other instances, thermal decomposition and combustion by-products are present, but to a relatively minor extent and / or are considered merely incidental.

[0045] The aerosol-generating material is a fibrous material. For example, the fibrous material is a plant material. The fibrous material is configured to release a compound when heated. The compound is a natural component of the fibrous material. For example, the fibrous material is a plant material such as tobacco, and the released compound is nicotine. The term "tobacco" includes any tobacco plant material, including tobacco leaf, tobacco plugs, reconstituted tobacco, compressed tobacco, formed tobacco, or powder tobacco, and combinations from one or more tobacco plants, such as Nicotiana rustica and Nicotiana tabacum.

[0046] In some exemplary embodiments, the tobacco material includes material from any member of the Nicotiana genus. Additionally, the tobacco material includes a blend of two or more different tobacco varieties. Suitable types of tobacco material for use include, but are not limited to, flue-cured tobacco, burley tobacco, dark tobacco, Maryland tobacco, Oriental tobacco, rare tobacco, specialty tobacco, blends thereof, and the like. The tobacco material may be provided in any suitable form, including, but not limited to, tobacco lamina, processed tobacco materials such as expanded tobacco or puffed tobacco, processed tobacco stems such as cut rolling stems or cut puffed stems, reconstituted tobacco materials, blends thereof, and the like. In some exemplary embodiments, the tobacco material is in the form of a substantially dried tobacco mass. Furthermore, in some examples, the tobacco material is mixed and / or combined with at least one of propylene glycol, glycerin, subcombinations thereof, or combinations thereof.

[0047] The compound is a natural component of a medicinal plant that has a medically acceptable therapeutic effect. For example, the medicinal plant is the cannabis plant, and the compound is a cannabinoid. Cannabinoids interact with receptors in the body, resulting in various effects. As a result, cannabinoids have been used for a variety of medicinal purposes (e.g., treating pain, nausea, epilepsy, and psychiatric disorders). The fibrous material includes leaf and / or flower material from one or more cannabis plants, such as Cannabis sativa, Cannabis indica, and Cannabis ruderalis. In some examples, the fibrous material is a mixture of 60-80% (e.g., 70%) Cannabis sativa and 20-40% (e.g., 30%) Cannabis indica.

[0048] Cannabinoids include tetrahydrocannabinolic acid (THCA), tetrahydrocannabinol (THC), cannabidiolic acid (CBDA), cannabidiol (CBD), cannabinol (CBN), cannabicyclol (CBL), cannabichromene (CBC), and cannabigerol (CBG). Tetrahydrocannabinolic acid (THCA) is a precursor of tetrahydrocannabinol (THC), and cannabidiolic acid (CBDA) is a precursor of cannabidiol (CBD). Tetrahydrocannabinolic acid (THCA) and cannabidiolic acid (CBDA) are converted to tetrahydrocannabinol (THC) and cannabidiol (CBD), respectively, upon heating. In an exemplary embodiment, heat from a heater causes decarboxylation to convert tetrahydrocannabinolic acid (THCA) in the capsule to tetrahydrocannabinol (THC) and / or cannabidiolic acid (CBDA) in the capsule to cannabidiol (CBD).

[0049] When both tetrahydrocannabinolic acid (THCA) and tetrahydrocannabinol (THC) are present in the capsule, decarboxylation and the resulting conversion will cause a decrease in tetrahydrocannabinolic acid (THCA) and an increase in tetrahydrocannabinol (THC). At least 50% (e.g., at least 87%) of the tetrahydrocannabinolic acid (THCA) will be converted to tetrahydrocannabinol (THC) during heating of the capsule. Similarly, when both cannabidiolic acid (CBDA) and cannabidiol (CBD) are present in the capsule, decarboxylation and the resulting conversion will cause a decrease in cannabidiolic acid (CBDA) and an increase in cannabidiol (CBD). At least 50% (e.g., at least 87%) of the cannabidiolic acid (CBDA) will be converted to cannabidiol (CBD) during heating of the capsule.

[0050] Furthermore, the compound may be or additionally include a non-natural additive that is subsequently introduced into the fibrous material. In one example, the fibrous material includes at least one of cotton, polyethylene, polyester, rayon, combinations thereof, etc. (e.g., in the form of gauze). In another example, the fibrous material is a cellulosic material (e.g., a non-tobacco material and / or a non-cannabis material). In either example, the introduced compound may include nicotine, a cannabinoid, and / or a flavoring. The flavoring may be naturally derived, such as a plant extract (e.g., tobacco extract, cannabis extract), and / or artificially derived. In yet another example, when the fibrous material includes tobacco and / or cannabis, the compound may be or additionally include one or more flavorings (e.g., menthol, mint, vanilla). Thus, the compound within the aerosol-generating material may include natural and / or non-natural additives. It should be understood that the level of natural components present in the aerosol-generating material may be increased by supplementation. For example, the level of nicotine present in tobacco may be increased by supplementing with an extract containing nicotine. Similarly, the levels of one or more cannabinoids present in cannabis may be increased by supplementing with an extract containing such cannabinoids.

[0051] First end cap 217 can include a first opening 218. In some embodiments, first opening 218 is a series of openings disposed through first end cap 217. Similarly, in some embodiments, second end cap can include a second opening that is also a series of openings. In some embodiments, first end cap 217 and / or second end cap are transparent to function as a window configured to allow viewing of the contents / components (e.g., aerosol-generating material and / or heater) within capsule 214.

[0052] The capsule receiving cavity 210 has a base that is internal to the housing 102. In some embodiments, the base includes at least one contact configured to couple to one or more contacts of the capsule 214 when the capsule 214 is received by the capsule receiving cavity 210. When the capsule 214 is inserted into the capsule receiving cavity 210, the weight of the capsule 214 itself is not sufficient to compress the at least one contact of the base of the capsule receiving cavity 210. As a result, the capsule 214 simply rests on the exposed pin of the at least one contact without compressing (or significantly compressing) the electrical contact of the at least one contact. Furthermore, when the lid 104 itself is rotated to the closed position, it does not compress the electrical contact of the at least one contact to a significant extent, but instead simply rests on the capsule 214 in an intermediate, partially open / closed position. In such an example, the intentional act of closing the lid 104 (e.g., a downward force) causes the surface 220 of the lid 104 to press down on the capsule 214 to provide the desired seal and also compress the capsule 214, thereby ensuring complete electrical contact of at least one contact.

[0053] Additionally, full closure of the lid 104 results in engagement with the latch 208. This engagement maintains the closed position and the desired mechanical / electrical engagement involving the capsule 214 until released (e.g., via the unlatch button 134). The force required to close the lid 104 helps to ensure and / or improve the air / aerosol seal and provide a stronger electrical connection, as well as improve device and thermal efficiency and battery life by reducing or eliminating initial power consumption and / or parasitic heating of the capsule 214.

[0054] The lid 104 includes an internal cavity 222 adapted to receive the housing 102 when the lid is in the closed position. In some embodiments, the internal cavity 222 of the lid 104 includes an abutment or engagement member, or surface 220, configured to engage the capsule 214 when the lid 104 is rotated to the closed position. The surface 220 of the lid 104 includes a recess corresponding to the size and shape of the capsule and / or a resilient material that strengthens the interface with the capsule to provide the desired seal. In some embodiments, the lid 104 further includes an opening 224 adapted to receive the second end 126 of the mouthpiece 122. The mouthpiece 122 includes at least one extension 226 that is received by the opening 224 of the lid 104 to secure the mouthpiece 122 to the lid 104. In some embodiments, the lid 104 further includes a protrusion configured to mate with a recess 228 of the housing 102. The protrusion fits within the recess 228 when the lid 104 is coupled to the housing 102 in the closed position.

[0055] Referring to FIG. 3 , a bottom perspective view of device 100 is shown. In some embodiments, housing 102 defines a port or charging connector 250. The charging connector is defined or disposed at first end 106 of housing 102. Charging connector 250 is configured to receive current from an external power source (e.g., via a USB / mini-USB cable) to charge a power source internal to device 100. In some embodiments, a protective grille 252 is disposed around charging connector 250. Protective grille 252 is configured to help reduce or prevent the ingress of debris and / or the inadvertent blockage of incoming airflow. For example, protective grille 252 defines a plurality of holes 254 along its length or course. As shown, protective grille 252 has an annular configuration surrounding charging connector 250. Note that holes 254 are disposed around charging connector 250 (e.g., in a series). Each hole 254 has, but is not limited to, an oval or circular shape. In at least one exemplary embodiment, protective grill 252 comprises an approved food contact material. For example, protective grill 252 comprises plastic, metal (e.g., stainless steel, aluminum), or any combination thereof. In at least one exemplary embodiment, the surface of protective grill 252 is coated with a thin layer of plastic and / or anodized, for example.

[0056] The holes 254 in the protective grille 252 function as inlets for air to be drawn into the device 100. During operation of the device 100, ambient air entering through the holes 254 in the protective grille 252 around the charging connector 250 will converge to form a combined flow leading to the capsule 214. For example, the holes 254 are in fluid communication with the capsule receiving cavity 210. In at least one exemplary embodiment, air is drawn from the holes 254 through the capsule receiving cavity 210. For example, the air is drawn out of the mouthpiece 122 through the capsule 214 received by the capsule receiving cavity 210.

[0057] 4, a bottom view of device 100 is shown. In some embodiments, charging connector 250 is an assembly defining a cavity 256 with a protrusion 258 within cavity 256. In at least one exemplary embodiment, protrusion 258 does not extend beyond the edge of cavity 256. Additionally, charging connector 250 is configured to transmit and / or receive data (e.g., via a USB / mini-USB cable) to other aerosol generating devices (e.g., heated-type (HNB) aerosol generating devices) and / or other electronic devices (e.g., phones, tablets, computers, etc.). In at least one embodiment, device 100 is alternatively or additionally configured to wirelessly communicate (e.g., via Bluetooth) with such other aerosol generating devices and / or electronic devices.

[0058] As will be appreciated, the device 100 and capsule 214 may include additional components (e.g., heaters and internal air flow paths) as described in Atty. Docket No. 24000NV-000847-US, filed September 19, 2022, assigned application serial number 17 / 947,436, and entitled "HEAT-NOT-BURN (HNB) AEROSOL-GENERATING DEVICES AND CAPSULES," the entire contents of which are incorporated herein by reference.

[0059] 5 , a block diagram of an engagement index system 500 for device 100 is shown, according to an example embodiment. In some embodiments, engagement index system 500 is configured to monitor usage of device 100 and determine consumer engagement with device 100. Engagement index system 500 is further configured to output an indicator of engagement with device 100 (usage score indicator). In some embodiments, the indicator of engagement with device 100 provides an indicator of at least one of the following: number of capsules used or heated, average number of puffs per capsule, accurate count of flight recorder events, and / or data integrity check of device 100.

[0060] Engagement index system 500 includes processor 502, memory 504, control buttons 138, mechanism detection switches 508, power supply 510, communication screen 136, heater 512, airflow sensor 514, charging contacts 516, temperature sensor 518, and battery monitoring system 520. In some embodiments, memory 504 includes capsule variables 522, suction variables 524, flight recorder event log 526, and flight recorder event variables 528. Processor 502 includes timer 530. In other embodiments, capsule variables 522, suction variables 524, flight recorder event log 526, and flight recorder event variables 528 are stored in processor 502, such as in local storage of processor 502, and timer 530 is executed using instructions stored in memory 504. In some embodiments, processor 502 includes memory 504. The processor 502 is in communication with the memory 504 , the control buttons 138 , the mechanism detection switch 508 , the power supply 510 , the communication screen 136 , the heater 512 , the airflow sensor 514 , the charging contacts 516 , the temperature sensor 518 , and the battery monitoring system 520 .

[0061] The processor 502 may be hardware including logic circuits, a hardware / software combination configured to execute software, or a combination thereof. For example, the processor 502 may include, but is not limited to, a central processing unit (CPU), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a system on a chip (SoC), a programmable logic unit, a microprocessor, an application specific integrated circuit (ASIC), or other similar devices. The processor 502 may be configured as a special purpose machine (e.g., a processing unit) and execute software or instructions stored in the memory 504. The software may be embodied as program code including instructions for performing and / or controlling any or all of the operations described herein as executed by the processor 502.

[0062] In other exemplary embodiments, other processing and / or control circuits are used.

[0063] While memory 504 is illustrated as being external to processor 502, in some exemplary embodiments, memory 504 is integrated with processor 502. Memory 504 may refer to any of the terms "storage medium," "computer-readable storage medium," or "non-transitory computer-readable storage medium," which may refer to one or more devices for storing data, including special-purpose memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage media, optical storage media, flash memory devices, and / or other tangible machine-readable media for storing information. The term "computer-readable medium" includes, but is not limited to, portable or permanent storage devices, optical storage devices, and various other media capable of storing, storing, or transporting instructions and / or data.

[0064] The capsule variable 522 is a counter that represents the number of capsules that have been used. The capsule variable 522 is set to zero when the device 100 is new and has not been used by a consumer. The capsule variable 522 is incremented by one each time a capsule is detected. A capsule is detected by the device 100 if it has been heated for at least 10 seconds. In some embodiments, a timer 530 is started by the processor 502 when power is applied to the heater 512. When the timer 530 reaches 10 seconds, the capsule variable 522 is incremented by one.

[0065] The suck variable 524 is a counter representing the number of sucks taken. The suck variable 524 is set to zero when a session ends, so that the suck variable 524 measures the number of sucks taken by the consumer each time a capsule is activated. The suck variable 524 is incremented by one each time a suck is detected. A suck is detected when a consumer places their mouth over the mouthpiece 122 of the device 100 and then applies negative pressure through the mouthpiece 122 of the device 100. In some embodiments, the suck variable 524 is configured to store the number of sucks taken per capsule and to store the average number of sucks taken per capsule. In some embodiments, the processor 502 and / or memory 504 are configured to calculate the average number of sucks taken per capsule. In some embodiments, the average number of sucks per capsule is updated each time a capsule is inserted into the device 100 and activated as described above.

[0066] Flight recorder event log 526 is configured to record events for device 100. For example, flight recorder event log 526 records when device 100 is inserted into and / or removed from a charger, when lid 104 is opened and / or closed, when a capsule is inserted into device 100, when a session is started and / or ended, and when control button 138 and / or unlatch button 134 are pressed. Additional events that may be recorded in flight recorder event log 526 are shown in the table below. In some embodiments, flight recorder event log 526 is configured to record more than 100 different interactions with device 100. Flight recorder event variable 528 is a counter that represents the number of events shown in flight recorder event log 526. Flight recorder event variable 528 is incremented by one each time a new event is added to flight recorder event log 526. [Table 1-1] [Table 1-2] [Table 1-3] Table 1: Events recorded in the Flight Recorder event log

[0067] In some embodiments, capsule variables 522, suction variables 524, flight recorder event log 526, and flight recorder event variables 528 are stored in memory 504 or in local memory that is part of processor 502. In some embodiments, because these variables (metrics) are stored in local memory, they will be preserved even if the battery is completely discharged. Furthermore, capsule variables 522, suction variables 524, flight recorder event log 526, and flight recorder event variables 528 are not reset to zero unless device 100 is reset to a factory default state. In some embodiments, device 100 is reset to a factory default state at the start of a device interrogation session.

[0068] Control button 138 is configured to generate a signal indicating that the consumer has placed device 100 in the "on" state if device 100 was previously in the "off" state, or that the consumer has placed device 100 in the "off" state if device 100 was previously in the "on" state. Control button 138 may also be pressed during a series of interactions with device 100 to display a message on communication screen 136. For example, a consumer may press control button 138 and complete an additional interaction with device 100 to display an indicator of their engagement with device 100 on communication screen 136.

[0069] The mechanism detection switch 508 is configured to generate a signal indicating that a lid mechanism, such as the lid 104 of the device 100, has been opened. The mechanism detection switch 508 may be a push button switch, a toggle button, a capacitance sensor, an IR sensor, a magnetic detection sensor such as a Hall Effect sensor, or other element configured to communicate with the processor 502 that the lid 104 of the device 100 has been opened. If the lid 104 of the device 100 is opened, any ongoing session of the device 100 is terminated. The mechanism detection switch 508 is configured to generate a signal indicating that the lid 104 has been opened when the unlatch mechanism of the device 100 releases the latch 208. Additionally or alternatively, the mechanism detection switch 508 is coupled to the unlatch button 134 and generates a signal indicating that the lid 104 of the device 100 has been opened when the unlatch button 134 is pressed. More specifically, mechanism detection switch 508 is disposed within recess 228 such that closing lid 104 of device 100 activates mechanism detection switch 508 .

[0070] In some embodiments, the housing 102 of the device 100 contains or houses a power source 510. The power source 510 includes one or more batteries, such as a rechargeable dual battery configuration, a lithium ion battery, and / or a fuel cell. The power source 510 is configured to receive current provided to the device 100 via a port to charge the power source 510. The battery monitoring system 520 generates a signal indicating that the device 100 has entered a low battery condition when the charge on the power source 510 falls below a predetermined threshold.

[0071] Communication screen 136 displays information related to device 100. Communication screen 136 displays one or more icons for communicating information related to device 100. For example, communication screen 136 displays one or more engagement indicator icons. In some embodiments, the engagement indicator is a single digit code or a hexadecimal code.

[0072] The heater 512 is housed within the device 100 and configured to heat the capsule 214 of the device 100. In some embodiments, the heater 512 is coupled to one or more elements of a heating voltage measurement circuit, a heating current measurement circuit, and / or a compensation measurement circuit, substantially as described in U.S. Application No. 17 / 15 / 409, filed January 18, 2021, and entitled "HEAT-NOT-BURN (HNB) AEROSOL-GENERATING DEVICES INCLUDING INTRA-DRAW HEATER," the disclosure of which is incorporated herein by reference in its entirety.

[0073] Airflow sensor 514 is configured to detect and / or measure characteristics of airflow through device 100. For example, airflow sensor 514 is configured to sense that air is flowing through device 100. In at least one exemplary embodiment, airflow sensor 514 is a microelectromechanical systems (MEMS) flow or pressure sensor, or other type of sensor configured to measure airflow, such as a hot wire anemometer. In other embodiments, airflow sensor 514 is other known sensors. Airflow sensor 514 is operated as an aspiration sensor that detects aspiration at flow rates of about 1 mL / s or greater, and then terminates aspiration when the flow rate drops to about 0 mL / s. In an exemplary embodiment, airflow sensor 514 is a MEMS flow sensor-based differential pressure sensor that converts differential pressure (in Pascals) to instantaneous flow rate readings (in mL / s) using a curve-fitting calibration function or lookup table (of flow rate values ​​for each differential pressure reading). In another exemplary embodiment, the flow sensor is a capacitive pressure drop sensor.

[0074] In some embodiments, airflow sensor 514 is communicatively coupled to processor 502 such that processor 502 is configured to measure the length of time that airflow is flowing through device 100. While airflow sensor 514 may be described as detecting suction, it should be understood that it is processor 502 detecting signals received from airflow sensor 514 that detects that suction is being applied. In some embodiments, suction is detected when negative pressure is detected through mouthpiece 122 of device 100.

[0075] Charging contacts 516 are configured to generate a signal indicating that device 100 is connected to a charger. In some embodiments, housing 102 of device 100 includes a charging connector or port, such as charging connector 250. For example, the port is defined / located on first end 106 of housing 102. The port receives current from an external power source (e.g., via a USB / mini-USB cable) to charge a power source, such as power supply 510, built into device 100. Charging contacts 516 are configured to detect when the port of device 100 is receiving current.

[0076] Temperature sensor 518 is configured to measure the temperature of device 100. In some embodiments, temperature sensor 518 is a thermistor or a thermocouple. More specifically, temperature sensor 518 is positioned proximate capsule 214 of device 100 and is configured to measure the temperature of an area proximate capsule 214 of device 100 and determine when capsule 214 is removed from device 100.

[0077] Battery monitoring system 520 is configured to generate a signal indicating that device 100 has experienced a low battery condition.

[0078] Referring to FIG. 6 , a single-digit code 602 is shown. The single-digit code 602 is displayed by the processor 502 on the communication screen 136 as an output of an indicator of engagement with the device. The single-digit code 602 represents an overall indicator of engagement with the device 100. In some embodiments, the single-digit code 602 is adjusted based on the duration of use of the device 100. For example, the duration of use may be two days of use, seven days of use, or some other duration. For example, the single-digit code 602 is a number ranging from 1 to 5. The lower the number, the less engaged the consumer is with the device 100. For example, a "1" indicates a low level of engagement, a "5" indicates a high level of engagement, and a "3" indicates an average level of engagement. The processor 502 determines the single-digit code from at least the capsule variable 522, the suction variable 524, and the flight recorder event variable 528. In some embodiments, additional variables are monitored and used to determine the single-digit code 602.

[0079] Referring to FIG. 7A , a hexadecimal code 702 is shown. The hexadecimal code 702 is displayed by the processor 502 on the communication screen 136 as an output of an indicator of engagement with the device. The hexadecimal code 702 is a 10-digit hexadecimal code. In some embodiments, the hexadecimal code 702 is displayed as two lines of five elements, such as a first line 704 and a second line 706. Each element is either a letter A through F or a number 0 through 9. Each element of the hexadecimal code 702 represents a variable related to the usage of the device 100. In some embodiments, the hexadecimal code 702 is adjusted based on the duration of use of the device 100. For example, the duration of use may be two days of use, seven days of use, or some other duration. In some embodiments, the capsule variable 522, the aspiration variable 524, and the flight recorder event variable 528 are each represented by an element of the hexadecimal code, and may be represented by a single element or two elements.

[0080] In some embodiments, any of the first nine elements of hex code 702 represent capsule variables 522, suction variables 524, and flight recorder event variables 528. Additionally or alternatively, the first nine elements of hex code 702 are used to encode additional information about device 100.

[0081] In some embodiments, one or more elements of hex code 702 are or represent capsule variables 522. In some embodiments, the elements of hex code 702 that represent capsule variables 522 are a rectified or coded representation of capsule variables 522 that can be decoded to determine the total number of capsules used by device 100. In some embodiments, one or more elements of hex code 702 are or represent flight recorder event variables 528. In some embodiments, the elements of hex code 702 that represent flight recorder event variables 528 are a rectified or coded representation of flight recorder event variables 528 that can be decoded to determine the total number of flight recorder events in flight recorder event log 526. In some embodiments, one or more elements of hex code 702 are or represent the average number of puffs taken per capsule represented by puff variable 524. In some embodiments, the element of the hexadecimal code 702 representing the suction variable 524 is an adjusted or coded representation of the suction variable 524 that can be decoded to determine the average suction recovery aspirated per capsule.

[0082] In some embodiments, one or more elements of the hexadecimal code 702 are data integrity check values, such as a checksum. In some embodiments, the data integrity check value is binary data that indicates whether the data is of good quality or not. If the data is corrupted, the data is considered to be of poor quality or has problems with one or more variables measured by the engagement index system 500. In other embodiments, the data integrity check value is encoded into multiple elements of the hexadecimal code 702. The data integrity check or checksum is a data redundancy check that is used as a pass / fail function to determine whether the consumer correctly interpreted and / or read the hexadecimal code 702. In some embodiments, the checksum is a standard cyclic redundancy check.

[0083] In some embodiments, the last element of the hexadecimal code is an overall indicator of engagement with the device 100. The last element is a number between 1 and 5, inclusive, where 1 indicates a low level of engagement with the device and 5 indicates a high level of engagement with the device 100. In some embodiments, the last digit of the hexadecimal code is the single-digit code 602 described above with reference to FIG.

[0084] 7B, the hex code 702 is calculated or determined from the 40-bit code as shown in process 750. In some embodiments, a data integrity check or checksum 752, an average number of puffs per capsule or puff variable 524, a total number of capsules used or actuated or capsule variable 522, a total number of events recorded in the flight recorder event log 526 or flight recorder event variable 528, and an overall indicator or summary digit 754 of device 100 involvement are stored in the 40-bit code. In some embodiments, the overall indicator or summary digit 754 of device involvement is a local summary digit and is stored in bits 0-3 of the 40-bit code. The flight recorder event variable 528 is stored in bits 4-12 of the 40-bit code. In some embodiments, flight recorder event variable 528 is stored with a resolution of 10,000 and rounded up so that flight recorder event variable 528 has a value range of 10,000 to 511,000, inclusive, as stored in a 40-bit code. Capsule variable 522 is stored in bits 13-24 of the 40-bit code. In some embodiments, capsule variable 522 has a range of 0 to 4095, inclusive. Suction variable 524 is stored in bits 25-31 of the 40-bit code. In some embodiments, suction variable 524 is stored with a resolution of 0.25, inclusive, and has a value range of 0 to 31.75, inclusive. Data integrity check or checksum 752 is stored in bits 32-39 of the 40-bit code. In some embodiments, suction variable 524, capsule variable 522, flight recorder event variable 528, and summary digit 754 are used to calculate checksum 752.

[0085] In some embodiments, capsule variable 522, suction variable 524, and flight recorder event variable 528 are compressed into a 32-bit word as described above. In some embodiments, this 32-bit word of capsule variable 522, suction variable 524, and flight recorder event variable 528 is XORed with a 28-bit constant "magic number" 756. The bits comprising capsule variable 522, suction variable 524, and flight recorder event variable 528 are XORed with magic number 756 to create a cipher. This cipher obfuscates fields in bits 4-31 of the 32-bit code. For example, this helps prevent misinterpretation of capsule variable 522, suction variable 524, and flight recorder event variable 528. When the capsule variable 522, the suction variable 524, and the flight recorder event variable 528 are XORed with the magic number 756, a summary digit 754 is calculated and added to bits 0-3 of the 40-bit code, and then a checksum 752 is calculated and added to bits 32-39 of the 40-bit code. Once each bit of the 40-bit code is determined, a hexadecimal code 702 is determined.

[0086] In some embodiments, the hexadecimal code 702 is replaced with a machine-readable code, such as a QR code, that is scannable by a device, such as a smartphone, configured to interpret and / or display one or more variables encoded by the machine-readable code. In some embodiments, when the machine-readable code is scanned, the variables encoded by the machine-readable code are further transmitted to a research facility or other remote location, such as via email.

[0087] FIG. 8A shows a chart 800 illustrating an example distribution of consumer data corresponding to a single-digit indicator of engagement, such as single-digit code 602. Chart 800 organizes data collected from one or more consumer surveys, including the number of capsules used with device 100, the number of flight recorder events for device 100, and the average number of puffs taken per capsule. These variables are analyzed, and consumers are categorized or organized and scored based on their engagement with device 100. The variables are adjusted and / or organized based on duration of use, as described above. By adjusting or organizing the data based on duration of device 100 use, consumers who use device 100 for a certain number of days can be compared to other consumers who use device 100 for the same number of days. This allows the data to be organized and analyzed to understand the consumer's relationship with device 100.

[0088] In some embodiments, if a consumer uses a number of capsules that is 20% or less of the consumer data, has a total number of flight recorder events that is 20% or less of the consumer data, or takes an average number of puffs per capsule that is 20% or less of the consumer data, the engagement index is considered low and assigned a score of "1." If a consumer uses a number of capsules that is 21% or more but not more than 39% of the consumer data, has a total number of flight recorder events that is 21% or more but not more than 39% of the consumer data, or takes an average number of puffs per capsule that is 21% or more but not more than 39% of the consumer data, the engagement index is assigned a score of "2." If a consumer uses a number of capsules that is 40% or more but not more than 60% of the consumer data, has a total number of flight recorder events that is 40% or more but not more than 60% of the consumer data, or takes an average number of puffs per capsule that is 40% or more but not more than 60% of the consumer data, the engagement index is considered average and assigned a score of "3." If a consumer uses a number of capsules that is between 61% and 79% of the consumer's data, has a total number of flight recorder events that is between 61% and 79% of the consumer's data, or takes an average number of puffs per capsule that is between 61% and 79% of the consumer's data, the engagement index will be assigned a score of "4." If a consumer uses a number of capsules that is 80% or more of the consumer's data, has a total number of flight recorder events that is 80% or more of the consumer's data, or takes an average number of puffs per capsule that is 80% or more of the consumer's data, the engagement index will be considered high and assigned a score of "5."

[0089] In other embodiments, percentages are adjusted, additional variables influence the engagement index, and / or some variables are weighted to have a greater or lesser impact on the engagement index for device 100. For example, in some embodiments, if any of the above variables are present in 10% or less of the consumer data, the engagement index is considered low and is assigned a score of "1." Additionally, if additional consumer data is obtained, the engagement index for device 100 is updated and / or adjusted. For example, single-digit code 602 and / or hexadecimal code 702 are adjusted and updated if additional consumer data is obtained.

[0090] In some embodiments, the single-digit code 602 is calculated by the processor 502 using the formula: SDC=ROUND((P*0.40)+(C*0.50)+(E*0.1)), where SDC is the single-digit code 602, P is the single-digit representation of the average number of puffs per capsule or puff variable 524, C is the single-digit representation of the total number of capsules or capsule variable 522, and E is the single-digit representation of the total number of events recorded in the flight recorder event log 526 or flight recorder event variable 528. As indicated by the above formula, the single-digit representation of the average number of puffs per capsule is given a weighting of 40% for the single-digit code 602, the single-digit representation of the total number of capsules is given a weighting of 50%, and the single-digit representation of the total number of flight recorder events is given a weighting of 10%.

[0091] FIG. 8B shows an example chart 850 of a method for determining a single-digit representation of the average number of puffs per capsule, a single-digit representation of the total number of capsules, and a single-digit representation of the total number of flight recorder events.

[0092] In some embodiments, if the average number of puffs or suctions variable 524 per capsule is less than 5, the average number of puffs is assigned the single-digit designator "1." If the average number of puffs or suctions variable 524 per capsule is less than 8, the average number of puffs is assigned the single-digit designator "2." If the average number of puffs or suctions variable 524 per capsule is less than 11.75, the average number of puffs is assigned the single-digit designator "3." If the average number of puffs or suctions variable 524 per capsule is less than 18.25, the average number of puffs is assigned the single-digit designator "4." If the average number of puffs or suctions variable 524 per capsule is 18.25 or greater, the average number of puffs is assigned the single-digit designator "5."

[0093] In some embodiments, if the total number of capsules or capsule variable 522 is less than 16, the total number of capsules is designated with the single-digit designation "1." If the total number of capsules or capsule variable 522 is less than 25, the total number of capsules is designated with the single-digit designation "2." If the total number of capsules or capsule variable 522 is less than 44, the total number of capsules is designated with the single-digit designation "3." If the total number of capsules or capsule variable 522 is less than 62, the total number of capsules is designated with the single-digit designation "4." If the total number of capsules or capsule variable 522 is 62 or greater, the total number of capsules is designated with the single-digit designation "5."

[0094] In some embodiments, if the total number of flight recorder events or the flight recorder events variable 528 is less than 20,000, the total number of flight recorder events is given the single-digit designation "1." If the total number of flight recorder events or the flight recorder events variable 528 is less than 30,000, the total number of flight recorder events is given the single-digit designation "2." If the total number of flight recorder events or the flight recorder events variable 528 is less than 50,000, the total number of flight recorder events is given the single-digit designation "3." If the total number of flight recorder events or the flight recorder events variable 528 is less than 70,000, the total number of flight recorder events is given the single-digit designation "4." If the total number of flight recorder events or the flight recorder events variable 528 is 70,000 or greater, the total number of flight recorder events is given the single-digit designation "5."

[0095] For example, if the suction variable 524 is 9.25, the single-digit representation is "3." If the capsule variable 522 is 62, the single-digit representation is "5." If the flight recorder event variable 528 is 65000, the single-digit representation is "4." Therefore, the single-digit code 602 is calculated by the formula: SDC=ROUND((3*0.40)+(5*0.50)+(4*0.1)). Therefore, SDC=ROUND(4.10), and the single-digit code 602 is "4."

[0096] In some embodiments, there is an additional final check performed by processor 502 to detect abnormal behavior. For example, if suction variable 524 is less than 3.0 and capsule variable 522 is greater than 10, engagement index system 500 overrides the calculations performed by processor 502 to determine single digit code 602 and instead determines that single digit code 602 is "1."

[0097] The chart in Figure 8B is an example of thresholds used to determine single-digit representations of capsule variable 522, suction variable 524, and flight recorder event variable 528. In other embodiments, different thresholds are used to classify a consumer's relationship or engagement with device 100.

[0098] Referring to Figure 9, a method 900 of operating engagement index system 500 is shown. Processor 502 is configured to cause engagement index system 500 to perform method 900 of Figure 9 by executing instructions stored by memory 504. In another exemplary embodiment, processor 502 is an ASIC and is configured to cause engagement index system 500 to perform method 900 of Figure 9. Method 900 begins when a consumer acquires a device, such as device 100. Method 900 proceeds to step 902, where engagement index system 500 monitors usage of device 100.

[0099] In some embodiments, engagement index system 500 monitors the usage of device 100 by monitoring at least the number of capsules used, the number of puffs taken, and the number of flight recorder events. Engagement index system 500 monitors these variables by monitoring capsule variable 522, puff variable 524, and flight recorder event variable 528.

[0100] Method 900 proceeds from step 902 to step 904, where it determines an indicator of engagement with device 100. In some examples, the indicator of engagement with device 100 is an icon displayed by processor 502 on communication screen 136. The indicator of engagement with device 100 is determined based on variables monitored in step 902 to monitor usage of device 100. In some embodiments, the indicator of engagement with device 100 is a one-digit code representative of overall engagement with device 100, such as one-digit code 602. In other embodiments, the indicator of engagement with device 100 is a hexadecimal code, such as hexadecimal code 702. Both one-digit code 602 and hexadecimal code 702 are determined substantially as described above with reference to FIGS. 6-8.

[0101] After the indicator of engagement is determined in step 904, the method 900 proceeds to step 906, where the processor 502 outputs the indicator of engagement determined in step 904. As described above, the indicator of engagement for the device 100 is an icon, such as a single digit code 602 or a hexadecimal code 702, that is output on the communication screen 136 of the device 100.

[0102] In some embodiments, the icon is displayed after a particular interaction with the device 100. For example, the icon is displayed after the control button 138 is pressed, the lid 104 is opened or closed while the control button 138 is pressed, and the control button 138 is released. In some embodiments, the interaction with the device 100 is a different sequence of events that displays either the single digit code 602 or the hexadecimal code 702 on the communication screen 136.

[0103] In some embodiments, device 100 is programmed to display either a single digit code or a hexadecimal code when control button 138 is pressed, lid 104 is opened or closed while control button 138 is pressed, and control button 138 is released.

[0104] 10-12, a process or method for engaging with device 100 to display an icon representing an indication of engagement with device 100 is shown. As shown in FIG. 10, the first step or engagement with device 100 is to press control button 138. Arrow 1002 represents the force of pressing control button 138. In some embodiments, control button 138 is pressed throughout the engagement with device 100 to display an indication of engagement with device 100.

[0105] While control button 138 is pressed, lid 104 of device 100 is opened as represented by arrow 1102. Then, lid 104 of device 100 is closed as represented by arrow 1104. Control button 138 remains pressed while lid 104 is opened and closed.

[0106] After the lid 104 is closed, the control button 138 is released, causing an engagement indicator, such as the single digit code 602 or the hex code 702, to be displayed on the communication screen 136 of the device 100. As shown in Figure 12, an icon is displayed on the communication screen 136. As mentioned above, the device 100 is pre-programmed to display either the single digit code 602 or the hex code 702 after engagement with the device 100.

[0107] In some embodiments, device 100 may additionally include a non-reversible fuse. In some embodiments, the non-reversible fuse is a component of or communicatively coupled to processor 502. If the non-reversible fuse is blown, engagement index system 500 will no longer calculate and / or store capsule variable 522, aspiration variable 524, and flight recorder event variable 528, and will no longer calculate single digit code 602 or hexadecimal code 702.

[0108] The systems, devices, and methods described herein offer significant advantages. Icons describing device 100 engagement metrics can be displayed by consumers, allowing for real-time, accurate feedback regarding the consumer's engagement with device 100. Device 100 engagement metrics also reduce the burden of in-person interviews for consumer research while providing the same or more detailed level of insight into product usage. Device 100 engagement metrics improve consumer research by providing a quantitative measure of device 100 usage, which can be used in conjunction with qualitative statements by consumers to determine a more accurate engagement metric than would be possible without a quantitative measure.

[0109] The appended claims set forth novel and inventive aspects of the subject matter described above, but the claims may also encompass additional subject matter not specifically recited. For example, certain features, elements, or aspects may be omitted from the claims if they are not necessary to distinguish novel and inventive features from those already known to those skilled in the art. Also, features, elements, and aspects described in the context of certain embodiments may be omitted, combined, or substituted with alternative features serving the same, equivalent, or similar purpose without departing from the scope of the invention as defined by the appended claims.

Claims

1. 1. A system configured to output an indicator of engagement with a device, comprising: at least one processor; a memory coupled to the at least one processor for storing instructions; The at least one processor executes the instructions to provide the system with: obtaining information relating to the usage of the device; determining the indicator of engagement with the device based on the usage of the device; A system configured to cause an indication of said engagement to said device to be output.

2. 10. The system of claim 1, The system, wherein the indication of engagement with the device includes a hexadecimal representation.

3. 3. The system of claim 2, The hexadecimal representation includes two columns of five hexadecimal digits.

4. 3. The system of claim 2, The system, wherein the hexadecimal representation encodes at least one of the number of capsules used, the average number of puffs per capsule, the exact number of flight recorder events, or a data integrity check.

5. 3. The system of claim 2, The at least one processor is configured to execute the instructions to cause the device to output an indication of the engagement with the device on a communication screen of the device.

6. 6. The system of claim 5, The at least one processor is configured to execute the instructions and cause the device to output the hexadecimal representation in response to an interaction with the device.

7. 7. The system of claim 6, The system, wherein the relationship to the device includes holding a button on the device, opening a lid of the device while the button is held, closing the lid of the device while the button is held, and releasing the button.

8. 3. The system of claim 2, The system, wherein the last element of the hexadecimal representation is a single digit.

9. 9. The system of claim 8, The single digit represents the overall involvement of the device, system.

10. 10. The system of claim 1, The system, wherein the indication of engagement with the device includes a one-digit code.

11. 11. The system of claim 10, The system, wherein the one-digit code is the last digit of the hexadecimal representation.

12. 11. The system of claim 10, The single-digit code represents an overall involvement with the device.

13. 13. The system of claim 12, The system, wherein the at least one processor is configured to determine the overall engagement with the device based on at least one of the number of capsules used, the average number of puffs per capsule, or the exact number of flight recorder events.

14. 11. The system of claim 10, The at least one processor is configured to execute the instructions and cause the device to output the single-digit code on a communication screen of the device.

15. 15. The system of claim 14, The at least one processor is configured to execute the instructions to cause the device to output the single-digit code on the communication screen of the device in response to an interaction with the device.

16. 16. The system of claim 15, The system, wherein the interaction with the device includes holding a button on the device, opening a lid on the device while the button is held, closing the lid on the device while the button is held, and releasing the button.

17. 11. The system of claim 10, The system, wherein the single-digit code is a number between 1 and 5, inclusive.

18. 10. The system of claim 1, The at least one processor is configured to execute the instructions to cause the indicator of engagement for the device to be adjusted as additional data is collected by the system.

19. 10. The system of claim 1, The at least one processor is configured to execute the instructions to cause the indicator of engagement with the device to be adjusted to a period of use.

20. 20. The system of claim 19, The system, wherein the period of use is at least one of two days of use or seven days of use.

Images