Engagement indication system

Abstract

A system configured to output an indication of engagement with a device. The system includes at least one processor and a memory coupled to the at least one processor. The memory is configured to store instructions. The at least one process is configured to execute the instructions to cause the system to monitor a usage of the device, determine an indication to engage with the device based on the usage of the device, and output an indication to engage with the device.

Description

Technical Field

[0001] The present disclosure relates to heat-not-burn (HNB) aerosol-generating devices and capsules configured to generate aerosols without involving substantial pyrolysis of an aerosol-forming substrate. Background Art

[0002] Some electronic devices are configured to heat the plant material to a temperature sufficient to release the components of the plant material while maintaining the temperature below the ignition point of the plant material to avoid any substantial pyrolysis of the plant material. Such devices may be referred to as aerosol generating devices (e.g., heat-not-burn aerosol generating devices), and the heated plant material may be tobacco. In some cases, the plant material may be introduced directly into the heating chamber of the aerosol generating device. In other cases, the plant material may be pre-packaged in a separate container for ease of insertion into and removal from the aerosol generating device. Summary of the Invention

[0003] Novel and useful systems, devices, and methods for a cooling alarm system for an aerosol generating device are set forth in the appended claims. Illustrative embodiments are also provided to enable one skilled in the art to make and use the claimed subject matter.

[0004] For example, in some exemplary embodiments, a system configured to output an indication of engaging with a device is described. 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 a device, determine an indication of engaging with the device based on the usage of the device, and output the indication of engaging with the device.

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

[0006] In some exemplary embodiments, the indication of device engagement may include a single-digit code. The single-digit code may be the last digit of a hexadecimal digital indicator. In some exemplary embodiments, the single-digit code may indicate full engagement with the device. In some exemplary embodiments, the at least one processor is configured to determine full engagement with the device based on at least one of the following: the number of capsules used, the average number of puffs per capsule, or the exact number of flight recorder events. In some exemplary embodiments, the at least one processor may be configured to execute instructions to cause the device to output the single-digit code on its communication screen. In some exemplary embodiments, the at least one processor is configured to execute instructions to cause the device to output the single-digit code on its communication screen in response to interacting with the device. Interacting with the device may include: pressing and holding a button on the device; opening the device's lid while pressing and holding the button; closing the device's lid while pressing and holding the button; and releasing the button. In some exemplary embodiments, the single-digit code may be a number between one and five.

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

[0008] In some exemplary embodiments, the at least one processor is configured to execute instructions to adjust the indication to engage with the device as the system collects additional data.

[0009] In some exemplary embodiments, the at least one processor is configured to execute instructions to scale the indication to engage with the device based on a duration of use, which may be at least one of two days of use or seven days of use. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The various features and advantages of the non-limiting embodiments herein will become more apparent upon reading the detailed description in conjunction with the accompanying drawings. The drawings are provided for illustrative purposes only and should not be construed as limiting the scope of the claims. Unless expressly noted, the drawings should not be considered to be drawn to scale. Various dimensions in the drawings may be exaggerated for clarity.

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

[0012] Figure 2 is an upper right front perspective view of the device with the cover opened and the device including the capsule.

[0013] Figure 3 is a bottom perspective view of the device.

[0014] Figure 4 is a bottom view of the device.

[0015] Figure 5 is a block diagram of an engagement indication system of an apparatus according to an exemplary embodiment.

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

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

[0018] Figure 7B yes Figure 7A A representation of a hexadecimal number icon shows the conversion of bit codes to hexadecimal number icons.

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

[0020] Figure 8B is another diagram that categorizes consumer data into single-digit icons according to an exemplary embodiment.

[0021] Figure 9 A method of operating an engagement indication system of a device according to an exemplary embodiment is provided.

[0022] Figure 10 is a first step in a method of interacting with a device to display an icon representing an indication of engagement with the device according to an exemplary embodiment.

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

[0024] Figure 12 is a third step of a method of interacting with a device to display an icon representing an indication of engagement with the device according to an exemplary embodiment. DETAILED DESCRIPTION

[0025] Some detailed exemplary embodiments are disclosed herein. However, the specific structural and functional details disclosed herein are merely representative for the purpose of describing the exemplary embodiments. However, the exemplary embodiments may be implemented in many alternative forms and should not be construed as being limited to the exemplary embodiments set forth herein.

[0026] Therefore, although the exemplary embodiments are capable of various modifications and alternative forms, exemplary embodiments thereof are shown by way of example in the drawings and will be described in detail herein. However, it should be understood 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 cover all modifications, equivalents, and alternatives within the scope of the exemplary embodiments. Like reference numerals represent like elements throughout the description of the figures.

[0027] It should be understood that when an element or layer is referred to as being "on," "connected to," "coupled to," or "overlying" another element or layer, the element or layer may be directly on, connected to, coupled to, or overlying the other element or layer, or there may be intermediate elements or layers. Conversely, when an element is referred to as being "directly on," "directly connected to," or "directly coupled to" another element or layer, there are no intermediate elements or layers. Throughout this specification, like reference numerals represent like elements. As used herein, the term "and / or" includes any and all combinations of one or more of the listed related items.

[0028] It should be understood that although the terms first, second, third, etc. can be used in this article to describe various elements, regions, layers and / or parts, these elements, regions, layers and / or parts should not be limited by these terms. These terms are only used to distinguish one element, region, layer or part from another region, layer or part. Therefore, without departing from the teachings of the exemplary embodiments, the first element, first component, first region, first layer or first part discussed below can be referred to as the second element, second region, second layer or second part.

[0029] For ease of description, spatially related terms (e.g., “below,” “beneath,” “lower,” “above,” and “upper,” etc.) may be used herein to describe the relationship of one element or feature to another element or feature shown in the drawings. It should be understood that, in addition to the orientations described in the drawings, spatially related terms are intended to include different orientations of the device in use or operation. For example, if the device in the drawings is turned over, an element described as being “below” or “below” other elements or features will be oriented as being “above” the other elements or features. Thus, the term “below” can include both the orientations of above and below. The device can be oriented in other ways (rotated 90 degrees or in other orientations), and the spatially related descriptors used herein are interpreted accordingly.

[0030] The terms used herein are for the purpose of describing various exemplary embodiments only and are not intended to limit the exemplary embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" are intended to include the plural forms as well. It will also be understood that the terms "includes", "including", "comprises", and / or "comprising" specify the presence of the recited features, integers, steps, operations, and / or elements, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, and / or groups thereof.

[0031] When the term "about" or "substantially" is used in connection with a numerical value in this specification, it is intended that the relevant numerical value includes a manufacturing or operating tolerance (e.g., ±10%) around the numerical value. In addition, when the term "substantially" or "substantially" is used in conjunction with a geometric shape, it is intended that the accuracy of the geometric shape is not required but that the overall shape is within the scope of the present disclosure. In addition, regardless of whether a numerical value or shape is modified to "about," "substantially," or "substantially," it will be understood that these values ​​and shapes should be interpreted as including a manufacturing or operating tolerance (e.g., ±10%) around the numerical value.

[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 embodiments belong. It should also be understood that terms (including those defined in commonly used dictionaries) should be interpreted as having a meaning consistent with their meaning in the relevant technical context and will not be interpreted as idealized or overly formal unless explicitly defined as such herein.

[0033] As used herein, "coupled" includes both detachably coupled and permanently coupled. For example, when the elastic layer and the support layer are detachably coupled to each other, the elastic layer and the support layer can be separated when sufficient force is applied.

[0034] The 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 any other device capable of responding to and / or executing instructions in a defined manner.

[0035] Figures 1 to 4is a diagram of a device 100 according to some exemplary embodiments. In some embodiments, the device 100 may be an aerosol generating device (e.g., a heat-not-burn (HNB) aerosol generating device). Figure 1 , shows a top perspective view of device 100. In some embodiments, the body of device 100 can have a generally oblong or pebble shape. The body of device 100 can include a housing 102 and a lid mechanism or cover 104. Housing 102 can have a first end 106 and a second end 108 opposite first end 106. Cover 104 can have a first end 110 and a second end 112 opposite first end 110. First end 110 of cover 104 can be fixedly coupled to second end 108 of housing 102 at a first point 114 and releasably coupled to second end 108 of housing 102 at a second point 116. First point 114 of housing 102 can be located on a first side 118 of device 100. Second point 116 of housing 102 can be located on a second side 120 of device 100.

[0036] In some exemplary embodiments, the device 100 may further include a mouthpiece 122. In at least some exemplary embodiments, the mouthpiece 122 may include a first end 124 and a second end 126 opposite the first end 124. The second end 126 of the mouthpiece 122 may be coupled to the second end 112 of the lid 104. In some embodiments, the second end 126 of the mouthpiece 122 may be releasably coupled to the second end 112 of the lid 104. In at least one exemplary embodiment, the mouthpiece 122 may have a tapered shape between the first end 124 and the second end 126. For example, the diameter or average length / width dimension of the first end 124 may be smaller than the diameter or average length / width dimension of the second end 126. Towards the first end 124, the taper may have a slight inward curve 128 configured to receive the lips of an adult consumer and improve comfort and experience. In some embodiments, the first end 124 may have an oblong or oval shape and may include one or more outlets 130. For example, the first end 124 may include four outlets 130 so that four or more different areas or quadrants of an adult consumer's mouth can be engaged during use of the device 100. In other embodiments, the mouthpiece 122 may have fewer than four outlets 130, or more than four outlets 130.

[0037] In some exemplary embodiments, the housing 102 may include a consumer interface panel 132 disposed on the second side 120 of the device 100. For example, the consumer interface panel 132 may be an oval-shaped panel extending along the second side 120 of the device 100. The consumer interface panel 132 may include a latch release button 134, a communication screen 136, and / or control buttons 138. For example, in at least some exemplary embodiments, the consumer interface panel 132 may include a communication screen 136 disposed between the latch release button 134 and the control buttons 138. As shown, the latch release button 134 may be disposed toward the second end 108 of the device 100, and the control buttons 138 may be disposed toward the first end 106 of the device 100. The latch release button 134 and the control button 138 may be adult consumer interaction buttons. The latch release button 134 and the control button 138 may have a substantially circular shape with a central depression or indentation configured to guide pressure applied by the adult consumer, but exemplary embodiments are not limited thereto. The control button 138 can turn the device 100 on and off. While only two buttons are shown, it will be appreciated that more or fewer buttons may be provided depending on the available functionality and the desired adult consumer interface.

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

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

[0040] Figure 2Another top perspective view of the device 100 is shown, with the lid 104 in an open configuration. The lid 104 can be fixedly coupled to the housing 102 at a first point 114 via a hinge 202 or other similar connector, which 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 can be a torsion spring. In at least some exemplary embodiments, the housing 102 can include a recess 204 at the first point 114. The recess 204 can be configured to receive a portion of the lid 104, thereby allowing the lid 104 to move easily and smoothly from the open position to the closed position (and vice versa). The recess 204 can have a structure corresponding to a corresponding portion of the lid 104. For example, as shown, the recess 204 can include a substantially curved portion 206 having a generally concave shape that corresponds to the curved portion of the lid 104 having a generally convex shape.

[0041] The lid 104 can be releasably coupled to the housing 102 at the second point 116 by means of a latch 208 or other similar connector that allows the lid 104 to be fixed or secured in a closed position and can be easily released to allow the lid 104 to be moved from the closed position to the open position. In at least one exemplary embodiment, the latch 208 can be coupled to a latch release mechanism (not shown) disposed within the housing. The latch release mechanism can be configured to move the latch 208 from a first, or closed, position to a second, or open position.

[0042] When the cover 104 is in the Figure 2 In the open position shown, the capsule receiving cavity 210 of the housing 102 is exposed. The capsule connector 212 can define the capsule receiving cavity 210 of the housing 102. In some embodiments, the capsule connector 212 can be mounted or otherwise secured to a printed circuit board (PCB) within the housing 102.

[0043] like Figure 2 As shown, the capsule 214 can be received by the capsule receiving cavity 210. In some embodiments not shown herein, a gasket can be provided around the capsule 214 to help secure the capsule 214 in place within the housing 102. The capsule 214 can include a housing 216 configured to accommodate the aerosol-forming substrate and the heater. In some embodiments, the housing 216 can be in the form of a cover, such as a housing or a box sleeve. In some embodiments, the capsule 214 can include a first end cap 217 and a second end cap. The second end cap can be opposite to the first end cap 217 so that when the capsule 214 is received by the capsule receiving cavity 210, the second end cap is disposed within the housing 102.

[0044] As discussed herein, an aerosol-forming substrate or consumable is a material or combination of materials that can produce an aerosol. An aerosol relates to a substance generated or output by the disclosed, claimed apparatus and their equivalents. The material may comprise a compound (e.g., nicotine), wherein an aerosol comprising the compound is produced when the material is heated. The heating may be below the combustion temperature so that the aerosol is produced without involving substantial pyrolysis of the aerosol-forming substrate or substantial production of combustion byproducts (if any). Thus, in an exemplary embodiment, pyrolysis does not occur during the heating and aerosol generation process. In other cases, there may be some pyrolysis and combustion byproducts, but the extent may be considered to be relatively minor and / or merely incidental.

[0045] The aerosol-forming substrate can be a fibrous material. For example, the fibrous material can be a plant material. The fibrous material is configured to release a compound when heated. The compound can be a naturally occurring component in the fibrous material. For example, the fibrous material can be a plant material, for example, tobacco, and the compound released can be nicotine. The term "tobacco" includes: any tobacco plant material, including tobacco leaves, tobacco plugs, reconstituted tobacco, compressed tobacco, shaped tobacco or powdered tobacco and combinations thereof from one or more tobacco plant species (such as Nicotiana rustica and Nicotiana tabacum).

[0046] In some exemplary embodiments, tobacco material can comprise the material from any member of Nicotiana. In addition, tobacco material can comprise the mixture of two or more different tobacco varieties. The example of the tobacco material of operable appropriate type includes, but is not limited to, flue-cured tobacco, Burleigh tobacco, dark tobacco, Maryland tobacco, oriental tobacco, rare tobacco, special tobacco and mixture thereof etc. Tobacco material can provide in any suitable form, and it includes but is not limited to tobacco sheet, processed tobacco material (for example, volume expansion or puffed tobacco), processed tobacco stem (for example, cut-roll or cut puffed tobacco stem), reconstructed tobacco material and mixture thereof etc. In some exemplary embodiments, tobacco material exists with the form of basic dry tobacco substance. In addition, in some instances, tobacco material can mix and / or combine with at least one in propylene glycol, glycerine, its sub-combination or its combination.

[0047] The compound may also be a natural component of a medicinal plant having a medically acceptable therapeutic effect.

[0048] In addition, compound can be or can comprise in addition the additive of the non-natural existence that is subsequently introduced into the fibrous material.In one case, fibrous material can comprise at least one (for example, in the form of gauze) in cotton, polyethylene, polyester, rayon or their combination etc.In another case, fibrous material can be cellulosic material (for example, non-tobacco material).In either case, the compound introduced can comprise nicotine and / or flavoring.Flavoring can be from natural origin, for example plant extract (for example, tobacco extract), and / or from artificial source.In another case, when fibrous material comprises tobacco, compound can be or can comprise in addition one or more flavorings (for example, menthol, mint, vanilla).Therefore, aerosol forms the compound in substrate and can comprise naturally occurring composition and / or the additive that non-natural exists.In this respect, it should be understood that the existing level of the natural component that aerosol forms substrate can be increased by supplementing.For example, the existing level of nicotine in a certain amount of tobacco can be increased by supplementing the extract that contains nicotine.

[0049] The first end cap 217 may include a first opening 218. In some embodiments, the first opening 218 may be a series of openings disposed through the first end cap 217. Similarly, the second end cap may include a second opening, which may be a series of openings in some embodiments. In some embodiments, the first end cap 217 and / or the second end cap may be transparent so as to function as a window configured to allow viewing of the contents / components within the capsule 214 (e.g., the aerosol-forming substrate and / or the heater).

[0050] The capsule receiving cavity 210 can have a base that can be located within the housing 102. In some embodiments, the base can include at least one contact point that can be configured to couple to one or more contact points 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 may not be sufficient to compress the at least one contact point of the base of the capsule receiving cavity 210. Thus, the capsule 214 can simply rest on the exposed pins of the at least one contact point without causing any compression (or any significant compression) of the electrical contact of the at least one contact point. Furthermore, when the lid 104 itself pivots to transition to the closed position, its weight may not cause any significant compression of the electrical contact of the at least one contact point, and can instead simply rest on the capsule 214 in the intermediate, partially open / closed position. In this case, intentional action (e.g., downward force) to close the lid 104 will cause the surface 220 of the lid 104 to press down on the bladder 214 to provide the desired seal and also cause the bladder 214 to compress, thereby fully engaging the electrical contact of at least one contact point.

[0051] Additionally, full closing of the lid 104 can result in engagement with the latch 208, which can maintain the closed position and the desired mechanical / electrical engagement with the capsule 214 until released (e.g., via the latch release button 134). The force required to close the lid 104 can help ensure and / or improve the air / aerosol seal and provide a more robust electrical connection, as well as improve device and thermal efficiency and battery life by reducing or eliminating premature power consumption and / or parasitic heating of the capsule 214.

[0052] The lid 104 can include an interior cavity 222 that can be adapted to receive the housing 102 when the lid is in the closed position. In some embodiments, the interior cavity 222 of the lid 104 can include an impact or engagement member or surface 220 configured to engage the bladder 214 when the lid 104 is pivoted to transition to the closed position. The surface 220 of the lid 104 can include a recessed portion that can correspond to the size and shape of the bladder and / or a resilient material to enhance the interface with the bladder to provide a desired seal. In some embodiments, the lid 104 can also include an opening 224 that can be adapted to receive the second end 126 of the mouthpiece 122. The mouthpiece 122 can include at least one extension 226 that can be received by the opening 224 of the lid 104 to secure the mouthpiece 122 to the lid 104. In some embodiments, the lid 104 can also include a protrusion that can be configured to couple with a recessed portion 228 of the housing 102. The protrusion may fit within the recess 228 when the lid 104 is coupled to the housing 102 in the closed position.

[0053] Reference Figure 3, showing a bottom perspective view of the device 100. In some embodiments, the housing 102 may define a port or charging connector 250. The charging connector may be defined or disposed at the first end 106 of the housing 102. The charging connector 250 may be configured to receive current from an external power source (e.g., via a USB / mini-USB cable) to charge a power source within the device 100. In some embodiments, a protective grille 252 is disposed around the charging connector 250. The protective grille 252 may be configured to help reduce or prevent the ingress of debris and / or inadvertent obstruction of incoming airflow. For example, the protective grille 252 may define a plurality of apertures 254 along its length or path. As shown, the protective grille 252 may have an annular form surrounding the charging connector 250. In this regard, the apertures 254 may also be arranged (e.g., in a series arrangement) around the charging connector 250. Each aperture 254 may have an oval or circular shape, but is not limited thereto. In at least one exemplary embodiment, the protective grille 252 may comprise an approved food contact material. For example, the protective grille 252 may include plastic, metal (eg, stainless steel, aluminum), or any combination thereof. In at least one exemplary embodiment, the surface of the protective grille 252 may be coated with, for example, a thin layer of plastic and / or anodizing.

[0054] Apertures 254 in protective grille 252 can serve as an inlet through which air is drawn into device 100. During operation of device 100, ambient air entering through apertures 254 in protective grille 252 surrounding charging connector 250 converges to form a combined flow, which then travels to capsule 214. For example, apertures 254 can be in fluid communication with capsule-receiving cavity 210. In at least one exemplary embodiment, air can be drawn from apertures 254 and through capsule-receiving cavity 210. For example, air can pass through capsule 214 received by capsule-receiving cavity 210 and be discharged from mouthpiece 122.

[0055] Reference Figure 4 , showing a bottom view of the device 100. In some embodiments, the charging connector 250 can be a component that defines a cavity 256 having a protrusion 258 therein. In at least one exemplary embodiment, the protrusion 258 does not extend beyond the edge of the cavity 256. In addition, the charging connector 250 can also be configured to send data to and / or receive data from another aerosol-generating device (e.g., a heat-not-burn (HNB) aerosol-generating device) and / or other electronic devices (e.g., a phone, tablet, and computer, etc.) (e.g., via a USB / mini-USB cable). In at least one embodiment, the device 100 can alternatively or additionally be configured to communicate wirelessly with such other aerosol-generating devices and / or electronic devices (e.g., via Bluetooth).

[0056] As should be understood, the device 100 and the capsule 214 include additional components (e.g., a heater and an internal air flow path), for example, as described in attorney docket No. 24000NV-000847-US, filed on September 19, 2022, with application number 17 / 947,436, entitled “HEAT-NOT-BURN (HNB) AEROSOL-GENERATING DEVICES AND CAPSULES,” the entire contents of which are incorporated herein by reference.

[0057] Reference Figure 5 , shows a block diagram of an engagement indication system 500 of the device 100 according to an exemplary embodiment. In some embodiments, the engagement indication system 500 can be configured to monitor usage of the device 100 to determine engagement of the device 100 by a consumer. The engagement indication system 500 can also be configured to output an indication of engagement with the device 100. In some embodiments, the engagement indication of the device 100 can provide an indication of at least one of the following: the number of capsules used or heated, the average number of puffs per capsule, the accurate number of flight recorder events, and / or a data integrity check of the device 100.

[0058] Engagement indication system 500 may include processor 502, memory 504, control buttons 138, mechanism detection switch 508, power supply 510, communication screen 136, heater 512, airflow sensor 514, charging connection 516, temperature sensor 518, and battery monitoring system 520. In some embodiments, memory 504 may include capsule variables 522, puff variables 524, flight recorder event log 526, and flight recorder event variables 528. Processor 502 may include timer 530. In other embodiments, capsule variables 522, puff variables 524, flight recorder event log 526, and flight recorder event variables 528 may be stored in processor 502, such as in a local memory of processor 502, and timer 530 may be executed using instructions stored in processor 504. In some embodiments, processor 502 may include memory 504. Processor 502 may communicate with memory 504 , control buttons 138 , mechanism detection switch 508 , power source 510 , communication screen 136 , heater 512 , air flow sensor 514 , charging connection 516 , temperature sensor 518 , and battery monitoring system 520 .

[0059] The processor 502 may be hardware including logic circuits, a hardware / software combination that can be 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 device) to execute software or instructions stored in the memory 504. The software may be embodied as program code that includes instructions for executing and / or controlling any or all operations described herein as being performed by the processor 502.

[0060] In other exemplary embodiments, other processing circuitry and / or control circuitry may be used.

[0061] Memory 504 is illustrated as being external to processor 502, but in some exemplary embodiments, memory 504 may be located on processor 502. Memory 504 may describe any of the terms "storage medium," "computer-readable storage medium," or "non-volatile computer-readable storage medium," and may represent one or more devices for storing data, including read-only 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" may include, but is not limited to, portable or fixed storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instructions and / or data.

[0062] Capsule variable 522 may be a counter indicating the number of capsules used. When device 100 is new and has not yet been used by a consumer, capsule variable 522 may be set to zero. Each time a capsule is detected, capsule variable 522 may be incremented by one. Device 100 may detect a capsule when the capsule has been heated for at least 10 seconds. In some embodiments, when heater 512 is powered on, processor 502 may start timer 530. Once timer 530 reaches 10 seconds, capsule variable 522 may be incremented by one.

[0063] Puff variable 524 can be a counter representing the number of puffs. When a session ends, puff variable 524 can be set to zero so that each time a capsule is activated, puff variable 524 can measure the number of puffs taken by the consumer. Puff variable 524 can be incremented by one each time a puff is detected. Puffs can be detected when a consumer places their mouth on mouthpiece 122 of device 100 and applies negative pressure through mouthpiece 122. In some embodiments, puff variable 524 can be configured to store the number of puffs taken for each capsule and to store an average number of puffs taken for each capsule. In some embodiments, processor 502 and / or memory 504 can be configured to calculate an average number of puffs taken for each capsule. In some embodiments, the average number of puffs taken for each capsule can be updated each time a capsule is inserted into device 100 and activated as described above.

[0064] The flight recorder event log 526 can be configured to record events for the device 100. For example, the flight recorder event log 526 can record when the device 100 is inserted into and / or removed from the charger, when the lid 104 is opened and / or closed, when the capsule is inserted into the device 100, when a session begins and / or ends, and when the control button 138 and / or the latch release button 134 are pressed. The following table lists other events that can be recorded in the flight recorder event log 526. In some embodiments, the flight recorder event log 526 can be configured to record over one hundred different interactions with the device 100. The flight recorder event variable 528 can be a counter representing the number of events listed in the flight recorder event log 526. The flight recorder event variable 528 can be incremented by one each time a new event is added to the flight recorder event log 526.

[0065]

[0066]

[0067]

[0068]

[0069] Figure 1 : Events recorded in the flight recorder event log

[0070] In some embodiments, capsule variables 522, puff variables 524, flight recorder event log 526, and flight recorder event variables 528 can be stored in local memory, which can be part of memory 504 or processor 502. In some embodiments, because these indicators are stored in local memory, they are retained even if the battery is fully discharged. In addition, capsule variables 522, puff variables 524, flight recorder event log 526, and flight recorder event variables 528 cannot be reset to zero unless the device 100 is reset to a factory default state. In some embodiments, the device 100 can be reset to a factory default state at the beginning of a device research session.

[0071] The control button 138 can be configured to generate a signal indicating that the consumer has switched the device 100 to an "on" state (if the device 100 was previously in an "off" state) or an "off" state (if the device 100 was previously in an "on" state). Additionally, as part of a series of interactions with the device 100, the control button 138 can be pressed to display a message on the communication screen 136. For example, the consumer can press the control button 138 and complete other interactions with the device 100 to display an indication on the communication screen 136 that the consumer is engaged with the device 100.

[0072] The mechanism detection switch 508 can be configured to generate a signal indicating that the lid mechanism (e.g., lid 104) of the device 100 has been opened. The mechanism detection switch 508 can be a push button switch, a toggle button, a capacitive sensor, an infrared sensor, a magnetic detection sensor (e.g., a Hall Effect sensor), or other element configured to communicate with the processor 502 to indicate that the lid 104 of the device 100 has been opened. When the lid 104 of the device 100 is opened, any ongoing session of the device 100 may end. The mechanism detection switch 508 can be configured to generate a signal indicating that the lid 104 has been opened when the latch release mechanism of the device 100 releases the latch 208. Additionally or alternatively, the mechanism detection switch 508 can be coupled to the latch release button 134 and can generate a signal indicating that the lid 104 of the device 100 has been opened when the latch release button 134 is pressed. More specifically, the mechanism detection switch 508 can be positioned within the recess 228 such that the mechanism detection switch 508 is actuated when the lid 104 of the device 100 is closed.

[0073] In some embodiments, the housing 102 of the device 100 may enclose or house a power source 510. The power source 510 may include one or more batteries, such as a rechargeable dual-battery device, a lithium-ion battery, and / or a fuel cell. The power source 510 may be configured to receive current supplied to the device 100 via a port, thereby charging the power source 510. When the charge level of the power source 510 falls below a predetermined threshold, the battery monitoring system 520 may generate a signal indicating that the device 100 has entered a low-battery state.

[0074] The communication screen 136 may display information related to the device 100. The communication screen 136 may display one or more icons for conveying information related to the device 100. For example, the communication screen 136 may display one or more engagement indicator icons. In some embodiments, the engagement indicator icon may be a single-digit code or a hexadecimal digit code.

[0075] The heater 512 can be housed within the device 100 and can be configured to heat the capsule 214 of the device 100. In some embodiments, the heater 512 can be an element of, or can be coupled to one or more of, a heating voltage measurement circuit, a heating current measurement circuit, and / or a compensation measurement circuit, substantially as described in U.S. application Ser. No. 17 / 151,409, filed on Jan. 18, 2021, and entitled “HEAT-NOT-BURN (HNB) AEROSOL-GENERATING DEVICES INCLUDING INTRA-DRAWHEATER CONTROL, AND METHODS OF CONTROLLING A HEATER,” the disclosure of which is incorporated herein by reference in its entirety.

[0076] Airflow sensor 514 can be configured to detect and / or measure characteristics of airflow through device 100. For example, airflow sensor 514 can be configured to detect and / or measure characteristics of airflow through device 100. For example, airflow sensor 514 can be configured to detect when air is flowing through device 100. In at least one exemplary embodiment, airflow sensor 514 can be a microelectromechanical system (MEMS) flow or pressure sensor or another type of sensor configured to measure airflow, such as a hot-wire anemometer. In other embodiments, airflow sensor 514 can be another known sensor. Airflow sensor 514 can operate as a puff sensor by detecting a puff with a flow rate value greater than or equal to approximately 1 mL / s and terminating the puff when the flow rate value subsequently drops to approximately 0 mL / s. In one exemplary embodiment, airflow sensor 514 can be a differential pressure sensor based on a MEMS flow sensor, where the differential pressure (in Pascals) is converted to an instantaneous flow reading (in mL / s) using a curve-fit calibration function or a lookup table (for each flow value of the differential pressure reading). In another exemplary embodiment, the flow sensor can be a capacitive pressure drop sensor.

[0077] In some embodiments, the airflow sensor 514 can be communicatively coupled to the processor 502 such that the processor 502 is configured to measure the length of time that airflow flows through the device 100. It should be understood that while the airflow sensor 514 may be said to detect a puff, it may be that the processor 502 detects a signal received from the airflow sensor 514 that detects that a puff has been taken. In some embodiments, a puff may be detected when negative pressure is detected through the mouthpiece 122 of the device 100.

[0078] Charging connection 516 can be configured to generate a signal indicating that device 100 is connected to a charger. In some embodiments, housing 102 of device 100 can include a charging connector or port, such as charging connector 250. For example, the port can be defined / disposed in first end 106 of housing 102. The port can be configured to receive current from an external power source (e.g., via a USB / mini-USB cable) to charge a power source (e.g., power source 510) within device 100. Charging connection 516 can be configured to detect when the port of device 100 is receiving current.

[0079] The temperature sensor 518 can be configured to measure the temperature of the device 100. In some embodiments, the temperature sensor 518 can be a thermistor or a thermocouple. More specifically, the temperature sensor 518 can be disposed near the capsule 214 of the device 100 and can be configured to measure the temperature of the area near the capsule 214 of the device 100 to determine when the capsule 214 can be removed from the device 100.

[0080] Battery monitoring system 520 may be configured to generate a signal indicating that device 100 has entered a low-battery state.

[0081] Reference Figure 6 , a single-digit code 602 is shown. The processor 502 may display the single-digit code 602 on the communication screen 136 as an output of an indicator of engagement with the device. The single-digit code 602 may represent an overall indication of engagement with the device 100. In some embodiments, the single-digit code 602 may be scaled 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 another duration. For example, the single-digit code 602 may be a number from one (1) to five (5). The lower the number, the lower the level of engagement of the consumer with the device 100. For example, 1 represents a low level of engagement, 5 represents a high level of engagement, and 3 represents an average level of engagement. The processor 502 may determine the single-digit code based on at least the capsule variable 522, the puff variable 524, and the flight recorder event variable 528. In some embodiments, other indicators may be monitored and used to determine the single-digit code 602.

[0082] Reference Figure 7A , a hexadecimal digital code 702 is shown. The hexadecimal digital code 702 can be displayed by the processor 502 on the communication screen 136 as an output of an indicator engaged with the device. The hexadecimal digital code 702 can be a ten-digit hexadecimal digital code. In some embodiments, the hexadecimal digital code 702 can be displayed as two rows of five elements each, such as a first row 704 and a second row 706. Each element can be a letter from A to F, or a number from zero (0) to nine (9). Each element of the hexadecimal digital code 702 can represent an indicator related to the use of the device 100. In some embodiments, the hexadecimal digital code 702 can be scaled according to the usage time of the device 100. For example, the usage time can be two days of use, seven days of use, or other length of time. In some embodiments, the capsule variable 522, the puff variable 524, and the flight recorder event variable 528 can be represented by elements of the hexadecimal digital code, respectively, or can be represented by a single element or two elements.

[0083] In some embodiments, any of the first nine elements of hexadecimal code 702 may represent capsule variable 522, puff variable 524, and flight recorder event variable 528. Additionally or alternatively, the first nine elements of hexadecimal code 702 may be used to encode additional information about device 100.

[0084] In some embodiments, one or more elements of hexadecimal digital code 702 may be or may represent capsule variable 522. In some embodiments, the elements of hexadecimal digital code 702 representing capsule variable 522 may be a scaled or encoded representation of capsule variable 522, which may be decoded to determine the total number of capsules used by device 100. In some embodiments, one or more elements of hexadecimal digital code 702 may be or may represent flight recorder event variable 528. In some embodiments, the elements of hexadecimal digital code 702 representing flight recorder event variable 528 may be a scaled or encoded representation of flight recorder event variable 528, which may 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 hexadecimal digital code 702 may be or may represent the average number of puffs per capsule represented by puff variable 524. In some embodiments, the elements of hexadecimal digital code 702 representing puff variable 524 may be a scaled or encoded representation of puff variable 524, which may be decoded to determine the average number of puffs per capsule.

[0085] In some embodiments, one or more elements of the hexadecimal digital code 702 may be a data integrity check value, such as a checksum. In some embodiments, the data integrity check value may be a binary value that may indicate whether the data is of good quality. If the data is corrupted, the data may be considered to be of poor quality, or there may be a problem with one or more indicators measured by the engagement indication system 500. In other embodiments, the data integrity check value may be encoded into multiple elements of the hexadecimal digital code 702. The data integrity check or checksum may be a data redundancy check that can be used as a pass / fail feature to determine whether the consumer has correctly interpreted and / or read the hexadecimal digital code 702. In some embodiments, the checksum may be a standard cyclic redundancy check.

[0086] In some embodiments, the last element of the hexadecimal digital code may be an overall indicator of engagement with the device 100. The last element may be a number between 1 and 5, 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 digital code may be the number indicated above with reference to Figure 6 A one-digit code describing 602.

[0087] Reference Figure 7BThe hexadecimal code 702 can be calculated or determined based on 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 activated 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 number 754 associated with the device 100 can be stored in the 40-bit code. In some embodiments, the overall indicator or summary number 754 associated with the device can be a local summary number and can be stored in bits 0-3 of the 40-bit code. The flight recorder event variable 528 can be stored in bits 4-12 of the 40-bit code. In some embodiments, the flight recorder event variable 528 can be stored at 10,000 times resolution and can be rounded up so that the value of the flight recorder event variable 528, when stored in the 40-bit code, ranges from 10,000 to 511,000. Capsule variable 522 may be stored in bits 13-24 of the 40-bit code. In some embodiments, the value range of capsule variable 522 is between 0 and 4095. Puff variable 524 may be stored in bits 25-31 of the 40-bit code. In some embodiments, puff variable 524 may be stored at 0.25x resolution and have a value range of between 0 and 31.75. A data integrity check or checksum 752 may be stored in bits 32-39 of the 40-bit code. In some embodiments, puff variable 524, capsule variable 522, flight recorder event variable 528, and summary number 754 may be included in checksum 752.

[0088] In some embodiments, the capsule variable 522, the puff variable 524, and the flight recorder event variable 528 can be packed into a 32-bit word as described above. In some embodiments, the capsule variable 522, the puff variable 524, and the flight recorder event variable 528 in this 32-bit word can be XORed with a 28-bit constant "magic number" 756. The bits comprising the capsule variable 522, the puff variable 524, and the flight recorder event variable 528 can be XORed with the magic number 756 to create ciphertext. The ciphertext can encrypt the 4-31 bit fields of the 32-bit code. For example, this can help prevent misreading of the capsule variable 522, the puff variable 524, and the flight recorder event variable 528. Once the capsule variable 522, the puff variable 524, and the flight recorder event variable 528 are XORed with the magic number 756, the digest number 754 is calculated and added to bits 0-3 of the 40-bit code, and then the 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, the hexadecimal code 702 can be determined.

[0089] In some embodiments, the hexadecimal code 702 can be replaced by a machine-readable code (e.g., a QR code). The machine-readable code can be scanned by a device, such as a smartphone, which can be configured to interpret and / or display one or more indicators encoded by the machine-readable code. In some embodiments, when the machine-readable code is scanned, the indicator encoded by the machine-readable code can also be sent to a research institution or other remote location, such as by email.

[0090] Figure 8A A chart 800 is shown showing an exemplary distribution of consumer data corresponding to a single-digit engagement indicator (e.g., single-digit code 602). Chart 800 can organize data collected from one or more consumer studies, including the number of capsules used with the device 100, the number of flight recorder events for the device 100, and the average number of puffs per capsule. These metrics can be analyzed and categorized or organized and scored based on the consumer's level of engagement with the device 100. These metrics can be scaled and / or organized based on duration of use, as described above. By scaling or organizing the data based on duration of use of the device 100, consumers who used the device 100 for a certain number of days can be compared to other consumers who used the device 100 for the same number of days. This allows the data to be organized and analyzed to understand the consumer's interaction with the device 100.

[0091] In some embodiments, if the number of capsules used by the consumer is at or below the 20th percentile of the consumer data, the total number of flight recorder events is at or below the 20th percentile of the consumer data, or the average number of puffs per capsule is at or below the 20th percentile of the consumer data, the engagement indication may be considered low and may be scored as a "1." If the number of capsules used by the consumer is between the 21st and 39th percentiles of the consumer data, the total number of flight recorder events is between the 21st and 39th percentiles of the consumer data, or the average number of puffs per capsule is between the 21st and 39th percentiles of the consumer data, the engagement indication may be scored as a "2." If the number of capsules used by the consumer is between the 40th and 60th percentiles of the consumer data, the total number of flight recorder events is between the 40th and 60th percentiles of the consumer data, or the average number of puffs per capsule is between the 40th and 60th percentiles of the consumer data, the engagement indication may be considered average and may be scored as a "3." If the number of capsules used by the consumer is between the 600th and 79th percentiles of the consumer data, the total number of flight recorder events is between the 600th and 79th percentiles of the consumer data, or the average number of puffs per capsule is between the 600th and 79th percentiles of the consumer data, then the engagement indicator may be scored as a "4." If the number of capsules used by the consumer is at or above the 80th percentile of the consumer data, the total number of flight recorder events is at or above the 80th percentile of the consumer data, or the average number of puffs per capsule is at or above the 80th percentile of the consumer data, then the engagement indicator may be considered average, may be considered high, and may be scored as a "5."

[0092] In other embodiments, the percentages may be adjusted, other metrics may influence the engagement indication, and / or certain metrics may be weighted to have a greater or lesser impact on the engagement indication with the device 100. For example, in some embodiments, if any of the aforementioned metrics is below the tenth percentile of the consumer data, the engagement indication may be considered low and may be scored as "1." Additionally, as additional consumer data is acquired, the engagement indication with the device 100 may be updated and / or adjusted. For example, as additional consumer data is acquired, the single-digit code 602 and / or the hexadecimal digit code 702 may be adjusted and updated.

[0093] In some embodiments, processor 502 may calculate the one-digit code 602 using the following formula: SDC = ROUND((P*0.40) + (C*0.50) + (E*0.1)). SDC may be the one-digit code 602, where P may be the one-digit representation of the average number of puffs per capsule or the puff variable 524, C may be the one-digit representation of the total number of capsules or the capsule variable 522, and E may be the one-digit representation of the flight recorder event variable 528 or the total number of events recorded in the flight recorder event log 526. As shown in the above formula, the one-digit representation of the average number of puffs per capsule may be assigned a weight of 40% of the one-digit code 602, the one-digit representation of the total number of capsules may be assigned a weight of 50%, and the one-digit representation of the total number of flight recorder events may be assigned a weight of 10%.

[0094] Figure 8B An exemplary graph 850 illustrates how a one-digit representation of the average number of puffs per balloon, a one-digit representation of the total number of balloons, and a one-digit representation of the total number of flight recorder events are determined.

[0095] In some embodiments, if the average number of puffs per balloon or the puff variable 524 is less than 5, the average number of puffs may be assigned a single digit to represent "1". If the average number of puffs per balloon or the puff variable 524 is less than 8, the average number of puffs may be assigned a single digit to represent "2". If the average number of puffs per balloon or the puff variable 524 is less than 11.75, the average number of puffs may be assigned a single digit to represent "3". If the average number of puffs per balloon or the puff variable 524 is less than 18.25, the average number of puffs may be assigned a single digit to represent "4". If the average number of puffs per balloon or the puff variable 524 is greater than or equal to 18.25, the average number of puffs may be assigned a single digit to represent "5".

[0096] In some embodiments, if the total number of capsules or capsule variable 522 is less than 16, the total number of capsules may be assigned a single digit representing "1". If the total number of capsules or capsule variable 522 is less than 25, the total number of capsules may be assigned a single digit representing "2". If the total number of capsules or capsule variable 522 is less than 44, the total number of capsules may be assigned a single digit representing "3". If the total number of capsules or capsule variable 522 is less than 62, the total number of capsules may be assigned a single digit representing "4". If the total number of capsules or capsule variable 522 is greater than or equal to 62, the total number of capsules may be assigned a single digit representing "5".

[0097] In some embodiments, if the total number of flight recorder events or the flight recorder event variable 528 is less than 20,000, the total number of flight recorder events may be assigned a single digit representing "1". If the total number of flight recorder events or the flight recorder event variable 528 is less than 30,000, the total number of flight recorder events may be assigned a single digit representing "2". If the total number of flight recorder events or the flight recorder event variable 528 is less than 50,000, the total number of flight recorder events may be assigned a single digit representing "3". If the total number of flight recorder events or the flight recorder event variable 528 is less than 70,000, the total number of flight recorder events may be assigned a single digit representing "4". If the total number of flight recorder events or the flight recorder event variable 528 is greater than or equal to 70,000, the total number of flight recorder events may be assigned a single digit representing "5".

[0098] For example, if the puff variable 524 is 9.25, the one-digit representation may be "3." If the capsule variable 522 is 62, the one-digit representation may be "5." If the flight recorder event variable 528 is 65000, the one-digit representation may be "4." Therefore, the one-digit code 602 may be calculated using the formula SDC=ROUND((3*0.40)+(5*0.50)+(4*0.1)). Therefore, SDC=ROUND(4.10), so the one-digit code 602 is "4."

[0099] In some embodiments, the processor 502 may perform additional final checks to detect abnormal behavior. For example, if the aspiration variable 524 is less than 3.0 and the balloon variable 522 is greater than 10, the engagement indication system 500 may override the calculation performed by the processor 502 and instead determine that the single-digit code 602 is "1."

[0100] Figure 8B The graph of is one example of thresholds for determining the one-digit representations of the capsule variable 522, the puff variable 524, and the flight recorder event variable 528. In other embodiments, the thresholds may be different but may be used to categorize a consumer's interaction or engagement with the device 100.

[0101] Reference Figure 9 , a method 900 of operating the engagement indication system 500 is shown. The processor 502 is configured to cause the engagement indication system 500 to perform by executing instructions stored by the memory 504. Figure 9 In other exemplary embodiments, the processor 502 may be an ASIC and configured to cause the engagement indication system 500 to execute Figure 9Method 900. Once a consumer obtains a device (e.g., device 100), method 900 can begin. Method 900 can proceed to step 902, where engagement indication system 500 monitors usage of device 100.

[0102] In some embodiments, engagement indication system 500 can monitor the use of device 100 by monitoring at least the number of balloons used, the number of puffs, and the number of flight recorder events. Engagement indication system 500 can monitor these indicators by monitoring balloon variable 522, puff variable 524, and flight recorder event variable 528.

[0103] Method 900 may proceed from step 902 to step 904 to determine an indication of engagement with device 100. In some examples, the indication of engagement with device 100 may be an icon that may be displayed by processor 502 on communication screen 136. The indication of engagement with device 100 may be determined based on the metrics monitored in step 902 for monitoring usage of device 100. In some embodiments, the indication of engagement with device 100 may be a one-digit code representing overall engagement with device 100, such as one-digit code 602. In other embodiments, the indication of engagement with device 100 may be a hexadecimal code, such as hexadecimal code 702. Both one-digit code 602 and hexadecimal code 702 may be substantially as described above with reference to FIG. Figure 6 Determined in the manner described in FIG8 .

[0104] After determining the engagement indication at step 904, method 900 may proceed to step 906, where processor 502 outputs the engagement indication determined at step 904. As described above, the engagement indication with device 100 may be an icon, such as a single-digit code 602 or a hexadecimal digit code 702 that may be output on the communication screen 136 of device 100.

[0105] In some embodiments, the icon may be displayed after a specific interaction with the device 100. For example, the icon may be displayed after pressing the control button 138, opening and closing the lid 104 while pressing the control button 138, and releasing the control button 138. In some embodiments, the interaction with the device 100 may be a different sequence of events that may display the single-digit code 602 or the hexadecimal digit code 702 on the communication screen 136.

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

[0107] Reference Figures 10 to 12 , shows a process or method of interacting with the device 100 to display an icon representing an indication of engagement with the device 100. Figure 10 As shown, the first step in device engagement may be pressing control button 138. Arrow 1002 may indicate the force with which control button 138 is pressed. In some embodiments, control button 138 may be pressed throughout interaction with device 100 in order to display an indication of engagement with device 100.

[0108] When the control button 138 is pressed, the lid 104 of the device 100 may open as indicated by arrow 1102. The lid 104 of the device 100 may then close as indicated by arrow 1104. The control button 138 may remain pressed as the lid 104 opens and closes.

[0109] After the lid 104 is closed, the control button 138 may be released, which causes an engagement indication (e.g., a single digit code 602 or a hexadecimal code 702) to appear on the communication screen 136 of the device 100. Figure 12 As shown, the icon may appear on the communication screen 136. As described above, the device 100 may be preprogrammed to display a single digit code 602 or a hexadecimal code 702 after such interaction with the device 100.

[0110] In some embodiments, the apparatus 100 may further include an irreversible fuse. In some embodiments, the irreversible fuse may be a component of the processor 502 or may be communicatively coupled to the processor 502. When the irreversible fuse is blown, the engagement indication system 500 no longer calculates and / or stores the capsule variable 522, the puff variable 524, and the flight recorder event variable 528, and no longer calculates the single-digit code 602 or the hexadecimal code 702.

[0111] The systems, devices, and methods described herein can provide significant advantages. A consumer can display an icon depicting an indication of engagement with the device 100 and be provided with real-time, accurate feedback on the consumer's engagement with the device 100. Indications of engagement with the device 100 can also reduce the burden of in-person interviews for consumer research while providing the same or more detailed insights into product usage. Indications of engagement with the device 100 can improve consumer research by providing a quantitative measure of usage of the device 100 that can be used in conjunction with qualitative statements from consumers to determine more accurate indications of engagement than without the quantitative measure.

[0112] The appended claims set forth the novel and inventive aspects of the subject matter described above, but the claims may also cover other 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 the novel and inventive features from features already known to those skilled in the art. Features, elements, and aspects described in the context of certain embodiments may also be omitted, combined, or replaced 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. A system configured to output an indication of engagement with a device, the system comprising: at least one processor; and a memory coupled to the at least one processor and storing instructions, The at least one processor is configured to execute the instructions to cause the system to: obtaining information related to usage of the device, determining an indication for engagement with the device based on usage of the device, and An indication of engagement with the device is output.

2. The system according to claim 1, wherein: The indication of engagement with the device includes a hexadecimal numeric indicator.

3. The system according to claim 2, wherein: The hexadecimal number indicator includes two rows of five hexadecimal numbers.

4. The system according to claim 2, wherein: The hexadecimal digital indicator encodes 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.

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

6. The system according to claim 5, wherein: The at least one processor is configured to execute the instructions to cause the apparatus to output the hexadecimal number indicator in response to interacting with the apparatus.

7. The system according to claim 6, wherein: The interacting with the device includes: pressing and holding a button of the device; opening a cover of the device while pressing and holding the button; closing the cover of the device while pressing and holding the button; and releasing the button.

8. The system according to claim 2, wherein: The last element of the hexadecimal number indicator is a single digit.

9. The system according to claim 8, wherein: The single digit represents the integral engagement with the device.

10. The system according to claim 1, wherein: The indication of engagement with the device comprises a one-digit code.

11. The system according to claim 10, wherein: The one-digit code is the last digit of the hexadecimal digital indicator.

12. The system according to claim 10, wherein: The one-digit code represents the integral engagement with the device.

13. The system according to claim 12, wherein: The at least one processor is configured to determine integral engagement with the device based on at least one of a number of balloons used, an average number of puffs per balloon, or an exact number of flight recorder events.

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

15. The system according to claim 14, wherein: The at least one processor is configured to execute the instructions to cause the device to output the one-digit code on a communication screen of the device in response to interacting with the device.

16. The system according to claim 15, wherein: The interacting with the device includes: pressing and holding a button of the device; opening a cover of the device while pressing and holding the button; closing the cover of the device while pressing and holding the button; and releasing the button.

17. The system according to claim 10, wherein: The one-digit code is a number between one and five.

18. The system according to claim 1, wherein: The at least one processor is configured to execute the instructions to adjust the indication to engage the device as the system collects additional data.

19. The system according to claim 1, wherein: The at least one processor is configured to execute the instructions to scale the indication of engagement with the device according to a duration of use.

20. The system of claim 19, wherein: The usage duration is at least one of two days or seven days.

Images