Nicotine electronic vaping device with automatic shutoff function

Abstract

The nicotine electronic vaporizing device includes a nicotine pod assembly (300) and a device body (100). The nicotine pod assembly (300) includes a nicotine reservoir for holding a nicotine pre-vapor formulation and a heater (336) configured to vaporize the nicotine pre-vapor formulation drawn from the nicotine reservoir. The device body (100) is configured to engage the nicotine pod assembly (300) and includes a controller (2105). The controller (2105) is configured to cause the device body (100) to detect a fault event in the nicotine electronic vaporizing device, classify the fault event as one of a plurality of types of fault event, and perform at least one resulting action based on the classification of the fault event.

Description

TECHNICAL FIELD

[0001] One or more exemplary embodiments relate to a nicotine electronic vaping (nicotine e-vaping) device. BACKGROUND ART

[0002] A nicotine electronic vaping device (or nicotine e-vaping device) includes a heater that vaporizes a nicotine pre-vaping formulation to generate nicotine vapor. The nicotine e-vaping device may include a number of nicotine e-vaping elements, including a power source, a nicotine cartridge or a nicotine e-vaping tank including the heater, and a nicotine reservoir capable of holding nicotine pre-vaping formulation material. SUMMARY OF THE INVENTION

[0003] At least one exemplary embodiment provides a nicotine electronic vaping device including a nicotine pod assembly and a device main body. The nicotine pod assembly includes a nicotine reservoir for holding a nicotine pre-vaping formulation, and a heater configured to vaporize the nicotine pre-vaping formulation drawn from the nicotine reservoir. The device main body is configured to engage with the nicotine pod assembly and includes a control device. The control device is configured to detect a fault event in the nicotine electronic vaping device, classify the fault event as one of a plurality of types of fault events, and perform at least one resulting action based on the classification of the fault event.

[0004] According to at least some exemplary embodiments, the fault event may be one of a normal event, a soft fault pod event, a hard fault pod event, a soft fault device event, or a hard fault device event. The soft fault pod event and the hard fault pod event may be an abnormal condition in the nicotine pod assembly, and the soft fault device event and the hard fault device event may be an abnormal condition in the device main body.

[0005] At least one resulting action includes an automatic shut-off, heater shut-off, vaping shut-off, charging stop, or a combination thereof.

[0006] The device body may further include at least one vapor indicator configured to output a message indicating that a fault event has occurred.

[0007] The device itself may further include memory.

[0008] The control device may be configured to perform at least one resulting action by disabling power to the heater, recording the occurrence of a fault event in memory, and causing at least one vapor indicator to output a message indicating that a fault event has occurred.

[0009] The control device may be configured to perform at least one resulting action by disabling the vaping function in the nicotine electronic vaping device, recording the occurrence of a malfunction event in memory, and causing at least one vapor indicator to output a message indicating that a malfunction event has occurred.

[0010] The control device may be configured to detect the detachment of the nicotine pod assembly from the device body and, in response to the detection of the detachment of the nicotine pod assembly from the device body, enable the vaping function in the nicotine electronic vaping device.

[0011] The control device may be configured to cause the main unit to enter sleep mode in response to a fault event and in response to determining that no corrective action has occurred.

[0012] The control device may be configured to perform at least one resulting action by activating an automatic shut-off operation that puts the nicotine electronic vaping device into sleep mode, recording the occurrence of a malfunction in memory, and causing at least one vapor indicator to output a message indicating that a malfunction has occurred.

[0013] The control device may be configured to perform at least one resulting action by disabling the vaping function, charging operation, or both the vaping function and charging operation in a nicotine electronic vaping device, recording the occurrence of a fault event in memory, and causing at least one vapor indicator to output a message indicating that a fault event has occurred.

[0014] The control unit may be configured to activate a reset timer in response to detecting a fault event, determine that the reset timer has elapsed, and, in response to determining that the reset timer has elapsed, perform a reset of the nicotine e-vaping device. The reset may be a soft reset, which resets the software application running on the control unit; a hard reset, which resets both the software application operating on the control unit and the hardware of the nicotine e-vaping device; or a power-on reset (POR). A POR may include generating a reset impulse to all circuits of the nicotine e-vaping device to clear the fault event.

[0015] The control device may be configured to determine that a fault event has been cleared by a reset, and in response to this determination that the fault event has been cleared by a reset, enable the vaping function, the charging operation, or both the vaping function and the charging operation.

[0016] The control device may be configured to detect a corrective action in a nicotine electronic vaping device and, in response to detecting the corrective action, enable the vaping function, the charging operation, or both the vaping function and the charging operation.

[0017] The nicotine pod assembly may include a memory configured to store a threshold temperature value, and the control device is configured to detect a fault event by retrieving the threshold temperature value from the memory, estimating the heater temperature during operation of the nicotine electronic vaping device, and detecting a fault event in response to determining that the heater temperature is equal to or greater than the threshold temperature value.

[0018] The device body may further include a power supply configured to supply power to a nicotine electronic vaping device. A fault event may be a power supply undervoltage fault event indicating that the power supply voltage is below a minimum threshold. The control device may further be configured to perform at least one resulting action in response to detecting a power supply undervoltage fault event, by disabling the vaping function in the nicotine electronic vaping device.

[0019] The device body may further include a power supply configured to supply power to a nicotine electronic vaping device. A fault event may be a temperature fault event of the power supply, indicating that the temperature of the power supply is above a maximum threshold. A control device may be configured to perform at least one resulting action in response to detecting a temperature fault event of the power supply, by preventing the power supply from being charged.

[0020] At least one exemplary embodiment provides a method for operating a nicotine electronic vaping device, the method comprising detecting a fault event in the nicotine electronic vaping device, classifying the fault event as one of a plurality of types of fault events, and performing at least one resulting action based on the classification of the fault event.

[0021] According to at least some exemplary embodiments, a failure event may be one of the following: a normal event, a soft failure pod event, a hard failure pod event, a soft failure device event, or a hard failure device event. Soft failure pod events and hard failure pod events may be abnormal conditions in the nicotine pod assembly, while soft failure device events and hard failure device events may be abnormal conditions in the device body.

[0022] At least one resulting action may include an automatic shut-off, heater shut-off, vaping shut-off, charging stop, or a combination thereof.

[0023] Performing the at least one resulting action may include disabling power to a heater in a nicotine electronic vaping device, recording the occurrence of a fault event in a memory of the nicotine electronic vaping device, and outputting an indication that the fault event has occurred.

[0024] Performing the at least one resulting action may include disabling a vaping function of a nicotine electronic vaping device, recording the occurrence of a fault event in a memory of the nicotine electronic vaping device, and outputting an indication that the fault event has occurred.

[0025] The method may further comprise: detecting removal of a nicotine pod assembly from the nicotine electronic vaping device; and enabling a vaping function of the nicotine electronic vaping device in response to detecting removal of the nicotine pod assembly from the nicotine electronic vaping device.

[0026] The method may further comprise causing the nicotine electronic vaping device to enter a sleep mode in response to determining that a corrective action has not occurred in response to the fault event.

[0027] Performing the at least one resulting action may include initiating an auto-off operation that causes the nicotine electronic vaping device to enter a sleep mode, recording the occurrence of a fault event in a memory of the nicotine electronic vaping device, and outputting an indication that the fault event has occurred.

[0028] Performing the at least one resulting action may include disabling a vaping function, a charging operation, or both a vaping function and a charging operation in a nicotine electronic vaping device, recording the occurrence of a fault event in a memory of the nicotine electronic vaping device, and outputting an indication that the fault event has occurred.

[0029] The method may further include, in response to detecting a malfunction event, activating a reset timer, determining that the reset timer has elapsed, and, in response to determining that the reset timer has elapsed, performing a reset of the nicotine electronic vaping device.

[0030] The method may further include determining that a fault event has been cleared by a reset, and, in response to determining that the fault event has been cleared by a reset, enabling the vaping function, charging operation, or both the vaping function and charging operation in the nicotine electronic vaping device.

[0031] The method may further include detecting a corrective action in a nicotine electronic vaping device, and enabling a vaping function, a charging operation, or both a vaping function and a charging operation in the nicotine electronic vaping device in response to detecting the corrective action.

[0032] Detecting a fault event may include obtaining a threshold temperature value from the memory of the nicotine electronic vaping device, estimating the temperature of the heater in the nicotine electronic vaping device, and detecting a fault event in response to determining that the heater temperature is above the threshold temperature value.

[0033] The fault event may be a power supply undervoltage fault event, indicating that the power supply voltage in the nicotine e-vaping device is below a minimum threshold. Performing at least one resulting action may include disabling the vaping function in the nicotine e-vaping device in response to detecting a power supply undervoltage fault event.

[0034] The fault event may be a power supply temperature fault event, indicating that the temperature of the power supply in the nicotine electronic vaping device is above a maximum threshold. Performing at least one resulting action may include preventing the power supply from charging in response to detecting a power supply temperature fault event.

[0035] Various features and advantages of non-limiting embodiments of this specification may become more apparent by considering the detailed description in conjunction with the accompanying drawings. The accompanying drawings are provided solely for illustrative purposes and should not be construed as limiting the scope of the claims. Unless otherwise stated, the accompanying drawings are not considered to be drawn to actual size. Various dimensions in the drawings may be exaggerated for clarity. [Brief explanation of the drawing]

[0036] [Figure 1] Figure 1 is a front view of a nicotine e-vaping device according to an exemplary embodiment. [Figure 2] Figure 2 is a side view of the nicotine e-vaping device shown in Figure 1. [Figure 3] Figure 3 is a rear view of the nicotine e-vaping device shown in Figure 1. [Figure 4] Figure 4 is a proximal end view of the nicotine e-vaping device shown in Figure 1. [Figure 5] Figure 5 is a distal end view of the nicotine e-vaping device shown in Figure 1. [Figure 6] Figure 6 is a perspective view of the nicotine e-vaping device shown in Figure 1. [Figure 7] Figure 7 is a magnified view of the pod entrance shown in Figure 6. [Figure 8] Figure 8 is a cross-sectional view of the nicotine e-vaping device shown in Figure 6. [Figure 9] Figure 9 is a perspective view of the main body of the nicotine e-vaping device shown in Figure 6. [Figure 10] Figure 10 is a front view of the main body of the device shown in Figure 9. [Figure 11] Figure 11 is an enlarged perspective view of the through hole in Figure 10. [Figure 12] Figure 12 is an enlarged perspective view of the electrical contacts of the device shown in Figure 10. [Figure 13] Figure 13 is a partial exploded view of the mouthpiece shown in Figure 12. [Figure 14] Figure 14 is a partially exploded view of the bezel structure shown in Figure 9. [Figure 15] Figure 15 is an enlarged perspective view of the mouthpiece, spring, retaining structure, and bezel structure shown in Figure 14. [Figure 16] Figure 16 is a partially exploded view of the front cover, frame, and rear cover shown in Figure 14. [Figure 17] Figure 17 is a perspective view of the nicotine pod assembly of the nicotine e-vaping device shown in Figure 6. [Figure 18] Figure 18 is another perspective view of the nicotine pod assembly shown in Figure 17. [Figure 19] Figure 19 is another perspective view of the nicotine pod assembly shown in Figure 18. [Figure 20] Figure 20 is a perspective view of the nicotine pod assembly from Figure 19, excluding the connector module. [Figure 21] Figure 21 is a perspective view of the connector module shown in Figure 19. [Figure 22] Figure 22 is another perspective view of the connector module shown in Figure 21. [Figure 23] Figure 23 is an exploded view of the core, heater, conductor, and contact core shown in Figure 22. [Figure 24] Figure 24 is an exploded view of the first housing portion of the nicotine pod assembly shown in Figure 17. [Figure 25] Figure 25 is a partially exploded view of the second housing portion of the nicotine pod assembly shown in Figure 17. [Figure 26] Figure 26 is an exploded view of the activation pin shown in Figure 25. [Figure 27] Figure 27 is a perspective view of the connector module of Figure 22, excluding the core, heater, conductor, and contact core. [Figure 28] Figure 28 is an exploded view of the connector module shown in Figure 27. [Figure 29] Figure 29 shows the electrical system of the device body and nicotine pod assembly of an exemplary embodiment of a nicotine e-vaping device. [Figure 30]Figure 30 is a simplified block diagram showing an automatic shutoff control system 2300 according to an exemplary embodiment. [Figure 31] Figure 31 is a flowchart showing a method for detecting idling events according to an exemplary embodiment. [Figure 32A] Figure 32A is a flowchart showing a method for detecting temperature-related problems in a heater according to an exemplary embodiment. [Figure 32B] Figure 32B is a flowchart showing a method for detecting a temperature-related event in a heater according to another exemplary embodiment. [Figure 33A] Figures 33A and 33B show an automatic shutoff control method according to one or more exemplary embodiments. [Figure 33B] Same as above. [Figure 34] Figure 34 shows an exemplary embodiment of the heater voltage measurement circuit 21252. [Figure 35] Figure 35 shows an exemplary embodiment of the heater current measurement circuit 21258 shown in Figure 29. [Figure 36] Figure 36 shows a temperature measurement circuit for a pod according to an exemplary embodiment. [Figure 37] Figure 37 shows a temperature measurement circuit for a pod according to another exemplary embodiment. [Figure 38] Figure 38 is a circuit diagram showing the control circuit of a heating engine according to an exemplary embodiment. [Figure 39] Figure 39 is a circuit diagram showing the control circuit of a heating engine according to an exemplary embodiment. [Figure 40] Figure 40 shows a temperature sensing converter according to an exemplary embodiment. [Figure 41] Figure 41 shows a temperature sensing converter according to another exemplary embodiment. [Figure 42A] Figure 42A shows a temperature measurement circuit for a power supply according to an exemplary embodiment. [Figure 42B] Figure 42B shows a temperature measurement circuit for a power supply according to another exemplary embodiment. [Figure 43A]Figure 43A shows a voltage measurement circuit for a power supply according to an exemplary embodiment. [Figure 43B] Figure 43B shows a voltage measurement circuit for a power supply according to an exemplary embodiment. [Figure 44A] Figure 44A shows a charger according to an exemplary embodiment. [Figure 44B] Figure 44B shows a charger according to another exemplary embodiment. [Modes for carrying out the invention]

[0037] Some detailed exemplary embodiments are disclosed herein. However, the specific structural and functional details disclosed herein are merely typical for the purpose of illustrating exemplary embodiments. Nevertheless, exemplary embodiments may be embodied in numerous alternative forms and should not be construed as being limited to the exemplary embodiments described herein.

[0038] Accordingly, while exemplary embodiments are subject to various modifications and alternative forms, they are shown as examples in the drawings and described in detail herein. However, it should be understood that there is no intention to limit the exemplary embodiments to any particular form disclosed; on the contrary, the exemplary embodiments encompass all their variations, equivalents, and alternatives. Similar figures refer to similar elements throughout the description in the figures.

[0039] Where an element or layer is referred to as "on top of," "connected to," "linked to," "attached to," "adjacent to," or "covering" another element or layer, it should be understood that there may be an element or layer that is directly on top of, directly connected to, directly linked to, directly attached to, directly adjacent to, or directly covers or interposed to the other element or layer. In contrast, where an element is referred to as "directly on top of," "directly connected to," or "directly linked to" another element or layer, there is no intervening element or layer. Similar figures refer to similar elements throughout this specification. The terms "and / or" as used herein include any and all combinations or partial combinations of one or more of the enumerated items relating to the element or layer.

[0040] The terms first, second, third, etc., may be used herein to describe various elements, regions, layers, and / or parts, but it should be understood that these elements, regions, layers, and / or parts should not be limited by these terms. These terms are used solely to distinguish one element, region, layer, or part from another. Accordingly, the first element, region, layer, or part described below will be referred to as the second element, region, layer, or part without departing from the teachings of the exemplary embodiments.

[0041] Spatial relationship terms (e.g., “down,” “below,” “bottom,” “up,” “top,” and similar) may be used herein to facilitate the description of the relationship between one element or feature and another when illustrating. It should be understood that spatial relationship terms are intended to encompass different orientations of the device in use or operation, in addition to the illustrated orientation. For example, if the device in the figure is inverted, an element described as “below” or “below” another element or feature will, after inversion, be oriented “up” the other element or feature. Thus, the term “below” may encompass both upward and downward orientations. The device may be oriented in other ways (by rotating 90 degrees or in other orientations), and the spatial relationship terms used herein should be interpreted accordingly.

[0042] The terms used herein are for the sole purpose of describing various exemplary embodiments and are not intended to limit the exemplary embodiments. The singular forms “a,” “an,” and “the” used herein are intended to include the plural unless the context explicitly indicates otherwise. It will be further understood that the terms “includes,” “including,” “comprises,” and / or “comprising,” when used herein, identify the presence of the described features, integers, steps, actions, and / or elements, but do not exclude the presence or addition of one or more other features, integers, steps, actions, elements, and / or groups thereof.

[0043] When the phrases “approximately” or “abbreviated” are used in this specification in combination with numerical values, unless otherwise clearly defined, the relevant numerical values ​​are intended to include a tolerance of ±10 percent above or below the stated numerical value.

[0044] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as those generally understood by those skilled in the art to the extent of the exemplary embodiments. Terms including those defined in commonly used dictionaries should, unless expressly defined herein, be construed to have a meaning consistent with those terms in the context of the relevant art, and not to be construed in an ideal or overly formal sense.

[0045] As used herein, “nicotine electronic vaping device” or “nicotine e-vaping device” may be referred to from time to time using “nicotine e-vaper device” and “nicotine e-vaping device,” and may be considered synonymous with them.

[0046] Figure 1 is a front view of a nicotine e-vaping device according to an exemplary embodiment. Figure 2 is a side view of the nicotine e-vaping device of Figure 1. Figure 3 is a rear view of the nicotine e-vaping device of Figure 1. Referring to Figures 1-3, the nicotine e-vaping device 500 includes a device body 100 configured to receive a nicotine pod assembly 300. The nicotine pod assembly 300 is a modular article configured to hold a nicotine pre-vapor formulation. The “nicotine pre-vapor formulation” is a material or combination of materials that can be deformed into a vapor. For example, the nicotine pre-vapor formulation may include, but is not limited to, water, beads, a solvent, an active ingredient, ethanol, a plant extract, a natural or artificial flavor, and / or a vapor-forming agent such as glycerin and propylene glycol, and may be a liquid formulation, a solid formulation, and / or a gel formulation. The nicotine e-vaping device 500 is configured to heat the nicotine pre-vapor formulation during vaping to generate nicotine vapor. As used herein, “nicotine vapor” is any substance generated or emitted from any nicotine e-vaping device relating to any of the exemplary embodiments disclosed herein.

[0047] As shown in Figures 1 and 3, the nicotine e-vaping device 500 extends in the longitudinal direction and has a length greater than its width. Furthermore, as shown in Figure 2, the length of the nicotine e-vaping device 500 is also greater than its thickness. Furthermore, the width of the nicotine e-vaping device 500 may be greater than its thickness. Assuming an xyz Cartesian coordinate system, the length of the nicotine e-vaping device 500 may be measured in the y direction, the width in the x direction, and the thickness in the z direction. Based on its front, side, and rear views, the nicotine e-vaping device 500 may have a substantially linear form with tapered ends, but exemplary embodiments are not limited thereto.

[0048] The device body 100 includes a front cover 104, a frame 106, and a rear cover 108. The front cover 104, frame 106, and rear cover 108 form a device housing that encloses mechanical elements, electronic elements, and / or circuits related to the operation of the nicotine e-vaping device 500. For example, the device housing of the device body 100 may enclose a power supply configured to power the nicotine e-vaping device 500, which may include supplying current to the nicotine pod assembly 300. The device housing of the device body 100 may also include one or more electrical systems for controlling the nicotine e-vaping device 500. Electrical systems according to exemplary embodiments will be described in more detail later. Furthermore, the front cover 104, frame 106, and rear cover 108 may constitute the majority of the visible portion of the device body 100 when assembled.

[0049] The front cover 104 (e.g., the first cover) defines a primary opening configured to accommodate a bezel structure 112. The primary opening may have a rounded rectangular shape, but other shapes are possible depending on the shape of the bezel structure 112. The bezel structure 112 defines a through-hole 150 configured to receive a nicotine pod assembly 300. The through-hole 150 is described herein in more detail, for example, with reference to Figure 9.

[0050] The front cover 104 also defines a secondary opening configured to house the optical guide device. The secondary opening may resemble a slot (e.g., an elongated rectangle with rounded ends), but other shapes are possible depending on the shape of the optical guide device. In an exemplary embodiment, the optical guide device includes an optical guide housing 114 and a button housing 122. The optical guide housing 114 is configured to expose an optical guide lens 116, while the button housing 122 is configured to expose a first button lens 124 and a second button lens 126 (e.g., Figure 16). The first button lens 124 and the upstream portion of the button housing 122 may form a first button 118. Similarly, the second button lens 126 and the downstream portion of the button housing 122 may form a second button 120. The button housing 122 may be in the form of a single structure or two separate structures. In the latter form, the first button 118 and the second button 120 are movable with a more independent feel when pressed.

[0051] The operation of the nicotine e-vaping device 500 can be controlled by a first button 118 and a second button 120. For example, the first button 118 may be a power button, and the second button 120 may be an intensity button. Although two buttons are shown in the drawings in relation to the optical guide device, it should be understood that more (or fewer) buttons may be provided depending on the available features and the desired user interface.

[0052] The frame 106 (e.g., base frame) is a central support structure for the device body 100 (and the nicotine e-vaping device 500 as a whole). The frame 106 may be referred to as the chassis. The frame 106 includes a proximal end, a distal end, and a pair of side sections between the proximal and distal ends. The proximal and distal ends may also be referred to as the downstream end and the upstream end, respectively. As used herein, “proximal” (and conversely “distal”) refers to the adult vapor during vaping, and “downstream” (and conversely “upstream”) refers to the flow of nicotine vapor. A bridging section may be placed between the opposing inner surfaces of the side sections (e.g., approximately midway along the length of the frame 106) for further strength and stability. The frame 106 may be formed integrally to form a monolithic structure.

[0053] Regarding the structural materials, the frame 106 may be formed from an alloy or plastic. Alloys (e.g., die-cast grade, machinable grade) may be aluminum (Al) alloy or zinc (Zn) alloy. Plastics may be polycarbonate (PC), acrylonitrile butadiene styrene (ABS), or a combination thereof (PC / ABS). For example, polycarbonate may be LUPOY SC1004A. Furthermore, the frame 106 may be provided with a surface finish for functional and / or aesthetic reasons (e.g., to provide a high-end appearance). In exemplary embodiments, the frame 106 (e.g., formed from an aluminum alloy) may be anodized. In another embodiment, the frame 106 (e.g., formed from a zinc alloy) may be coated or painted with hard enamel. In yet another embodiment, the frame 106 (e.g., formed from polycarbonate) may be metallized. In yet another embodiment, the frame 106 (e.g., formed from acrylonitrile butadiene styrene) may be electroplated. It should be understood that the structural materials relating to frame 106 may also apply to the front cover 104, rear cover 108, and / or other suitable parts of the nicotine e-vaping device 500.

[0054] The rear cover 108 (e.g., a second cover) also defines an opening configured to accommodate a bezel structure 112. The opening may have a rounded rectangular shape, but other shapes are possible depending on the shape of the bezel structure 112. In exemplary embodiments, the opening in the rear cover 108 is smaller than the primary opening in the front cover 104. Furthermore, although not shown, it should be understood that an optical guide device (e.g., including a button) may be provided on the rear of the nicotine e-vaping device 500 in addition to (or instead of) the optical guide device on the front of the nicotine e-vaping device 500.

[0055] The front cover 104 and the rear cover 108 may be configured to engage with the frame 106 via a snap-fit ​​device. For example, the front cover 104 and / or the rear cover 108 may include clips configured to interlock with corresponding mating members of the frame 106. In a non-limiting embodiment, the clips may be in the form of tabs having orifices configured to receive corresponding mating members of the frame 106 (e.g., projections with inclined edges). Alternatively, the front cover 104 and / or the rear cover 108 may be configured to engage with the frame 106 via a press-fit (which may also be referred to as a press-fit or friction-fit). However, it should be understood that the front cover 104, the frame 106, and the rear cover 108 may be connected via other suitable devices and techniques.

[0056] The device body 100 also includes a mouthpiece 102. The mouthpiece 102 can be fixed to the proximal end of the frame 106. Furthermore, in an exemplary embodiment where the frame 106 is sandwiched between a front cover 104 and a rear cover 108, as shown in Figure 2, the mouthpiece 102 can abut against the front cover 104, the frame 106, and the rear cover 108. Furthermore, in a non-limiting embodiment, the mouthpiece 102 can be coupled to the device housing via a bayonet connection.

[0057] Figure 4 is a proximal end view of the nicotine e-vaping device of Figure 1. Referring to Figure 4, the outlet surface of the mouthpiece 102 defines multiple vapor outlets. In a non-limiting embodiment, the outlet surface of the mouthpiece 102 may be elliptical. Furthermore, the outlet surface of the mouthpiece 102 may include a first crossbar corresponding to the major axis of the elliptical outlet surface and a second crossbar corresponding to the minor axis of the elliptical outlet surface. Furthermore, the first and second crossbars intersect at a right angle and may be integrally formed parts of the mouthpiece 102. Although the outlet surface is shown defining four vapor outlets, it should be understood that exemplary embodiments are not limited thereto. For example, the outlet surface may define fewer than four (e.g., one, two) vapor outlets or more than four (e.g., six, eight) vapor outlets.

[0058] Figure 5 is a distal end view of the nicotine e-vaping device of Figure 1. Referring to Figure 5, the distal end of the nicotine e-vaping device 500 includes a port 110. Port 110 is configured to receive current from an external power source (e.g., via a USB cable) to charge the internal power supply within the nicotine e-vaping device 500. Furthermore, port 110 may also be configured to transmit and / or receive data to and from another nicotine e-vaping device or other electronic devices (e.g., a phone, tablet, or computer) (e.g., via a USB cable). In addition, the nicotine e-vaping device 500 may be configured for wireless communication with another electronic device, such as a phone, via application software (app) installed on its electronic device. In such an example, an adult vaper may control the nicotine e-vaping device 500 through the app or otherwise connect with it (e.g., locate the nicotine e-vaping device, check usage information, change operating parameters).

[0059] Figure 6 is a perspective view of the nicotine e-vaping device of Figure 1. Figure 7 is a magnified view of the pod inlet of Figure 6. Referring to Figures 6 and 7, and as briefly mentioned above, the nicotine e-vaping device 500 includes a nicotine pod assembly 300 configured to hold a nicotine prevapor formulation. The nicotine pod assembly 300 has an upstream end (facing the optical guide device) and a downstream end (facing the mouthpiece 102). In a non-limiting embodiment, the upstream end is the face opposite the downstream end of the nicotine pod assembly 300. The upstream end of the nicotine pod assembly 300 defines the pod inlet 322. The device body 100 defines a through-hole (e.g., the through-hole 150 in Figure 9) configured to receive the nicotine pod assembly 300. In an exemplary embodiment, the bezel structure 112 of the device body 100 defines the through-hole and includes an upstream edge. In particular, as shown in Figure 7, the upstream edge of the bezel structure 112 is angled (for example, downwards inward) so as to expose the pod inlet 322 when the nicotine pod assembly 300 is placed in the through-hole of the device body 100.

[0060] For example, rather than continuing the contour of the front cover 104 (which is coplanar relative to the front of the nicotine pod assembly 300 and thus covers the pod inlet 322), the upstream edge of the bezel structure 112 is in the form of a scoop configured to direct ambient air into the pod inlet 322. This angled / scoop configuration may help reduce or prevent blockage of the air intake of the nicotine e-vaping device 500 (e.g., the pod inlet 322). The depth of the scoop may be such that less than half (e.g., less than a quarter) of the upstream end face of the nicotine pod assembly 300 is exposed. Furthermore, in a non-limiting embodiment, the pod inlet 322 is in the form of a slot. Furthermore, if the device body 100 is considered to extend in a first direction, the slot may be considered to extend in a second direction which is transverse to the first direction.

[0061] Figure 8 is a cross-sectional view of the nicotine e-vaping device of Figure 6. In Figure 8, the cross-section is cut along the longitudinal axis of the nicotine e-vaping device 500. As shown, the device body 100 and the nicotine pod assembly 300 include mechanical elements, electronic elements, and / or circuits related to the operation of the nicotine e-vaping device 500, which are described in more detail herein and / or incorporated herein by reference. For example, the nicotine pod assembly 300 may include mechanical elements configured to act to release a nicotine pre-vapor formulation from an internally sealed nicotine storage unit. The nicotine pod assembly 300 may also have mechanical aspects configured to engage with the device body 100 to facilitate the insertion and seating of the nicotine pod assembly 300.

[0062] Furthermore, the nicotine pod assembly 300 may be a “smart pod” including electronic elements and / or circuits configured to store, receive, and / or transmit information to and from the device body 100. Such information may be used to authenticate the nicotine pod assembly 300 for use with the device body 100 (for example, to prevent the use of unauthorized / counterfeit nicotine pod assemblies). Furthermore, the information may be used to identify the type of nicotine pod assembly 300, which is then correlated with a vaping profile based on the identified type. The vaping profile may be designed to define general parameters for heating the nicotine pre-vaper formulation and may be subjected to adjustment, purification, or other adjustments by an adult vaper before and / or during vaping.

[0063] The nicotine pod assembly 300 may also communicate with the device body 100 other information that may be relevant to the operation of the nicotine e-vaping device 500. Examples of relevant information may include the level of nicotine pre-vapor formulation in the nicotine pod assembly 300, and / or the time elapsed since the nicotine pod assembly 300 was inserted into and activated in the device body 100. For example, if the nicotine pod assembly 300 was inserted into the device body 100 and activated more than a certain period of time prior to the device (e.g., more than 6 months prior), the nicotine e-vaping device 500 may not allow vaping, and the adult vaper may be prompted to replace the nicotine pod assembly 300 with a new one, even if the nicotine pod assembly 300 still contains an appropriate level of nicotine pre-vapor formulation.

[0064] The device body 100 may include mechanical elements (e.g., complementary structures) configured to engage with, hold, and / or activate the nicotine pod assembly 300. Furthermore, the device body 100 may include electronic elements and / or circuits configured to receive current and charge an internal power source (e.g., a battery), which is then configured to supply power to the nicotine pod assembly 300 during vaping. Furthermore, the device body 100 may include electronic elements and / or circuits configured to communicate with the nicotine pod assembly 300, different nicotine e-vaping devices, other electronic devices (e.g., phones, tablets, computers), and / or adult vapers. Information communicated may include pod-specific data, details of the current vaping, and / or past vaping patterns / history. Adult vapers may be notified of such communications by feedback, which may be tactile (e.g., vibration), auditory (e.g., beeping), and / or visual (e.g., colored / flashing light). Charging and / or information communication may be performed via port 110 (for example, via a USB cable).

[0065] Figure 9 is a perspective view of the device body of the nicotine e-vaping device of Figure 6. Referring to Figure 9, the bezel structure 112 of the device body 100 defines a through-hole 150. The through-hole 150 is configured to receive a nicotine pod assembly 300. To facilitate the insertion and seating of the nicotine pod assembly 300 into the through-hole 150, the upstream edge of the bezel structure 112 includes a first upstream projection 128a and a second upstream projection 128b. The through-hole 150 may have a rectangular shape with rounded corners. In an exemplary embodiment, the first upstream projection 128a and the second upstream projection 128b are integrally formed with the bezel structure 112 and are positioned at the two rounded corners of the upstream edge.

[0066] The downstream side wall of the bezel structure 112 may define a first downstream opening, a second downstream opening, and a third downstream opening. The retaining structure, including the first downstream projection 130a and the second downstream projection 130b, is engaged with the bezel structure 112 such that the first downstream projection 130a and the second downstream projection 130b each project into the through hole 150 through the first downstream opening and the second downstream opening of the bezel structure 112, respectively. Furthermore, the distal end of the mouthpiece 102 extends into the through hole 150 through the third downstream opening of the bezel structure 112, and as a result lies between the first downstream projection 130a and the second downstream projection 130b.

[0067] Figure 10 is a front view of the device body shown in Figure 9. Referring to Figure 10, the device body 100 includes an electrical connector 132 for the device located upstream of the through-hole 150. The electrical connector 132 of the device body 100 is configured to electrically engage with the nicotine pod assembly 300, which is placed inside the through-hole 150. As a result, during vaping, power can be supplied from the device body 100 to the nicotine pod assembly 300 via the electrical connector 132. Furthermore, data can be transmitted and / or received between the device body 100 and the nicotine pod assembly 300 via the electrical connector 132.

[0068] Figure 11 is an enlarged perspective view of the through-hole in Figure 10. Referring to Figure 11, the first upstream projection 128a, the second upstream projection 128b, the first downstream projection 130a, the second downstream projection 130b, and the distal end of the mouthpiece 102 protrude into the through-hole 150. In exemplary embodiments, the first upstream projection 128a and the second upstream projection 128b are fixed structures (e.g., fixed pivots), while the first downstream projection 130a and the second downstream projection 130b are easily machined structures (e.g., retractable members). For example, the first projection 130a and the second downstream projection 130b may be configured to be extended by default (e.g., spring-loaded), while also being configured to temporarily retract (and reversibly return to the extended state) to facilitate insertion of the nicotine pod assembly 300.

[0069] In particular, when inserting the nicotine pod assembly 300 into the through hole 150 of the device body 100, the recess on the upstream end face of the nicotine pod assembly 300 first engages with the first upstream projection 128a and the second upstream projection 128b, and then the nicotine pod assembly 300 can be rotated (around the first upstream projection 128a and the second upstream projection 128b) until the recess on the downstream end face of the nicotine pod assembly 300 engages with the first downstream projection 130a and the second downstream projection 130b. In such cases, the axis of rotation of the nicotine pod assembly 300 (during rotation) can be perpendicular to the longitudinal axis of the device body 100. Furthermore, the first downstream projection 130a and the second downstream projection 130b, which can be biased to facilitate processing, can retract and elastically extend when the nicotine pod assembly 300 is rotated into the through hole 150, and can engage with a recess on the downstream end face of the nicotine pod assembly 300. Moreover, when the first downstream projection 130a and the second downstream projection 130b engage with the recess on the downstream end face of the nicotine pod assembly 300, tactile and / or auditory feedback (e.g., an audible click) can be generated to inform an adult vaper that the nicotine pod assembly 300 is properly positioned in the through hole 150 of the device body 100.

[0070] Figure 12 is an enlarged perspective view of the electrical contacts of the device in Figure 10. The electrical contacts of the device body 100 are configured to engage with the electrical contacts of the pods of the nicotine pod assembly 300 when the nicotine pod assembly 300 is placed in the through-hole 150 of the device body 100. Referring to Figure 12, the electrical contacts of the device body 100 include the device's electrical connector 132. The device's electrical connector 132 includes power contacts and data contacts. The power contacts of the device's electrical connector 132 are configured to supply power from the device body 100 to the nicotine pod assembly 300. As shown, the power contacts of the device's electrical connector 132 include a first pair of power contacts and a second pair of power contacts (positioned closer to the front cover 104 than to the rear cover 108). The first power contact pair (e.g., the pair adjacent to the first upstream projection 128a) may be a single, integrated structure, separate from the second power contact pair, and when assembled, may include two projections extending into the through-hole 150. Similarly, the second power contact pair (e.g., the pair adjacent to the second upstream projection 128b) may be a single, integrated structure, separate from the first power contact pair, and when assembled, may include two projections extending into the through-hole 150. The first and second power contact pairs of the electrical connector 132 of the device may be mounted and biased in a manner that facilitates machining, so as to extend into the through-hole 150 by default, and so as to retract (e.g., independently) from the through-hole 150 when subjected to a force that overcomes biasing.

[0071] The data contacts of the device's electrical connector 132 are configured to transmit data between the nicotine pod assembly 300 and the device body 100. As shown in the figure, the data contacts of the device's electrical connector 132 include a row of five protrusions (positioned closer to the rear cover 108 than to the front cover 104). The data contacts of the device's electrical connector 132 may be a separate structure that extends into the through-hole 150 when assembled. The data contacts of the device's electrical connector 132 may also be mounted and biased (e.g., using a spring) in a manner that allows for easy machining, such as extending into the through-hole 150 by default, and retracting (e.g., independently) from the through-hole 150 if subjected to a force that overcomes bias. For example, when the nicotine pod assembly 300 is inserted into the through-hole 150 of the device body 100, the pod electrical contacts of the nicotine pod assembly 300 press against the corresponding device electrical contacts of the device body 100. As a result, the power and data contacts of the device's electrical connector 132 are retracted (e.g., at least partially retracted) into the device body 100, but due to their elastic arrangement, they remain pressed against the corresponding pod electrical contacts, thereby helping to ensure proper electrical connection between the device body 100 and the nicotine pod assembly 300. Furthermore, such a connection may also be mechanically fixed and have minimal contact resistance to ensure that power and / or signals between the device body 100 and the nicotine pod assembly 300 are reliably and accurately transmitted and / or communicated. Although various embodiments have been described in relation to the device's electrical contacts in the device body 100, it should be understood that exemplary embodiments are not limited thereto, and other configurations may be available.

[0072] Figure 13 is a partially exploded view relating to the mouthpiece of Figure 12. Referring to Figure 13, the mouthpiece 102 is configured to engage with the housing of the device via a retaining structure 140. In an exemplary embodiment, the retaining structure 140 is primarily located between the frame 106 and the bezel structure 112. As shown, the retaining structure 140 is positioned within the housing of the device such that its proximal end extends through the proximal end of the frame 106. The retaining structure 140 may extend slightly beyond the proximal end of the frame 106 or substantially horizontally with it. The proximal end of the retaining structure 140 is configured to receive the distal end of the mouthpiece 102. The proximal end of the retaining structure 140 may be a female end, while the distal end of the mouthpiece may be a male end.

[0073] For example, the mouthpiece 102 may be connected to the retaining structure 140 by a bayonet connection (e.g., reversibly connected). In such an example, the female end of the retaining structure 140 may define a pair of opposing L-shaped slots, while the male end of the mouthpiece 102 may have opposing radial members 134 (e.g., radial pins) configured to engage with the L-shaped slots of the retaining structure 140. Each of the L-shaped slots of the retaining structure 140 may have a longitudinal portion and a circumferential portion. Optionally, the end of the circumferential portion may have a serif portion that helps reduce or prevent the possibility of the radial member 134 of the mouthpiece 102 being accidentally disengaged. In a non-limiting embodiment, the longitudinal portion of the L-shaped slot extends parallel to the longitudinal axis of the device body 100, while the circumferential portion of the L-shaped slot extends around the longitudinal axis (e.g., central axis) of the device body 100. As a result, in order to connect the mouthpiece 102 to the housing of the device, the mouthpiece 102 shown in Figure 13 is first rotated 90 degrees so that the radial member 134 is aligned with the entrance to the longitudinal portion of the L-shaped slot of the retaining structure 140. The mouthpiece 102 is then pushed into the retaining structure 140 so that it slides along the longitudinal portion of the L-shaped slot until the radial member 134 reaches the joint with each of the circumferential portions. At this point, the mouthpiece 102 is then rotated so that the radial member 134 moves across the circumferential portions until it reaches each end. If a serif portion is present at each end, tactile and / or auditory feedback (e.g., an audible click) may be generated to inform the adult vaper that the mouthpiece 102 is properly connected to the housing of the device.

[0074] The mouthpiece 102 defines a vapor passage 136 through which nicotine vapor flows during vaping. The vapor passage 136 is in fluid communication with a through-hole 150 (where the nicotine pod assembly 300 is placed within the device body 100). The proximal end of the vapor passage 136 may include a flared portion. Furthermore, the mouthpiece 102 may include an end cover 138. The end cover 138 may be tapered from its distal end to its proximal end. The outlet surface of the end cover 138 defines a plurality of vapor outlets. Four vapor outlets are shown in the end cover 138, but it should be understood that exemplary embodiments are not limited thereto.

[0075] Figure 14 is an exploded view relating to the bezel structure of Figure 9. Figure 15 is an enlarged perspective view of the mouthpiece, spring, retaining structure, and bezel structure of Figure 14. Referring to Figures 14 and 15, the bezel structure 112 includes an upstream side wall and a downstream side wall. The upstream side wall of the bezel structure 112 defines a connector opening 146. The connector opening 146 is configured to expose or receive the electrical connector 132 of the device body 100. The downstream side wall of the bezel structure 112 defines a first downstream opening 148a, a second downstream opening 148b, and a third downstream opening 148c. The first downstream opening 148a and the second downstream opening 148b of the bezel structure 112 are configured to receive the first downstream projection 130a and the second downstream projection 130b of the retaining structure 140, respectively. The third downstream opening 148c of the bezel structure 112 is configured to receive the distal end of the mouthpiece 102.

[0076] As shown in Figure 14, the first downstream projection 130a and the second downstream projection 130b are located on the concave side surface of the retaining structure 140. As shown in Figure 15, the first post 142a and the second post 142b are located on the opposing convex side surfaces of the retaining structure 140. The first spring 144a and the second spring 144b are positioned on the first post 142a and the second post 142b, respectively. The first spring 144a and the second spring 144b are configured to bias the retaining structure 140 against the bezel structure 112.

[0077] The bezel structure 112, when assembled, can be secured to the frame 106 via a pair of tabs adjacent to the connector opening 146. Furthermore, the retaining structure 140 abuts against the bezel structure 112 such that the first downstream projection 130a and the second downstream projection 130b extend through the first downstream opening 148a and the second downstream opening 148b, respectively. The mouthpiece 102 is connected to the retaining structure 140 such that the distal end of the mouthpiece 102 extends through the retaining structure 140 and the third downstream opening 148c of the bezel structure 112. The first spring 144a and the second spring 144b are located between the frame 106 and the retaining structure 140.

[0078] When the nicotine pod assembly 300 is inserted into the through-hole 150 of the device body 100, the downstream end of the nicotine pod assembly 300 pushes the first downstream projection 130a and the second downstream projection 130b of the retaining structure 140. As a result, the first downstream projection 130a and the second downstream projection 130b of the retaining structure 140 elastically yield and retract from the through-hole 150 of the device body 100 (by compression of the first spring 144a and the second spring 144b), thereby allowing the insertion of the nicotine pod assembly 300 to proceed. In an exemplary embodiment, when the first downstream projection 130a and the second downstream projection 130b are fully retracted from the through-hole 150 of the device body 100, the displacement of the retaining structure 140 may cause the ends of the first post 142a and the second post 142b to contact the inner end face of the frame 106. Furthermore, since the mouthpiece 102 is connected to the retaining structure 140, the distal end of the mouthpiece 102 retracts from the through hole 150, and therefore the proximal end of the mouthpiece 102 (e.g., the visible portion including the end cover 138) also shifts by a corresponding distance away from the housing of the device.

[0079] Once the nicotine pod assembly 300 is properly inserted, the first downstream recess and the second downstream recess of the nicotine pod assembly 300 reach positions that enable engagement with the first downstream projection 130a and the second downstream projection 130b, respectively. Due to the energy conserved from the compression of the first spring 144a and the second spring 144b, the first downstream projection 130a and the second downstream projection 130b elastically extend and engage with the first downstream recess and the second downstream recess of the nicotine pod assembly 300, respectively. Furthermore, this engagement may generate tactile and / or auditory feedback (e.g., an audible click) to inform the adult vaper that the nicotine pod assembly 300 is properly positioned within the through-hole 150 of the device body 100.

[0080] Figure 16 is a partially exploded view relating to the front cover, frame, and rear cover of Figure 14. Referring to Figure 16, various mechanical, electronic, and / or circuitry related to the operation of the nicotine e-vaping device 500 may be fixed to the frame 106. The front cover 104 and rear cover 108 may be configured to engage with the frame 106 via snap-fit ​​devices. In exemplary embodiments, the front cover 104 and rear cover 108 include clips configured to interlock with corresponding mating members of the frame 106. The clips may be in the form of tabs having orifices configured to receive corresponding mating members of the frame 106 (e.g., projections with rounded edges). In Figure 16, the front cover 104 has two rows of four clips each (a total of eight clips for the front cover 104). Similarly, the rear cover 108 has two rows of four clips each (a total of eight clips for the rear cover 108). The corresponding fitting members of frame 106 may be located on the inner sidewall of frame 106. As a result, the engaged clips and fitting members may be hidden from view when the front cover 104 and rear cover 108 are closed together. Alternatively, the front cover 104 and / or rear cover 108 may be configured to engage with frame 106 via a press-fit. However, it should be understood that the front cover 104, frame 106, and rear cover 108 may be connected by other suitable devices and techniques.

[0081] Figure 17 is a perspective view of the nicotine pod assembly of the nicotine e-vaping device of Figure 6. Figure 18 is another perspective view of the nicotine pod assembly of Figure 17. Figure 19 is another perspective view of the nicotine pod assembly of Figure 18. Referring to Figures 17-19, the nicotine pod assembly 300 for the nicotine e-vaping device 500 includes a pod body configured to hold a nicotine pre-vapor formulation. The pod body has an upstream end and a downstream end. The upstream end of the pod body defines a cavity 310 (Figure 20). The downstream end of the pod body defines a pod outlet 304 that is in fluid communication with the cavity 310 at the upstream end. A connector module 320 is configured to fit within the cavity 310 of the pod body. The connector module 320 includes an outer surface and sides. The outer surface of the connector module 320 forms the outer surface of the pod body.

[0082] The outer surface of the connector module 320 defines the pod inlet 322. The pod inlet 322 (through which air enters during vaping) is in fluid communication with the pod outlet 304 (through which nicotine vapor is expelled during vaping). The pod inlet 322 is shown in the form of a slot in Figure 19. However, it should be understood that the exemplary embodiment is not limited thereto, and other forms are possible. When the connector module 320 is housed within the cavity 310 of the pod body, the outer surface of the connector module 320 remains visible, while the sides of the connector module 320 are almost obscured so that they are only partially visible through the pod inlet 322 based on a given angle.

[0083] The outer surface of the connector module 320 includes at least one electrical contact. This at least one electrical contact may include multiple power contacts. For example, the multiple power contacts may include a first power contact 324a and a second power contact 324b. The first power contact 324a of the nicotine pod assembly 300 is configured to electrically connect to a first pair of power contacts of the device's electrical connector 132 of the device body 100 (for example, the pair of power contacts adjacent to the first upstream projection 128a in Figure 12). Similarly, the second power contact 324b of the nicotine pod assembly 300 is configured to electrically connect to a second pair of power contacts of the device's electrical connector 132 of the device body 100 (for example, the pair of power contacts adjacent to the second upstream projection 128b in Figure 12). Furthermore, at least one electrical contact of the nicotine pod assembly 300 includes multiple data contacts 326. The multiple data contacts 326 of the nicotine pod assembly 300 are configured to electrically connect to the data contacts of the device's electrical connector 132 (e.g., the row of five protrusions in Figure 12). While two power contacts and five data contacts are shown in relation to the nicotine pod assembly 300, it should be understood that other variations are possible depending on the design of the device body 100.

[0084] In exemplary embodiments, the nicotine pod assembly 300 includes a front surface, a rear surface opposite the front surface, a first side surface between the front and rear surfaces, a second side surface opposite the first side surface, an upstream end surface, and a downstream end surface opposite the upstream end surface. The corners of the side surfaces and end surfaces (e.g., the corner between the first side surface and the upstream end surface, the corner between the upstream end surface and the second side surface, the corner between the second side surface and the downstream end surface, and the corner between the downstream end surface and the first side surface) may be rounded. However, in some cases, the corners may be angular. Furthermore, the peripheral edge of the front surface may be in the form of a ledge. The outer surface of the connector module 320 may be considered part of the upstream end surface of the nicotine pod assembly 300. The front surface of the nicotine pod assembly 300 may be wider and longer than the rear surface. In such cases, the first and second side surfaces may be angled inward toward each other. The upstream and downstream end surfaces may also be angled inward toward each other. The insertion of the nicotine pod assembly 300 is unidirectional due to its angled surface (for example, from the front side of the device body 100 (the side associated with the front cover 104)). As a result, the possibility of the nicotine pod assembly 300 being improperly inserted into the device body 100 can be reduced or prevented.

[0085] As shown in the figure, the pod body of the nicotine pod assembly 300 includes a first housing portion 302 and a second housing portion 308. The first housing portion 302 has a downstream end that defines a pod outlet 304. The edge of the pod outlet 304 may optionally be a recessed or indented area. In such cases, this area may resemble a cove, with the side of the edge adjacent to the rear surface of the nicotine pod assembly 300 being open, while the side of the edge adjacent to the front surface may be enclosed by a raised portion at the downstream end of the first housing portion 302. The raised portion may function as a stopper for the distal end of the mouthpiece 102. As a result, this configuration of the pod outlet 304 may facilitate the reception and alignment of the distal end of the mouthpiece 102 via seating on the open side of the edge and subsequently on the raised portion at the downstream end of the first housing portion 302 (e.g., Figure 11). In a non-limiting embodiment, the distal end of the mouthpiece 102 may also include (or be formed with) an elastic material that helps create a seal around the pod outlet 304 when the nicotine pod assembly 300 is properly inserted into the through hole 150 of the device body 100.

[0086] The downstream end of the first housing portion 302 additionally defines at least one downstream recess. In exemplary embodiments, the at least one downstream recess is in the form of a first downstream recess 306a and a second downstream recess 306b. The pod outlet 304 may be located between the first downstream recess 306a and the second downstream recess 306b. The first downstream recess 306a and the second downstream recess 306b are configured to engage with a first downstream projection 130a and a second downstream projection 130b of the device body 100, respectively. As shown in Figure 11, the first downstream projection 130a and the second downstream projection 130b of the device body 100 may be located at adjacent corners of the downstream side wall of the through hole 150. The first downstream recess 306a and the second downstream recess 306b may each be in the form of a V-shaped notch. In such cases, each of the first downstream projection 130a and the second downstream projection 130b of the device body 100 may take the form of a wedge-shaped structure configured to engage with corresponding V-shaped notches in the first downstream recess 306a and the second downstream recess 306b. The first downstream recess 306a may abut against the downstream end face and the corner of the first side surface, while the second downstream recess 306b may abut against the downstream end face and the corner of the second side surface. As a result, the edges of the first downstream recess 306a and the second downstream recess 306b adjacent to the first and second side surfaces, respectively, may be open. In such cases, as shown in Figure 18, each of the first downstream recess 306a and the second downstream recess 306b may be a three-sided recess.

[0087] The second housing portion 308 has an upstream end that defines a cavity 310 (Figure 20). The cavity 310 is configured to receive a connector module 320 (Figure 21). Furthermore, the upstream end of the second housing portion 308 defines at least one upstream recess. In an exemplary embodiment, the at least one upstream recess is in the form of a first upstream recess 312a and a second upstream recess 312b. The pod inlet 322 may be located between the first upstream recess 312a and the second upstream recess 312b. The first upstream recess 312a and the second upstream recess 312b are configured to engage with a first upstream projection 128a and a second upstream projection 128b of the device body 100, respectively. As shown in Figure 12, the first upstream projection 128a and the second upstream projection 128b of the device body 100 may be located at adjacent corners of the upstream side wall of the through hole 150. The depth of the first upstream recess 312a and the second upstream recess 312b may be greater than the depth of the first downstream recess 306a and the second downstream recess 306b. The ends of the first upstream recess 312a and the second upstream recess 312b may also be more rounded than the ends of the first downstream recess 306a and the second downstream recess 306b. For example, the first upstream recess 312a and the second upstream recess 312b may each be in the form of a U-shaped recess. In such a case, the first upstream projection 128a and the second upstream projection 128b of the device body 100 may each be in the form of a rounded knob configured to engage with the corresponding U-shaped recesses of the first upstream recess 312a and the second upstream recess 312b. The first upstream recess 312a can abut against the corner between the upstream end face and the first side surface, while the second upstream recess 312b can abut against the corner between the upstream end face and the second side surface. As a result, the edges of the first upstream recess 312a and the edge of the second upstream recess 312b adjacent to the first and second side surfaces, respectively, can be left open.

[0088] The first housing portion 302 may define an internal nicotine storage section configured to hold the nicotine prevapor formulation. The nicotine storage section may be configured to seal the nicotine prevapor formulation until the activation of the nicotine pod assembly 300 to release the nicotine prevapor formulation from the nicotine storage section. As a result of the sealing, the nicotine prevapor formulation is separated from the environment and internal elements of the nicotine pod assembly 300 that may react with the nicotine prevapor formulation, thereby reducing or preventing the possibility of adverse effects on the shelf life and / or perceptual properties (e.g., flavor) of the nicotine prevapor formulation. The second housing portion 308 may contain a structure configured to activate the nicotine pod assembly 300 and, after activation, receive and heat the nicotine prevapor formulation released from the nicotine storage section.

[0089] The nicotine pod assembly 300 may be manually activated by an adult vaper before inserting the nicotine pod assembly 300 into the device body 100. Alternatively, the nicotine pod assembly 300 may be activated as part of the insertion of the nicotine pod assembly 300 into the device body 100. In exemplary embodiments, the second housing portion 308 of the pod body includes a puncture device configured to release the nicotine prevapor formulation from the nicotine storage during the activation of the nicotine pod assembly 300. The puncture device may be in the form of a first activation pin 314a and a second activation pin 314b, which are described in more detail herein.

[0090] To manually activate the nicotine pod assembly 300, an adult vaper may press the first activation pin 314a and the second activation pin 314b inward (for example, simultaneously or sequentially) before inserting the nicotine pod assembly 300 into the through-hole 150 of the device body 100. For example, the first activation pin 314a and the second activation pin 314b may be manually pressed until their ends are substantially horizontal to the upstream end face of the nicotine pod assembly 300. In an exemplary embodiment, the inward movement of the first activation pin 314a and the second activation pin 314b causes the seal of the nicotine storage to be perforated or otherwise compromised so that the nicotine pre-vapor formulation is released therefrom.

[0091] Alternatively, to activate the nicotine pod assembly 300 as part of inserting it into the device body 100, the nicotine pod assembly 300 is first positioned such that the first upstream recess 312a and the second upstream recess 312b engage (e.g., upstream engage) with the first upstream projection 128a and the second upstream projection 128b, respectively. Since each of the first upstream projection 128a and the second upstream projection 128b of the device body 100 may be in the form of a rounded knob configured to engage with the corresponding U-shaped recesses of the first upstream recess 312a and the second upstream recess 312b, the nicotine pod assembly 300 can then be relatively easily swung into the through-hole 150 of the device body 100 around the first upstream projection 128a and the second upstream projection 128b.

[0092] With respect to the rotation of the nicotine pod assembly 300, the axis of rotation can be considered to extend through the first upstream projection 128a and the second upstream projection 128b and be oriented perpendicular to the longitudinal axis of the device body 100. During the initial positioning and subsequent rotation of the nicotine pod assembly 300, the first activation pin 314a and the second activation pin 314b contact the upstream side wall of the through hole 150, and as the nicotine pod assembly 300 advances into the through hole 150, the first activation pin 314a and the second activation pin 314b transition from an extended state to a retracted state as they are pushed (for example, simultaneously) into the second housing portion 308. When the downstream end of the nicotine pod assembly 300 reaches the vicinity of the downstream side wall of the through hole 150 and contacts the first downstream projection 130a and the second downstream projection 130b, the first downstream projection 130a and the second downstream projection 130b retract, and then, due to the positioning of the nicotine pod assembly 300, the first downstream projection 130a and the second downstream projection 130b of the device body 100 become capable of engaging (e.g., downstream engaging) with the first downstream recess 306a and the second downstream recess 306b of the nicotine pod assembly 300, respectively, and elastically extend (e.g., spring back).

[0093] As described above, according to the exemplary embodiment, the mouthpiece 102 is fixed to the retaining structure 140 (the first downstream projection 130a and the second downstream projection 130b being part of this). In such an example, the retraction of the first downstream projection 130a and the second downstream projection 130b from the through-hole 150 causes a simultaneous shift of the mouthpiece 102 by a distance corresponding to the same direction (e.g., downstream). Conversely, if the nicotine pod assembly 300 is inserted sufficiently to facilitate downstream engagement, the mouthpiece 102 springs back simultaneously with the first downstream projection 130a and the second downstream projection 130b. In addition to the elastic engagement by the first downstream projection 130a and the second downstream projection 130b, the distal end of the mouthpiece 102 is also configured to be biased (and relatively aligned with the pod outlet 304 to form a nicotine vapor airtight seal) relative to the nicotine pod assembly 300 when the nicotine pod assembly 300 is properly positioned within the through hole 150 of the device body 100.

[0094] Furthermore, the downstream engagement may generate an audible click and / or tactile feedback indicating that the nicotine pod assembly 300 is properly positioned within the through-hole 150 of the device body 100. When properly positioned, the nicotine pod assembly 300 is mechanically, electrically, and fluidly connected to the device body 100. Although non-limiting embodiments of this specification describe the upstream engagement of the nicotine pod assembly 300 occurring before the downstream engagement, it should be understood that the associated mating, activation, and / or electrical devices may be reversed so that the downstream engagement occurs before the upstream engagement.

[0095] Figure 20 is a perspective view of the nicotine pod assembly of Figure 19, without the connector module. Referring to Figure 20, the upstream end of the second housing portion 308 defines a cavity 310. As described above, the cavity 310 is configured to receive the connector module 320 (e.g., via a treadlock fit). In an exemplary embodiment, the cavity 310 is located between the first upstream recess 312a and the second upstream recess 312b, and also between the first activation pin 314a and the second activation pin 314b. When the connector module 320 is not present, the insert 342 (Figure 24) and the absorbent material 346 (Figure 25) are visible through the recessed opening of the cavity 310. The insert 342 is configured to hold the absorbent material 346. The absorbent material 346 is configured to absorb and hold the amount of nicotine prevapor formulation released from the nicotine storage when the nicotine pod assembly 300 is activated. The insert 342 and the absorbent material 346 are described in more detail herein.

[0096] Figure 21 is a perspective view of the connector module of Figure 19. Figure 22 is another perspective view of the connector module of Figure 21. Referring to Figures 21 and 22, the general framework of the connector module 320 includes a module housing 354 and a faceplate 366. Furthermore, the connector module 320 has multiple surfaces, including an outer surface and side surfaces, the outer surface being adjacent to the side surfaces. In an exemplary embodiment, the outer surface of the connector module 320 consists of the faceplate 366, the first power contact 324a, the second power contact 324b, and the upstream surface of the data contact 326. The side surfaces of the connector module 320 are part of the module housing 354. The side surfaces of the connector module 320 define the first module inlet 330 and the second module inlet 332. Furthermore, two lateral surfaces adjacent to the side surfaces (which are also part of the module housing 354) may include a rib structure (e.g., crush ribs) configured to facilitate interlocking when the connector module 320 is placed in the cavity 310 of the pod body. For example, each of the two lateral surfaces may include a pair of rib structures that are tapered away from the faceplate 366. As a result, the module housing 354 will have increased resistance through friction of the rib structures against the lateral walls of the cavity 310 when the connector module 320 is pressed into the cavity 310 of the pod body. When the connector module 320 is placed inside the cavity 310, the faceplate 366 may be substantially coplanar with the upstream end of the second housing portion 308. Also, the sides of the connector module 320 (defining the first module inlet 330 and the second module inlet 332) face the side walls of the cavity 310.

[0097] The faceplate 366 of the connector module 320 may have a grooved edge 328 that, in combination with the corresponding side of the cavity 310, defines the pod inlet 322. However, it should be understood that exemplary embodiments are not limited thereto. For example, the faceplate 366 of the connector module 320 may be configured alternatively to completely define the pod inlet 322. The side of the connector module 320 (defining the first module inlet 330 and the second module inlet 332) and the side wall of the cavity 310 (facing the side) define an intermediate space between them. The intermediate space is downstream of the pod inlet 322 and upstream of the first module inlet 330 and the second module inlet 332. Thus, in exemplary embodiments, the pod inlet 322 is in fluid communication with both the first module inlet 330 and the second module inlet 332 through the intermediate space. The first module inlet 330 may be larger than the second module inlet 332. In such cases, when incoming air is received by the pod inlet 322 during vaping, the first module inlet 330 may receive the primary flow of incoming air (e.g., a larger flow), while the second module inlet 332 may receive the secondary flow of incoming air (e.g., a smaller flow).

[0098] As shown in Figure 22, the connector module 320 includes a wick 338 configured to move a nicotine prevapor formulation to a heater 336. The heater 336 is configured to heat the nicotine prevapor formulation during vaping to generate nicotine vapor. The heater 336 may be mounted within the connector module 320 via a contact core 334. The heater 336 is electrically connected to at least one electrical contact of the connector module 320. For example, one end of the heater 336 (e.g., the first end) may be connected to a first power contact 324a, while the other end of the heater 336 (e.g., the second end) may be connected to a second power contact 324b. In exemplary embodiments, the heater 336 includes a folded heating element. In such cases, the wick 338 may have a planar configuration configured to be held by the folded heating element. When the connector module 320 is placed inside the cavity 310 of the pod body, the wick 338 is configured to be in fluid communication with the absorbent material 346 so that the nicotine prevapor formulation, which is located inside the absorbent material 346, moves to the wick 338 via capillary action (when the nicotine pod assembly 300 is activated).

[0099] Figure 23 is an exploded view relating to the core, heater, conductor, and contact core of Figure 22. Referring to Figure 23, the core 338 may be a fibrous pad or other structure having voids / gaps designed for capillary action. Furthermore, the core 338 may have a non-uniform hexagonal shape, but exemplary embodiments are not limited thereto. The core 338 may be manufactured in a hexagonal shape or cut into this shape from a larger sheet material. Because the lower part of the core 338 is tapered toward the winding portion of the heater 336, the possibility of the nicotine pre-vapor formulation becoming part of the core 338 that avoids continuous vaporization (due to its distance from the heater 336) can be reduced or avoided.

[0100] In an exemplary embodiment, the heater 336 is configured to be Joule heated (also known as ohm / resistive heating) when an electric current is applied thereto. More specifically, the heater 336 may be formed of one or more conductors and may be configured to generate heat when an electric current is passed through it. The electric current may be supplied from a power source (e.g., a battery) within the apparatus body 100 and may be transmitted to the heater 336 via a first power contact 324a or a first conductor 340a (or a second power contact 324b or a second conductor 340b).

[0101] Suitable conductors for the heater 336 include iron-based alloys (e.g., stainless steel) and / or nickel-based alloys (e.g., nichrome). The heater 336 may be made from a conductive sheet (e.g., metal, alloy) which is then stamped to cut a winding pattern. The winding pattern may have curved portions that alternate with horizontal portions, with the horizontal portions extending parallel to each other and zigzag back and forth. Furthermore, the width of each horizontal portion of the winding pattern may be approximately equal to the spacing between adjacent horizontal portions of the winding pattern, but exemplary embodiments are not limited thereto. To obtain the illustrated form of the heater 336, the winding pattern may be folded to grip a core 338.

[0102] The heater 336 can be fixed to the contact core 334 by a first conductor 340a and a second conductor 340b. The contact core 334 is formed from an insulating material and is configured to electrically insulate the first conductor 340a from the second conductor 340b. In an exemplary embodiment, the first conductor 340a and the second conductor 340b each define a female opening configured to engage with the corresponding male member of the contact core 334. The first and second ends of the heater 336, once engaged, can be fixed (e.g., welded, soldered, brazed) to the first conductor 340a and the second conductor 340b, respectively. The contact core 334 can then be placed in the corresponding socket of the module housing 354 (e.g., via interference mating). When the connector module 320 is assembled, the first conductor 340a electrically connects the first end of the heater 336 to the first power contact 324a, while the second conductor 340b electrically connects the second end of the heater 336 to the second power contact 324b. The heater and related structure are described in detail in U.S. Patent Application No. 15 / 729,909, filed October 11, 2017, entitled "Folded Heater For Electronic Vaping Device" (Atty. Dkt. No. 24000-000371-US), the entire contents of which are incorporated herein by reference.

[0103] Figure 24 is an exploded view relating to the first housing portion of the nicotine pod assembly of Figure 17. Referring to Figure 24, the first housing portion 302 includes a vapor channel 316. The vapor channel 316 is configured to receive vapor generated by the heater 336 and is in fluid communication with the pod outlet 304. In exemplary embodiments, the size (e.g., diameter) of the vapor channel 316 may gradually increase as it extends toward the pod outlet 304. Furthermore, the vapor channel 316 may be formed integrally with the first housing portion 302. The wrap 318, insert 342, and seal 344 are located at the upstream end of the first housing portion 302 and define the nicotine storage portion of the nicotine pod assembly 300. For example, the wrap 318 may be located on the rim of the first housing portion 302. The insert 342 may be placed within the first housing portion 302 such that the peripheral surface of the insert 342 engages with the inner surface of the first housing portion 302 along its edge (e.g., via a press fit) such that the interface between the peripheral surface of the insert 342 and the inner surface of the first housing portion 302 is fluid-tight (e.g., liquid-tight and / or airtight). Furthermore, the seal 344 may be attached to the upstream side of the insert 342 to seal the outlet of the storage portion of the insert 342, providing fluid-tight (e.g., liquid-tight and / or airtight) containment of the nicotine prevapor formulation into the nicotine storage portion.

[0104] In an exemplary embodiment, the insert 342 includes a holder portion protruding from the upstream side (shown in Figure 24) and a connector portion protruding from the downstream side (hidden in Figure 24). The holder portion of the insert 342 is configured to hold the absorbent material 346, while the connector portion of the insert 342 is configured to engage with the vapor channel 316 of the first housing portion 302. The connector portion of the insert 342 may be positioned within the vapor channel 316 and therefore configured to engage with the interior of the vapor channel 316. Alternatively, the connector portion of the insert 342 may be configured to receive the vapor channel 316 and therefore engage with the exterior of the vapor channel 316. The insert 342 also defines a storage outlet through which the nicotine pre-vapor formulation flows when the seal 344 is punctured during the activation of the nicotine pod assembly 300 (as shown in Figure 24). The holder portion and connector portion of the insert 342 may be located between the storage outlets (e.g., a first storage outlet and a second storage outlet), but exemplary embodiments are not limited thereto. Furthermore, the insert 342 defines vapor conduits extending through the holder portion and connector portion. As a result, when the insert 342 is placed within the first housing portion 302, the vapor conduits of the insert 342 are aligned with and fluidly communicated with the vapor channel 316, forming a continuous path through the nicotine storage to the pod outlet 304 for nicotine vapor generated by the heater 336 during vaping.

[0105] The seal 344 is attached to the upstream side of the insert 342 so as to cover the storage outlet of the insert 342. In an exemplary embodiment, the seal 344 defines an opening (e.g., a central opening) configured to provide a suitable gap to accommodate the holder portion (protruding from the upstream side of the insert 342) when the seal 344 is attached to the insert 342. It should be understood that in Figure 24, the seal 344 is shown in a perforated state. In particular, the two perforated portions of the seal 344 are pushed into the nicotine storage section as flaps (as shown in Figure 24) when perforated by the first activation pin 314a and the second activation pin 314b of the nicotine pod assembly 300, thus creating two perforated openings within the seal 344 (e.g., one on each side of the central opening). The size and shape of the perforated openings within the seal 344 may correspond to the size and shape of the storage outlet of the insert 342. In contrast, the seal 344, when perforated, has a planar shape and only one opening (e.g., a central opening). The seal 344 is designed to have sufficient strength to remain intact so as not to be torn prematurely or accidentally during normal movement and / or handling of the nicotine pod assembly 300. For example, the seal 344 may be a coated foil (e.g., titanium backed with aluminum).

[0106] Figure 25 is a partially exploded view relating to the second housing portion of the nicotine pod assembly of Figure 17. Referring to Figure 25, the second housing portion 308 is structured to contain various elements configured to release, receive, and heat the nicotine prevapor formulation. For example, the first activation pin 314a and the second activation pin 314b are configured to perforate the nicotine storage portion of the first housing portion 302 to release the nicotine prevapor formulation. Each of the first activation pin 314a and the second activation pin 314b has a distal end that extends through a corresponding opening in the second housing portion 308. In exemplary embodiments, the distal ends of the first activation pin 314a and the distal ends of the second activation pin 314b are visible after assembly (e.g., Figure 17), while the rest of the first activation pin 314a and the second activation pin 314b are hidden from view within the nicotine pod assembly 300. Furthermore, each of the first activation pin 314a and the second activation pin 314b has a proximal end that is positioned adjacent to and upstream of the seal 344 before activation of the nicotine pod assembly 300. When the first activation pin 314a and the second activation pin 314b are pushed into the second housing portion 308 to activate the nicotine pod assembly 300, the proximal ends of each of the first activation pin 314a and the second activation pin 314b advance through the insert 342, thereby perforating the seal 344, which releases the nicotine prevapor formulation from the nicotine storage portion. The movement of the first activation pin 314a may be independent of the movement of the second activation pin 314b (and vice versa). The first activation pin 314a and the second activation pin 314b are described in more detail herein.

[0107] Furthermore, as described above, the absorbent material 346 is configured to engage with the holder portion of the insert 342 (which protrudes from the upstream side of the insert 342, as shown in Figure 24). The absorbent material 346 may have an annular shape, but exemplary embodiments are not limited thereto. As shown in Figure 25, the absorbent material 346 may resemble a hollow cylindrical shape. In such cases, the outer diameter of the absorbent material 346 may be approximately equal to (or slightly larger than) the length of the core 338. The inner diameter of the absorbent material 346 may be smaller than the average outer diameter of the holder portion of the insert 342 to provide an interlocking fit. To facilitate engagement with the absorbent material 346, the tip of the holder portion of the insert 342 may be tapered. Furthermore, although not visible in Figure 25, the downstream side of the second housing portion 308 may define a cavity configured to receive and support the absorbent material 346. An example of such a cavity may be a circular chamber located downstream of the cavity 310, which is in fluid communication with the cavity 310. The absorbent material 346 is configured to receive and retain the amount of nicotine prevapor formulation released from the nicotine storage unit when the nicotine pod assembly 300 is activated.

[0108] The wick 338 is positioned within the nicotine pod assembly 300 to be in fluid communication with the absorbent material 346 so that the nicotine prevapor formulation can be drawn out from the absorbent material 346 to the heater 336 via capillary action. The wick 338 may be in physical contact with the upstream side of the absorbent material 346 (for example, the bottom of the absorbent material 346, based on the diagram shown in Figure 25). Furthermore, the wick 338 may be aligned with the diameter of the absorbent material 346, but exemplary embodiments are not limited thereto.

[0109] As shown in Figure 25 (and Figure 23 above), the heater 336 may have a folded configuration that grips opposing surfaces of the wick 338 and establishes thermal contact with it. The heater 336 is configured to heat the wick 338 during vaping to generate nicotine. To facilitate such heating, the first end of the heater 336 may be electrically connected to the first power contact 324a via the first conductor 340a, while the second end of the heater 336 may be electrically connected to the second power contact 324b via the second conductor 340b. As a result, current can be supplied from a power source (e.g., a battery) within the device body 100 and transmitted to the heater 336 via the first power contact 324a and the first conductor 340a (or the second power contact 324b and the second conductor 340b). The first conductor 340a and the second conductor 340b (shown separately in Figure 23) can be engaged with the contact core 334 (as shown in Figure 25). Relevant details of other embodiments of the connector module 320, configured to be placed within the cavity 310 of the second housing portion 308 (for example, in relation to Figures 21 and 22), as described above, are not repeated in this section for the sake of brevity. Nicotine generated by the heater 336 is drawn out during vaping through the vapor conduit of the insert 342, through the vapor channel 316 of the first housing portion 302, out of the pod outlet 304 of the nicotine pod assembly 300, through the vapor passage 136 of the mouthpiece 102, to one or more vapor outlets.

[0110] Figure 26 is an exploded view of the activation pin of Figure 25. Referring to Figure 26, the activation pin may take the form of a first activation pin 314a and a second activation pin 314b. Although two activation pins are illustrated and described in relation to the non-limiting embodiments herein, it should be understood that, alternatively, the nicotine pod assembly 300 may include only one activation pin. In Figure 26, the first activation pin 314a may include a first blade 348a, a first actuator 350a, and a first O-ring 352a. Similarly, the second activation pin 314b may include a second blade 348b, a second actuator 350b, and a second O-ring 352b.

[0111] In exemplary embodiments, the first blade 348a and the second blade 348b are configured to be attached to or fitted to the upper portions (e.g., proximal portions) of the first actuator 350a and the second actuator 350b, respectively. Attachment or fitting can be achieved via snap-fit ​​connections, interlocking (e.g., friction-fit) connections, adhesives, or other suitable bonding techniques. The upper portions of each of the first blade 348a and the second blade 348b may have one or more curved or concave edges that taper upward toward a pointed tip. For example, each of the first blade 348a and the second blade 348b may have two pointed tips with a concave edge between them, and a curved edge adjacent to each pointed tip. The radii of curvature of the concave and curved edges may be the same, while their arc lengths may differ. The first blade 348a and the second blade 348b may be formed from sheet metal (e.g., stainless steel) that is cut or otherwise shaped to have a desired profile and then bent into its final form. In another example, the first blade 348a and the second blade 348b may be formed from plastic.

[0112] Based on the plan view, the size and shape of the first blade 348a, the second blade 348b, and the parts of the first actuator 350a and the second actuator 350b on which they are mounted may correspond to the size and shape of the storage outlet of the insert 342. Furthermore, as shown in Figure 26, the first actuator 350a and the second actuator 350b may include protruding edges (e.g., curved inner lips facing each other) configured to push the two perforated sections of the seal 344 into the nicotine storage as the first blade 348a and the second blade 348b advance into the nicotine storage. In a non-limiting embodiment, when the first activation pin 314a and the second activation pin 314b are fully inserted into the nicotine pod assembly 300, the two flaps (from the two perforated portions of the seal 344, as shown in Figure 24) may be located between the curved side wall of the storage outlet of the insert 342 and the corresponding curves of the protruding edges of the first actuator 350a and the second actuator 350b. As a result, the possibility of the two perforated openings of the seal 344 being obstructed (by the two flaps from the two perforated portions) can be reduced or prevented. Furthermore, the first actuator 350a and the second actuator 350b may be configured to guide the nicotine prevapor formulation from the nicotine storage towards the absorbent material 346.

[0113] The lower portions (e.g., distal portions) of the first actuator 350a and the second actuator 350b are configured to extend through the bottom portion (e.g., upstream end) of the second housing portion 308. These rod-like portions of the first actuator 350a and the second actuator 350b can also be referred to as shafts. The first O-ring 352a and the second O-ring 352b may be placed in annular grooves within the shafts of the first actuator 350a and the second actuator 350b, respectively. The first O-ring 352a and the second O-ring 352b are configured to engage with the shafts of the first actuator 350a and the second actuator 350b, as well as the inner surfaces of the corresponding openings of the second housing portion 308, in order to provide a fluid-tight seal. As a result, when the first activation pin 314a and the second activation pin 314b are pushed inward to activate the nicotine pod assembly 300, the first O-ring 352a and the second O-ring 352b move together with the respective shafts of the first actuator 350a and the second actuator 350b within the corresponding openings of the second housing portion 308, while maintaining their respective seals, thereby helping to reduce or prevent leakage of the nicotine pre-vapor formulation through the openings of the second housing portion 308 to the first activation pin 314a and the second activation pin 314b. The first O-ring 352a and the second O-ring 352b may be formed of silicone.

[0114] Figure 27 is a perspective view of the connector module of Figure 22, excluding the core, heater, conductor and contact core. Figure 28 is an exploded view of the connector module of Figure 27. Referring to Figures 27 and 28, the module housing 354 and faceplate 366 generally form the external framework of the connector module 320. The module housing 354 defines a first module inlet 330 and a grooved edge 356. The grooved edge 356 of the module housing 354 exposes a second module inlet 332 (defined by the bypass structure 358). However, it should be understood that the grooved edge 356 can also be considered to define a module inlet (for example, in combination with the faceplate 366). The faceplate 366 has a grooved edge 328 that defines a pod inlet 322, together with the corresponding side of the cavity 310 of the second housing portion 308. Furthermore, the panel 366 defines a first contact opening, a second contact opening, and a third contact opening. The first and second contact openings may be square and configured to expose a first power contact 324a and a second power contact 324b, respectively, while the third contact opening may be rectangular and configured to expose a plurality of data contacts 326, but exemplary embodiments are not limited thereto.

[0115] The first power contact 324a, the second power contact 324b, the printed circuit board (PCB) 362, and the bypass structure 358 are arranged within an external framework formed by the module housing 354 and the faceplate 366. The printed circuit board (PCB) 362 includes a plurality of data contacts 326 on its upstream side (not visible in Figure 28) and a sensor 364 on its downstream side. The bypass structure 358 defines a second module inlet 332 and a bypass outlet 360.

[0116] The first power contact 324a and the second power contact 324b are positioned during assembly so that they are visible through the first and second contact openings of the faceplate 366, respectively. Furthermore, the printed circuit board (PCB) 362 is positioned so that its upstream data contacts 326 are visible through a third contact opening of the faceplate 366. The printed circuit board (PCB) 362 may also overlap the back surfaces of the first power contact 324a and the second power contact 324b. The bypass structure 358 is positioned on the printed circuit board (PCB) 362 so that the sensor 364 is within an airflow path defined by the second module inlet 332 and the bypass outlet 360. When assembled, the bypass structure 358 and the printed circuit board 362 can be considered to be surrounded on at least four sides by the meandering structure of the first power contact 324a and the second power contact 324b. In an exemplary embodiment, the bifurcated ends of the first power contact 324a and the second power contact 324b are configured to be electrically connected to the first conductor 340a and the second conductor 340b.

[0117] When incoming air is received by the pod inlet 322 during vaping, the first module inlet 330 may receive a primary flow of incoming air (e.g., a larger flow), while the second module inlet 332 may receive a secondary flow of incoming air (e.g., a smaller flow). The secondary flow of incoming air may improve the sensitivity of the sensor 364. The secondary flow exits the bypass structure 358 through the bypass outlet 360, then recombines with the primary flow to form a combined flow drawn into the contact core 334, so as to encounter the heater 336 and the core 338. In a non-limiting embodiment, the primary flow rate may be 60-95% (e.g., 80-90%) of the incoming air, while the secondary flow rate may be 5-40% (e.g., 10-20%) of the incoming air.

[0118] The first module inlet 330 may be a draw-out resistance (RTD) port, while the second module inlet 332 may be a bypass port. In such a configuration, the draw-out resistance of the nicotine e-vaping device 500 can be adjusted by changing the size of the first module inlet 330 (rather than changing the size of the pod inlet 322). In an exemplary embodiment, the size of the first module inlet 330 may be selected such that the draw-out resistance is 25 to 100 millimeters of water column (e.g., 30 to 50 millimeters of water column). For example, a diameter of 1.0 mm for the first module inlet 330 may result in a draw-out resistance of 88.3 millimeters of water column. In another example, a diameter of 1.1 mm for the first module inlet 330 may result in a draw-out resistance of 73.6 millimeters of water column. In yet another example, a diameter of 1.2 mm for the first module inlet 330 may result in a draw-out resistance of 58.7 millimeters of water column. In another example, a 1.3 mm diameter of the first module inlet 330 can result in a draw resistance of 43.8 millimeters of water column. In particular, the size of the first module inlet 330 can be adjusted for its internal placement without affecting the external aesthetics of the nicotine pod assembly 300, thereby enabling a more standardized product design of pod assemblies with varying draw resistances (RTDs), while also reducing the possibility of accidental blockage of incoming air.

[0119] Figure 29 shows the electrical system of the device body and nicotine pod assembly of an exemplary embodiment of a nicotine e-vaping device.

[0120] Referring to Figure 29, the electrical system includes the electrical system 2100 of the device body and the electrical system 2200 of the nicotine pod assembly. The electrical system 2100 of the device body may be included in the device body 100, and the electrical system 2200 of the nicotine pod assembly may be included in the nicotine pod assembly 300 of the nicotine e-vaping device 500 described with respect to Figures 1-28.

[0121] In the exemplary embodiment shown in Figure 29, the electrical system 2200 of the nicotine pod assembly includes a heater 336, one or more pod sensors 2220, and a non-volatile memory (NVM) 2205. The NVM 2205 may be an electrically erasable programmable read-only memory (EEPROM) integrated circuit (IC).

[0122] The electrical system 2200 of the nicotine pod assembly may further include an electrical / data interface (not shown) of the body for transferring power and / or data between the device body 100 and the nicotine pod assembly 300. According to at least one exemplary embodiment, the electrical contacts 324a, 324b and 326 shown in Figure 17 may function, for example, as an electrical / data interface of the body.

[0123] The electrical system 2100 of the device body includes a control device 2105, a power supply 2110, a device sensor or measuring circuit 2125 (hereinafter referred to as the device sensor 2125), a heating engine control circuit (also referred to as the heating engine shut-off circuit) 2127, a vapor indicator 2135, an in-product control device 2150 (e.g., buttons 118 and 120 shown in Figure 1), a memory 2130, and a clock circuit 2128. The electrical system 2100 of the device body may further include a pod electrical / data interface (not shown) for transferring power and / or data between the device body 100 and the nicotine pod assembly 300. According to at least one exemplary embodiment, for example, the device's electrical connector 132 shown in Figure 12 may function as the pod's electrical / data interface.

[0124] The power supply 2110 may be an internal power supply for supplying power to the device body 100 and nicotine pod assembly 300 of the nicotine e-vaping device 500. The power supply from the power supply 2110 may be controlled by a control device 2105 via a power control circuit (not shown). The power control circuit may include one or more switches or transistors for adjusting the power output from the power supply 2110. The power supply 2110 may be a lithium-ion battery or another form thereof (e.g., a lithium-ion polymer battery). The power supply 2110 may be connected to a charger 2132 for charging (also referred to herein as a power supply charger or battery charger). Exemplary embodiments of the power supply charger 2132 are described in detail below with respect to Figures 44A and 44B.

[0125] The control device 2105 may be configured to control the overall operation of the nicotine e-vaping device 500. According to at least some exemplary embodiments, the control device 2105 may include processing circuits such as hardware including logic circuits, a combination of hardware / software such as a processor that runs software, or a combination thereof. More specifically, the processing circuits include, but are 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), and the like.

[0126] In the exemplary embodiment shown in Figure 29, the control device 2105 includes general-purpose input / output (GPIO) and inter-integrated circuit communication (I 2 C) Interfaces may include input / output interfaces such as a serial peripheral interface bus (SPI) interface, a multi-channel analog-to-digital converter (ADC), and a clock input terminal. However, exemplary embodiments should not be limited to this embodiment. In at least one exemplary implementation, the control device 2105 may be a microprocessor.

[0127] The control unit 2105 is communicatively coupled to the device sensor 2125, the heating engine control circuit 2127, the vapor indicator 2135, the memory 2130, the in-product control unit 2150, the clock circuit 2128, and the power supply 2110. The control unit 2105 may also be communicatively coupled to the charger 2132 (for example, via a Universal Serial Bus (USB) connection) when charging the power supply 2110.

[0128] The heating engine control circuit 2127 is connected to the control unit 2105 via GPIO pins. The memory 2130 is connected to the control unit 2105 via SPI pins. The clock circuit 2128 is connected to the clock input pin of the control unit 2105. The vapor indicator 2135 is I 2 The device sensor 2125 is connected to the control unit 2105 via C interface pins and GPIO pins. The elements of the device sensor 2125 are connected to the control unit 2105 via the respective pins of the multi-channel ADC. The power charger 2132 may also be connected to the control unit 2105 via GPIO pins, if connected.

[0129] The clock circuit 2128 may be a timing mechanism such as an oscillator circuit, enabling the control device 2105 to track the idle time of the nicotine e-vaping device 500, the reset time via the reset timer, the vapor length, the measurement interval, a combination thereof, or similar. The clock circuit 2128 may also include a dedicated external clock crystal configured to generate a system clock for the nicotine e-vaping device 500.

[0130] Memory 2130 may be a non-volatile memory configured to store one or more blockage (or failure event) logs. In one embodiment, memory 2130 may store one or more blockage logs in one or more tables. Memory 2130 and the one or more blockage logs stored therein will be described in more detail later. In one embodiment, memory 2130 may be an electrically erasable programmable read-only memory (EEPROM), such as flash memory or similar.

[0131] Referring further to Figure 29, the device sensor 2125 may include a plurality of sensors or measuring circuits configured to provide the control device 2105 with measured values ​​or signals indicating sensor or measurement information. In the embodiment shown in Figure 29, the device sensor 2125 includes a heater current measuring circuit 21258, a heater voltage measuring circuit 21252, a pod temperature measuring circuit 21250, a power supply temperature measuring circuit 21254, and a power supply voltage measuring circuit 21256.

[0132] The heater current measurement circuit 21258 may be configured to output a signal (e.g., voltage) indicating the current passing through the heater 336. Exemplary embodiments of the heater current measurement circuit 21258 will be described in more detail later with respect to Figure 35.

[0133] The heater voltage measurement circuit 21252 may be configured to output a signal (e.g., voltage) indicating the voltage across the heater 336. Exemplary embodiments of the heater voltage measurement circuit 21252 will be described in more detail later with respect to Figure 34.

[0134] The pod temperature measurement circuit 21250 may be configured to output a signal (e.g., voltage) indicating the resistance and / or temperature of one or more elements of the nicotine pod assembly 300. Exemplary embodiments of the pod temperature measurement circuit 21250 will be described in more detail later with respect to Figures 36 and 37.

[0135] The power supply temperature measurement circuit 21254 may be configured to measure the temperature of the power supply 2110 during operation and / or charging. Exemplary forms of the power supply temperature measurement circuit 21254 will be described in more detail later with respect to Figures 42A and 42B.

[0136] The power supply voltage measurement circuit 21256 may be configured to output a signal indicating the voltage of the power supply 2110 during operation and / or charging. Exemplary embodiments of the power supply voltage measurement circuit 21256 will be described in more detail later with respect to Figures 43A and 43B.

[0137] As described above, the pod temperature measurement circuit 21250, heater current measurement circuit 21258, heater voltage measurement circuit 21252, power supply temperature measurement circuit 21254, and power supply voltage measurement circuit 21256 are connected to the control unit 2105 via the pins of the multi-channel ADC. To measure the characteristics and / or parameters of the nicotine e-vaping device 500 (e.g., voltage, current, resistance, temperature of the heater 336), the multi-channel ADC in the control unit 2105 can sample the output signals from the device sensors 2125 at an appropriate sampling rate for a given characteristic and / or parameter measured by each device sensor.

[0138] As shown in Figure 29, the pod sensor 2220 also includes the sensor 364 shown in Figure 28. In at least one exemplary embodiment, the sensor 364 may be a micro-electromechanical system (MEMS) flow or pressure sensor, or another type of sensor configured to measure airflow, such as a hot-wire anemometer.

[0139] The heating engine control circuit 2127 is connected to the control unit 2105 via GPIO pins. The heating engine control circuit 2127 is configured to control (enable and / or disable) the heating engine of the nicotine e-vaping device 500 by controlling the power to the heater 336. As will be described in more detail later, the heating engine control circuit 2127 may disable the heating engine based on a control signal from the control unit 2105 (which may be referred to herein as the device power status signal).

[0140] When the nicotine pod assembly 300 is inserted into the device body 100, the control device 2105 also 2 The controller is communicatively coupled to at least the NVM2205 and the pod sensor 2220 via a C interface. In one embodiment, the control unit 2105 may obtain operating parameters for the electrical system 2200 of the nicotine pod assembly from the NVM2205.

[0141] The control device 2105 may control a vapor indicator 2135 to show the status, fault events, and / or operation of the nicotine e-vaping device 500 to an adult vaper. The vapor indicator 2135 may include a power indicator (e.g., an LED) which may be at least partially implemented via a light guide (e.g., the light guide device shown in Figure 1) and which can be activated when the control device 2105 senses a button pressed by an adult vaper. The vapor indicator 2135 may also include a vibrator, speaker, display device, or other feedback mechanism which may indicate the current state of vaping parameters (e.g., nicotine vapor volume) controlled by the adult vaper.

[0142] Referring further to Figure 29, the control device 2105 may control the power to the heater 336 to heat the nicotine prevapor formulation according to a heating profile (e.g., heating based on volume, temperature, flavor, etc.). The heating profile may be determined based on empirical data and stored in the NVM 2205 of the nicotine pod assembly 300.

[0143] Figure 30 is a simplified block diagram showing an automatic shutoff control system 2300 according to an exemplary embodiment.

[0144] The automatic shutdown control system 2300 shown in Figure 30 may be implemented in the control unit 2105. In one embodiment, the automatic shutdown control system 2300 may be implemented as part of the device manager finite state machine (FSM) software implementation in the control unit 2105. In the embodiment shown in Figure 30, the automatic shutdown control system 2300 includes a fault detection subsystem 2630 and an automatic shutdown decision subsystem 2650. However, it should be understood that the automatic shutdown control system 2300 may include various other subsystems.

[0145] Referring to Figure 30, the automatic shut-off control system 2300, and more generally, the control device 2105, can detect a fault event (or state) in the nicotine e-vaping device 500 and cause the control device 2105 to control one or more subsystems of the nicotine e-vaping device 500 to perform one or more resulting actions in response to detecting the fault event. As will be described in more detail later, types of fault events may include normal (fault) events, soft fault pod events, hard fault pod events, soft fault device events, and hard fault device events.

[0146] Normal events may include, for example, the event of the power supply (or battery) being fully charged (charge complete event), the adult vapor input event (e.g., via the in-product control device 2150), the insertion of the electrical system 2200 of the nicotine pod assembly, the idling event (or idling failure event), or a combination thereof. More generally, for example, a normal event may be a normal state of the nicotine e-vaping device 500 in which vaping or other functions of the nicotine e-vaping device 500 cannot be disabled.

[0147] A soft fault pod event may include, for example, a heater temperature fault event in which the temperature of the heater 336 exceeds a threshold value. More generally, a soft fault pod event may be an abnormal condition within the nicotine pod assembly 300 in which a resulting action (e.g., disabled vaping) occurs and adult vapor interaction with the nicotine electronic vaping device 500 does not need to be corrected.

[0148] A hard fault pod event may include an open-circuit failure of the heater 336, depletion of the nicotine pre-vapor formulation in the nicotine pod assembly 300 (empty pod), a combination thereof, or similar. More generally, for example, a hard fault pod event may be an abnormal condition in the nicotine pod assembly 300 that results in an effect (e.g., a deactivated vapor) and requires correction of the adult vapor interaction with the nicotine electronic vaping device 500.

[0149] Examples of soft fault device events include startup failures and power supply undervoltage fault events, where the voltage of the power supply 2110 falls below a threshold minimum (e.g., the power supply is depleted and requires recharging). Power supply undervoltage fault events may also be referred to herein as power supply (or battery) undervoltage fault or battery undervoltage fault event. More generally, for example, a soft fault device event may be an abnormal condition in the nicotine e-vaping device 500 where vaping is disabled until a corrective action is performed.

[0150] Examples of hardware failure events include charging failures and power stage failures of the power supply (or battery) in the charger 2132, which will be described in more detail later. More generally, for example, a hardware failure event may be an abnormal condition in the nicotine e-vaping device 500, which at least disables vaping and requires improvement of adult vaper intervention.

[0151] The control unit 2105 may control one or more subsystems by outputting (or asserting or deasserting) one or more control signals, as will be described in more detail later. In some cases, the control signals output from the control unit 2105 may be referred to as device power status signals, device power status commands, or device power control signals. According to one or more exemplary embodiments, in response to detecting one or more fault events in the nicotine e-vaping device 500, the control unit 2105 may output one or more control signals to the heating engine control circuit 2127 to cut off power to the heater 336, and / or output one or more control signals to the charger 2132 to shut off the vaping function in the nicotine e-vaping device 500, and / or perform a charge stop operation.

[0152] According to one or more exemplary embodiments, the type of resulting action in the nicotine e-vaping device 500 may depend on the identified fault event and / or the current operation of the nicotine e-vaping device. Multiple resulting actions may be performed sequentially in response to the fault event. In one embodiment, the resulting actions are:

[0153] The Nicotine e-Vaping Device 500 has an automatic shut-off function that switches to a low-power state (equivalent to, for example, turning off the Nicotine e-Vaping Device using the power button),

[0154] The heater-off operation cuts off or disables power to heater 336, ending the current vapor extraction, but otherwise leaving it ready for vaping.

[0155] The vaping subsystem is disabled (for example, by disabling all power to heater 336), thereby preventing vaping until a corrective action is performed (for example, recharging the power supply, replacing the nicotine pod assembly, etc.), in a vaping-off operation.

[0156] The Nicotine e-Vaping device software is reset via a device soft reset to clear any malfunctions and return the Nicotine e-Vaping device to its known normal operating state.

[0157] A hard reset of the device is performed to reset the device software and hardware, clearing fault events and returning the nicotine e-vaping device to a known normal operating state.

[0158] This includes stopping the charger, which will not restart until the power charging process is stopped and a corrective action is performed.

[0159] Referring further to Figure 30, in a more specific embodiment, the fault detection subsystem 2630, and more generally, the control device 2105, may detect an idling event in the nicotine e-vaping device 500 and, in response to the idling event, output one or more control signals (or assert or deassert each signal) to cause the nicotine e-vaping device 500 to perform one or more resulting actions. The fault detection subsystem 2630 may determine whether an idling event has occurred based on whether the cutoff timer has elapsed, whether a software timer is running in the device's firmware, whether any software event is in a software queue awaiting processing (e.g., a communication message from an external device via wired or wireless communication), whether any hardware operation (e.g., direct memory access (DMA) processing) is ongoing, or a combination thereof. If these checks return false values, the fault detection subsystem 2630 may output an idling alarm (or idling event alarm) to the automatic shutdown decision subsystem 2650 in response to the automatic shutdown decision subsystem 2650 being able to cause the nicotine e-vaping device 500 to enter a low-power state by disabling one or more subsystems of the nicotine e-vaping device 500. In one embodiment, the automatic shutdown decision subsystem 2650 (or more generally, the control unit 2105) may output a number of GPIO control lines (signals) to turn off all or nearly all peripherals of the nicotine e-vaping device 500 and cause the control unit 2105 to enter a sleep state.

[0160] Functions and / or operations according to one or more exemplary embodiments may be described herein with respect to being performed by the control unit 2105, the fault detection subsystem 2630, and / or the automatic shutdown decision subsystem 2650 in a particular context. However, it should be understood that functions and / or operations described with respect to the control unit 2105 may be described interchangeably as being performed by the fault detection subsystem 2630 and / or the automatic shutdown decision subsystem 2650. Similarly, it should be understood that functions and / or operations described with respect to the fault detection subsystem 2630 and / or the automatic shutdown decision subsystem 2650 may be described interchangeably as being performed by the control unit 2105.

[0161] Figure 31 is a flowchart illustrating a method for detecting an idling event according to an exemplary embodiment. The flowchart in Figure 31 represents a single iteration of the process for idling detection. The fault detection subsystem 2630 may perform this process continuously and / or periodically to determine whether to perform the resulting action, such as causing the nicotine e-vaping device 500 to enter a low-power sleep state.

[0162] For illustrative purposes, the flowchart shown in Figure 31 describes the electrical system shown in Figure 29. However, it should be understood that the exemplary embodiment should not be limited to this embodiment. Rather, the exemplary embodiment may be applicable to other nicotine e-vaping devices and their electrical systems. Furthermore, the exemplary embodiment shown in Figure 31 describes the operation performed by the fault detection subsystem 2630. However, it should be understood that the exemplary embodiment may similarly describe the automatic shut-off control system 2300 and / or control device 2105 that perform one or more of the functions / operations shown in Figure 31.

[0163] Referring to Figure 31, in step S3100, the fault detection subsystem 2630 schedules an idle task for the nicotine e-vaping device 500 to output an idle alarm to the automatic shut-off decision subsystem 2650 while the software timer, hardware driver, and software queue in the nicotine e-vaping device 500 are checked.

[0164] In step S3102, the fault detection subsystem 2630 checks the foreground software timers on the control unit 2105 and determines whether any foreground software timers are currently running. According to one or more exemplary embodiments, a foreground software timer is started each time a software module of the nicotine e-vaping device 500 starts an operational state. The fault detection subsystem 2630 determines that a foreground software timer is running if the foreground software timer has not elapsed (counted down to zero) or has been interrupted by the respective software module (operational state completed).

[0165] An example of a foreground timer in a special case is a timer used to monitor adult vaper interaction with the Nicotine e-vaping device 500. This may be referred to as the “device off” software timer and may be used to determine the length of time since the adult vaper last interacted with the Nicotine e-vaping device 500. This timer may correspond to the time (e.g., seconds or minutes) until the Nicotine e-vaping device 500 automatically enters a low-power state or shuts off. The timer may be set to a value specified by the adult vaper (e.g., via the in-product control unit 2150, the connected application “app”, or a combination thereof, or similar). The timer may count down in millisecond increments and may be restarted each time the adult vaper interacts with the Nicotine e-vaping device 500. In at least one exemplary embodiment, adult vaper interactions that can restart the foreground timer and keep the device awake (for example, preventing the device from entering a low-power state) include pressing a button on the Nicotine e-vaping device 500, vaping, inserting the Nicotine Pod Assembly 300, disconnecting the Nicotine e-vaping device 500 from the USB cable, or a combination thereof.

[0166] If one or more foreground software timers are running (step S3104), the fault detection subsystem 2630 interrupts the scheduled idle task and does not output an idle alarm to the automatic shut-off decision subsystem 2650. In this case, the nicotine e-vaping device 500 remains in an alert state ready for vaping.

[0167] Returning to step S3104, if the foreground software timers are not running (for example, all foreground software timers have elapsed or been interrupted), in step S3108, the fault detection subsystem 2630 checks the hardware drivers on the control unit 2105 to determine whether any hardware operation (for example, a DMA transaction) is being performed on the nicotine e-vaping device 500.

[0168] Each time a hardware operation begins, the driver software for that operation sets a busy flag and registers itself as "busy." The driver software then sets itself as "idle" (resetting the busy flag) when the hardware operation is complete (for example, when an interrupt is received or data processing is completed). Therefore, the fault detection subsystem 2630 can determine whether any hardware operation is currently ongoing by checking whether the busy flag for the hardware operation is set.

[0169] If the fault detection subsystem 2630 determines that one or more hardware operations are in progress in step S3110 (for example, a busy flag is set for at least one hardware driver), the process proceeds to step S3106 and continues as described above.

[0170] Returning to step S3110, if the fault detection subsystem 2630 determines that no hardware operation is currently running (e.g., the busy flag is not set), in step S3112, the fault detection subsystem 2630 checks the software queue for events waiting to be processed by the control unit 2105. According to one or more exemplary embodiments, the control unit 2105 may schedule events to be executed in the software queue in response to communication messages from an external device, for example, via wired (e.g., Universal Serial Bus (USB)) and / or wireless (e.g., short-range wireless such as Bluetooth®) communication.

[0171] According to at least one exemplary embodiment, a software queue check, such as the one performed in step S3112, may be performed as a task in a real-time operating system (RTOS) running on the control unit 2105.

[0172] If the fault detection subsystem 2630 determines that an event exists in the software queue waiting for processing in step S3114, the process proceeds to step S3106 and continues as described above.

[0173] Returning to step S3114, if the fault detection subsystem 2630 determines that there are no software events waiting to be processed, the fault detection subsystem 2630 outputs an idle alarm to the automatic shutdown decision subsystem 2650 indicating that an idle event has occurred. In response to the idle alarm, the automatic shutdown decision subsystem 2650 may determine one or more resulting actions to be performed and may control the nicotine e-vaping device 500 by outputting one or more device power status signals in order to perform one or more resulting actions. Exemplary operation of the automatic shutdown decision subsystem 2650 in response to fault alarms such as the idle alarm described above is described in more detail below with respect to Figures 33A and 33B.

[0174] Returning to Figure 30, in another embodiment, the fault detection subsystem 2630 may detect and / or determine when the temperature of the heater 336 reaches or exceeds (or becomes greater than) a threshold maximum temperature value (Heater_Max_TemperatureThresholdParameter) (heater temperature fault event), and in response, output a temperature alarm to the automatic shut-off decision subsystem 2650.

[0175] The fault detection subsystem 2630 may determine whether to output a temperature alarm based on the temperature and confidence interval (CI) of the heater 336. The threshold maximum temperature value and CI may be determined based on empirical data and may be stored and retrieved from the NVM 2205 in the nicotine pod assembly electrical system 2200. The temperature of the heater 336 (or a signal indicating the temperature of the heater 336) may be provided, for example, by a temperature sensing transducer component of the pod sensor 2220.

[0176] In another embodiment, the control device 2105 may determine the temperature of the heater 336 based on voltage measurements from the heater voltage measurement circuit 21252 and / or current measurements from the heater current measurement circuit 21258.

[0177] CI is the level of engineering margin for the temperature of the heater 336. For resistance-based measurements of the heater 336, temperature estimates can be relatively inaccurate due to tolerances of components, rounding errors, variable contact resistance, etc. Therefore, the error in the theoretical worst-case scenario can be applied as CI. In at least one exemplary embodiment, the error in the worst-case scenario may be about 15°C.

[0178] Regarding pod sensor-based measurements, the CI for estimating the temperature of heater 336 may be larger (e.g., on the order of approximately 50 to 100 degrees) because the pod sensor cannot be in close proximity to heater 336, and therefore the temperature of heater 336 may be inferred rather than estimated. According to at least one exemplary embodiment, the pod sensor-based measurement may be used as a measure of the enclosure temperature (e.g., only as such) rather than the heater itself, and the cutoff point from this reading was dedicated to preventing the temperature of the pod body from rising beyond a maximum threshold.

[0179] Figure 32A is a flowchart showing a method for detecting heater temperature-related problems according to an exemplary embodiment.

[0180] For illustrative purposes, the flowchart shown in Figure 32A describes the electrical system shown in Figure 29. However, it should be understood that the exemplary embodiment should not be limited to this embodiment. Rather, the exemplary embodiment may be applicable to other nicotine e-vaping devices and their electrical systems. Furthermore, the exemplary embodiment shown in Figure 32A primarily describes the operations performed by the fault detection subsystem 2630. However, it should be understood that the exemplary embodiment may similarly describe the automatic shut-off control system 2300 and / or control device 2105 that perform one or more of the functions / operations shown in Figure 32A.

[0181] Referring to Figure 32A, when the nicotine pod assembly 300 is inserted into the device body 100, in step S2902, the fault detection subsystem 2630 obtains a threshold maximum temperature value from the NVM 2205 of the nicotine pod assembly electrical system 2200. In one embodiment, the threshold maximum temperature value may be stored in a single byte with a resolution of about 2°C and may be in the range of about 0°C to about 510°C.

[0182] According to at least one exemplary embodiment, the temperature was stored with a resolution of about 2°C to fit a useful range in a single byte. Since the required range, according to at least one exemplary embodiment, covers at least about 0 to 300°C, a temperature stored with a resolution of about 1°C would not fit in a single byte (which would, for example, only provide the range of 0 to 255°C).

[0183] In step S2904, the fault detection subsystem 2630 determines whether vaping conditions are present in the nicotine e-vaping device 500. According to at least one exemplary embodiment, the fault detection subsystem 2630 may determine whether vaping conditions are present in the nicotine e-vaping device 500 based on the output from the sensor 364. In one embodiment, if the output from the sensor 364 indicates the application of a negative pressure exceeding a threshold at the mouthpiece 102 of the nicotine e-vaping device 500, the fault detection subsystem 2630 may determine that vaping conditions are present in the nicotine e-vaping device 500.

[0184] If the fault detection subsystem 2630 determines that vaping conditions are present in the nicotine e-vaping device 500, in step S2905, the control device 2105 controls the heating engine control circuit 2127 to apply power to the heater 336 for the vapor. Exemplary control of the heating engine control circuit 2127 for applying power to the heater 336 will be described in more detail later with respect to Figures 38 and 39.

[0185] In step S2906, the fault detection subsystem 2630 determines whether the resistance of the heater 336 has stabilized. The fault detection subsystem 2630 may determine that the resistance of the heater 336 has stabilized once the current passing through the heater 336 reaches a "wet" current threshold (for example, about 100 milliamperes (mA)). The fault detection subsystem 2630 may determine that the current passing through the heater 336 has reached the "wet" current threshold based on the output signal from the heater current measurement circuit 21258.

[0186] If the fault detection subsystem 2630 determines that the resistance of the heater 336 has stabilized, in step S2910, the fault detection subsystem 2630 estimates the temperature of the heater 336 based on the measured resistance of the heater 336. The fault detection subsystem 2630 may estimate the temperature of the heater 336 in any known way (for example, based on a relatively linear relationship between the resistance and temperature of the heater 336). In one embodiment, as will be described in more detail later, the fault detection subsystem 2630 may determine the temperature measurement based on the output from the temperature sensing transducer component of the pod sensor 2220.

[0187] Referring further to Figure 32A, in step S2912, the fault detection subsystem 2630 determines whether the estimated temperature of the heater 336 is equal to or greater than (reached or exceeded) the threshold maximum temperature by comparing the estimated temperature with the threshold maximum temperature value obtained from the NVM 2205.

[0188] If the fault detection subsystem 2630 determines that the estimated temperature of the heater 336 is below the threshold maximum temperature, in step S2916 the fault detection subsystem 2630 determines whether the measurement interval has ended. The measurement interval may be determined based on empirical data. In one embodiment, the measurement interval may be about 10 milliseconds.

[0189] According to at least one exemplary embodiment, a 10-millisecond measurement interval may be used for measurements acquired from an I2C pod sensor (as this may be the maximum sample rate). However, in at least one other exemplary embodiment, a 1-millisecond measurement interval (the system's tick rate) may be used for resistance-based heater measurements.

[0190] Once the measurement interval is complete, the process returns to step S2910 and continues as described herein.

[0191] Returning to step S2916, if the measurement interval has not yet ended, the fault detection subsystem 2630 waits for the measurement interval to end, then returns to step S2910 and continues as described herein.

[0192] Returning to step S2912, if the fault detection subsystem 2630 determines that the estimated temperature of the heater 336 has reached or exceeded the threshold maximum temperature value, in step S2914, the fault detection subsystem 2630 outputs a heater temperature fault event alarm to the automatic shut-off decision subsystem 2650.

[0193] Returning to step S2906, if the fault detection subsystem 2630 determines that the resistance of the heater 336 is not yet stable, the fault detection subsystem 2630 continues to monitor (or wait for) the resistance of the heater 336. Once the resistance of the heater 336 stabilizes, the process proceeds to step S2910 and continues as described above.

[0194] Returning to step S2904, if the fault detection subsystem 2630 determines that no vaping conditions exist for the nicotine e-vaping device 500, the fault detection subsystem 2630 continues to monitor the output of sensor 364 for the presence of nicotine e-vaping conditions. Once nicotine e-vaping conditions are detected, the process continues as described above.

[0195] Figure 32B is a flowchart showing a method for detecting a heater temperature disturbance event according to another exemplary embodiment. The method shown in Figure 32B may enable the nicotine e-vaping device 500 to determine whether to apply power to the heater 336 at the start of a vapor inhalation event (for example, when negative pressure is initially applied to the mouthpiece 102).

[0196] Similar to the exemplary embodiment shown in Figure 32A, the flowchart shown in Figure 32B is illustrated for illustrative purposes with respect to the electrical system shown in Figure 29. However, it should be understood that the exemplary embodiment should not be limited to this embodiment. Rather, the exemplary embodiment may be applicable to other nicotine e-vaping devices and their electrical systems. Furthermore, the exemplary embodiment shown in Figure 32B primarily describes the operations performed by the fault detection subsystem 2630. However, it should be understood that the exemplary embodiment may similarly describe the automatic shut-off control system 2300 and / or control device 2105 that perform one or more of the functions / operations shown in Figure 32B.

[0197] Referring to Figure 32B, when the nicotine pod assembly 300 is inserted into the device body 100, in step S3000, the fault detection subsystem 2630 obtains the threshold maximum temperature value from the NVM 2205 of the nicotine pod assembly electrical system 2200. The threshold maximum temperature value may be the same or substantially the same as that described above with respect to step S2902 in Figure 32A.

[0198] In step S3002, the fault detection subsystem 2630 determines whether the vaping conditions are present in the nicotine e-vaping device 500. With respect to step S2904 in Figure 32A, the fault detection subsystem 2630 may determine whether the vaping conditions are present in the nicotine e-vaping device 500 in the same or substantially the same manner as described above.

[0199] If the fault detection subsystem 2630 detects the presence of vaping conditions in step S3002, in step S3004, the fault detection subsystem 2630 estimates the temperature of the heater 336 based on information from the components of the temperature sensing transducer of the pod sensor 2220. With respect to step S2910 in Figure 32A, the fault detection subsystem 2630 may estimate the temperature of the heater 336 in the same or substantially the same manner as described above.

[0200] In step S3006, the fault detection subsystem 2630 determines whether the estimated temperature is, for example, greater than or equal to the threshold maximum temperature value obtained from the NVM2205 by comparing the estimated temperature with the threshold maximum temperature value obtained from the NVM2205. The threshold maximum temperature value obtained from the NVM2205 may be the same as or substantially the same as the one described above with respect to Figure 32A.

[0201] If the fault detection subsystem 2630 determines that the estimated temperature exceeds the threshold maximum temperature value, in step S3008, the fault detection subsystem 2630 outputs a heater temperature fault event alarm to the automatic shut-off decision subsystem 2650, and the process terminates.

[0202] Returning to step S3006, if the fault detection subsystem 2630 determines that the estimated temperature does not exceed the threshold maximum temperature value, the fault detection subsystem 2630 does not need to output a heater temperature fault event alarm to the fault detection subsystem 2630, and the control device 2105 can apply power to the heater 336 in step S3010.

[0203] Figures 33A and 33B show an automatic shutoff control method according to one or more exemplary embodiments.

[0204] For illustrative purposes, the flowcharts shown in Figures 33A and 33B describe the electrical system shown in Figure 29. However, it should be understood that the exemplary embodiment should not be limited to this embodiment. Rather, the exemplary embodiment may be applicable to other nicotine e-vaping devices and their electrical systems. Furthermore, the exemplary embodiment shown in Figures 33A and 33B primarily describes the operations performed by the automatic shut-off decision subsystem 2650. However, it should be understood that the exemplary embodiment may similarly describe the automatic shut-off control system 2300 and / or control device 2105 that perform one or more of the functions / operations shown in Figures 33A and 33B.

[0205] Referring to Figures 33A and 33B, in step S3702, the automatic shutdown decision subsystem 2650 determines whether a fault event has occurred in the nicotine e-vaping device 500. According to one or more exemplary embodiments, the automatic shutdown decision subsystem 2650 determines that a fault event has occurred in response to receiving a fault alarm from the fault detection subsystem 2630.

[0206] If the automatic shutdown decision subsystem 2650 determines that a fault event has occurred, in step S3704, the automatic shutdown decision subsystem 2650 classifies the fault event as one of the following: a normal fault event, a soft fault pod event, a hard fault pod event, a soft fault device event, or a hard fault device event. According to one or more exemplary embodiments, the automatic shutdown decision subsystem 2650 may classify the fault event using a lookup table that stores fault event classifications in relation to a specific fault event and / or fault error code associated with it. In this embodiment, the fault detection subsystem 2630 may output a display of the fault event that triggered a fault alarm to be sent to the automatic shutdown decision subsystem 2650.

[0207] In at least one exemplary embodiment, the classification may be carried out using a “switch” programming statement to select the type of fault based on an enumerated value of the faults.

[0208] Similarly, as described above, normal failure events may include an interrupt from the charger 2132 indicating that charging of the power supply 2110 is complete, an adult vapor input via the in-product control device 2150 (for example, to shut off the vaping subsystem or nicotine e-vaping device), an idling event in which the nicotine e-vaping device 500 remains idle for at least a threshold time interval (for example, as described above with respect to Figure 31), and combinations thereof.

[0209] If the automatic shutdown decision subsystem 2650 classifies a fault event as a normal fault event, in step S3710, the automatic shutdown decision subsystem 2650 causes the nicotine e-vaping device 500 to perform one or more resulting actions depending on the fault event that occurred. For example, the automatic shutdown decision subsystem 2650 may output one or more device power status signals to control the nicotine e-vaping device 500 and perform one or more resulting actions (e.g., a charger stop operation, a vaping off operation, an automatic off operation, a heater off operation, or a combination thereof).

[0210] In an embodiment where a normal fault event is an interrupt from the charger 2132 indicating that charging of the power supply 2110 is complete, the fault detection subsystem 2630 can receive the interrupt from the charger 2132. In response to receiving the interrupt from the charger 2132, the fault detection subsystem 2630 can output a fault alarm (charging completion fault alarm) to the automatic shutdown decision subsystem 2650 indicating that an interrupt has been received. In response to the fault alarm, the automatic shutdown decision subsystem 2650 determines that a normal fault event has occurred and initiates / executes the stop operation of the charger.

[0211] As will be described in more detail later, the charger 2132 may include a dedicated charging IC with multiple inputs / outputs (I / O) used to manage and control the charging of the power supply 2110. The charger stop operation may disable or stop the charging of the power supply 2110 in the nicotine e-vaping device 500. As will be described in more detail later, the control device 2105 may control the charger 2132 to disable or stop the charging of the power supply 2110 by outputting a charger stop signal BATT_SUSP (e.g., having a high logic level) to the dedicated charging IC in the charger 2132.

[0212] In an embodiment where a normal fault event is an interrupt generated in response to an input via the in-product control unit 2150 (for example, requesting the disabling of the vaping function, disabling power to the heater 336, or cutting off power to the nicotine e-vaping device 500), the fault detection subsystem 2630 may receive the interrupt from the in-product control unit 2150. In response to receiving the interrupt, the fault detection subsystem 2630 may output a fault alarm (adult vapor fault alarm) to the automatic shutdown decision subsystem 2650 indicating that an interrupt has been received. In response to the fault alarm, the automatic shutdown decision subsystem 2650 determines that a normal fault event has occurred and, if necessary, initiates / executes a vaping off operation, a heater off operation, an automatic shut-off operation, or a combination thereof.

[0213] According to at least some exemplary embodiments, the automatic shut-off decision subsystem 2650 (or control device 2105) may perform an automatic shut-off operation by outputting a number of GPIO control lines (signals) to turn off all or substantially all peripherals of the nicotine e-vaping device 500, thereby putting the control device 2105 into a sleep state.

[0214] The vaping-off operation can disable all energy to the heater 336, thereby preventing vaping until a corrective action is performed (e.g., by an adult vapor). As will be described in more detail later, the automatic shut-off decision subsystem 2650 can control the heating engine control circuit 2127 to disable all energy to the heater 336 by outputting a vaping-off signal COIL_SHDN having a logic high level (Figure 38) or by deasserting (or stopping the output of) a vaping-enable signal COIL_VGATE_PWM (Figure 39). In at least one embodiment, at least the vaping-enable signal COIL_VPATE_PWM may be a pulse-width modulation (PWM) signal.

[0215] The heater-off operation can disconnect power to the heater 336 and terminate any current vaping event, otherwise the nicotine e-vaping device 500 may remain in a vaping-ready state. As will be discussed in more detail later, the automatic shut-off decision subsystem 2650 (or more generally, the control unit 2105) can control the heating engine control circuit 2127 to disconnect power to the heater 336 by outputting a heater enable signal GATE_ON (Figure 38) with a logic low level, or by outputting one or more of the first heater enable signal GATE_ENB or the second heater enable signal COIL_Z (Figure 39) with a logic low level.

[0216] In yet another embodiment, the fault detection subsystem 2630 may determine that an idling event has occurred in accordance with the exemplary embodiment shown in Figure 31. In this embodiment, in response to determining that an idling event has occurred, the fault detection subsystem 2630 may output a fault alarm (idling alarm) to the automatic shut-off decision subsystem 2650 indicating that an idling event has occurred. In response to the fault alarm, the automatic shut-off decision subsystem 2650 may classify the idling event as a normal fault event and, if necessary, perform a heater off operation, a vaping off operation, an automatic shut-off operation, or something similar.

[0217] Returning to step S3706, if the fault event is not a normal fault event, in step S3722, the automatic shutdown decision subsystem 2650 determines whether the fault event is a soft fault pod event.

[0218] As described above, soft fault pod events may include temperature events in which the temperature of the nicotine pod assembly electrical system 2200 or its components (e.g., heater 336) exceeds a maximum temperature threshold. In more specific embodiments, a fault detection subsystem may determine whether a heater temperature fault event occurred in relation to one or more of the exemplary embodiments shown in Figures 32A and 32B. However, the exemplary embodiments should not be limited to these examples.

[0219] If the automatic shutdown decision subsystem 2650 identifies a fault event as a soft fault pod event, in step S372, the automatic shutdown decision subsystem 2650 performs one or more resulting actions on the soft fault pod event.

[0220] For illustrative purposes, more detailed examples are described with respect to one or more resulting actions in response to heater temperature disturbance events.

[0221] As shown in Figures 33A and 33B, in step S3724, the automatic shut-off decision subsystem 2650 controls the heating engine control circuit 2127 to perform a heater-off operation, as described above and in more detail below.

[0222] In step S3726, the automatic shutdown decision subsystem 2650 records the occurrence of a soft fault pod event in the memory 2130. In one embodiment, the control device 2105 may store an identifier of the soft fault pod event (e.g., a heater temperature fault event) related to the identification of the heater off operation, and the time when the soft fault pod event and the heater off operation occurred.

[0223] In step S3727, the automatic shut-off decision subsystem 2650 controls the vapor indicator 2135 to output a display indicating that a fault event (e.g., a heater temperature fault event) has occurred. In one embodiment, the display may be in the form of audio, visual, and / or tactile feedback to the adult vapor. For example, the display may be a flashing red LED and a software message containing an error code that is transmitted (e.g., via Bluetooth®) to a connected “app” of a remote electronic device.

[0224] In step S3728, the automatic shutdown decision subsystem 2650 determines whether to return the nicotine e-vaping device 500 to normal operation (FSM non-fault state). In embodiments where the soft fault pod event is a heater temperature fault event, the automatic shutdown decision subsystem 2650 may determine whether to return to normal operation based on whether the temperature of the heater 336 is below the threshold maximum temperature value.

[0225] If the automatic shutdown decision subsystem 2650 determines that the nicotine e-vaping device 500 will not return to normal operation (for example, the temperature of the heater 336 will not fall below the threshold maximum temperature value), the process returns to step S3727 and continues to wait for an indication that the nicotine e-vaping device 500 should return to normal operation.

[0226] However, if the automatic shutdown decision subsystem 2650 determines in step S3728 that the nicotine e-vaping device 500 will return to normal operation, in step S3729 the automatic shutdown decision subsystem 2650 returns the nicotine e-vaping device 500 to normal operation, ready for vaping when vaping conditions are subsequently presented (for example, in response to the application of negative pressure by an adult). In embodiments in which a heater temperature fault event occurs, the automatic shutdown decision subsystem 2650 may control the heating engine control circuit 2127 to enable power to the heater 336 by outputting a heater enable signal GATE_ON (Figure 38) having a high logic level, or by outputting both a first heater enable signal GATE_ENB and a second heater enable signal COIL_Z (Figure 39) having high logic levels.

[0227] While the exemplary embodiments shown in Figures 33A and 33B are described as including step S3728, this step may be omitted, and the process may proceed directly from step S3727 to step S3729, in which the automatic shutdown decision subsystem 2650 returns to normal operation. Because soft fault pod events are relatively low in importance and, in simpler implementations, intermittent and self-extinguishing, these faults are not actively monitored, and no state information regarding them is maintained within the decision system. Instead, the faults reappear (and are dealt with again) if they are still present when vaping conditions are presented again in the nicotine e-vaping device. For example, if the temperature of the heater 336 is still above the threshold maximum temperature value and an adult vaper applies negative pressure to the nicotine e-vaping device, the heater off operation is performed again.

[0228] Returning to step S3722, if the failure event is not a soft failure pod event, in step S3730 the automatic shutdown decision subsystem 2650 determines whether the failure event is a hard failure pod event.

[0229] As described above, hard fault pod events may include open-circuit faults in the nicotine pod assembly electrical system 2200, depletion of the nicotine pre-vapor formulation in the nicotine pod assembly 300 (empty pod), detection of dry vapor inhalation in the nicotine pod assembly 300, a combination thereof, or similar events.

[0230] If the automatic shutdown decision subsystem 2650 identifies a fault event as a hard fault pod event, in step S3730, the automatic shutdown decision subsystem 2650 performs one or more resulting actions on the hard fault pod event.

[0231] As shown in Figures 33A and 33B, in at least one exemplary embodiment, in step S3732, the automatic shutdown decision subsystem 2650 may perform a vaping-off operation in response to a hard fault pod event, as described above with respect to step S3710.

[0232] In step S3734, the automatic shutdown decision subsystem 2650 records or stores the occurrence of a hard fault pod event in the memory 2130. The automatic shutdown decision subsystem 2650 may record or store the occurrence of a hard fault pod event in the same or substantially the same manner as described above with respect to step S3726.

[0233] In step S3736, the automatic shutdown decision subsystem 2650 controls the vapor indicator 2135 to output a display indicating that a hard fault pod event has occurred. The automatic shutdown decision subsystem 2650 may control the vapor indicator 2135 to output a display in the same or substantially the same manner as described above with respect to step S3727.

[0234] In step S3738, the automatic shutdown decision subsystem 2650 determines whether a corrective action has been performed in response to a hard fault pod event (for example, by an adult vaper within a threshold time after the hard fault pod event has been detected). The corrective action may include removing the nicotine pod assembly 300 from the (pre-termination) device body 100 within a subsequent removal threshold time interval after indicating a hard fault pod event to an adult vaper (for example, in response to a hard fault pod event).

[0235] In this embodiment, the automatic shut-off decision subsystem 2650 may determine that the nicotine pod assembly 300 has been removed from the device body 100 by digitally checking that a set of five contacts 326 of the nicotine pod assembly 300 has been removed. In another embodiment, the automatic shut-off decision subsystem 2650 may determine that the nicotine pod assembly 300 has been removed from the device body 100 by sensing that the electrical contacts 324a, 324b and / or 326 of the nicotine pod assembly 300 have been removed from the device's electrical connector 132 of the device body 100.

[0236] If the automatic shut-off decision subsystem 2650 determines that a corrective action has been performed (for example, the nicotine pod assembly 300 was removed from the device body 100 within the removal threshold time interval after exhibiting a hard fault pod event), the process proceeds to step S3729 and continues as described above. In this case, although the energy to the heater 336 is still deactivated because the nicotine pod assembly 300 has been removed, the nicotine e-vaping device 500 is otherwise ready for vaporization in response to the application of negative pressure by an adult vaporizer once a new nicotine pod assembly is inserted.

[0237] If the automatic shut-off decision subsystem 2650 determines that the nicotine pod assembly 300 has not been removed within the removal threshold time interval (i.e., no correction action has been performed within the threshold time interval), the automatic shut-off decision subsystem 2650 outputs one or more other control signals to perform an automatic shut-off operation.

[0238] By performing an automatic shut-off operation, the discharge of the power supply 2110 of the nicotine e-vaping device 500 due to prolonged malfunction can be prevented.

[0239] Returning to step S3730, if the fault event is not a hard fault pod event, in step S3742 the automatic shutdown decision subsystem 2650 determines whether the fault event is a soft fault device event. As described above, an example of a soft fault device event may be a power supply undervoltage fault event, where the voltage or charge of the power supply 2110 falls below a minimum threshold level. In this embodiment, the fault detection subsystem 2630 may determine that a power supply undervoltage fault event has occurred and output a fault alarm to the automatic shutdown decision subsystem 2650 indicating the occurrence of a power supply undervoltage fault event. In response to the fault alarm, the automatic shutdown decision subsystem 2650 classifies the power supply undervoltage fault event as a soft fault device event. More generally, the fault detection subsystem 2630 may output a soft fault device event alarm to the automatic shutdown decision subsystem 2650 indicating that the soft fault device event occurred in the nicotine e-vaping device 500.

[0240] If the automatic shutdown decision subsystem 2650 identifies a fault event as a soft fault device event, in step S374, the automatic shutdown decision subsystem 2650 performs one or more resulting actions in response to the soft fault device event.

[0241] As shown in Figures 33A and 33B, in at least one exemplary embodiment, in step S3744, the automatic shutdown decision subsystem 2650 outputs one or more device power status signals to initiate / execute a vaping-off operation and / or an automatic shutdown operation. The automatic shutdown decision subsystem 2650 may determine whether to initiate a vaping-off operation and / or an automatic shutdown operation based on the current voltage of the power supply. For example, if the voltage of the power supply 2110 is below a first threshold level, the automatic shutdown decision subsystem 2650 may initiate a vaping-off operation. However, if the voltage of the power supply 2110 is below a second threshold level that is lower than the first threshold level, the automatic shutdown decision subsystem 2650 may initiate an automatic shutdown operation.

[0242] In step S3746, the automatic shutdown decision subsystem 2650 records or saves the occurrence of a soft fault device event in the memory 2130. With respect to step S3726, the automatic shutdown decision subsystem 2650 may record or save the occurrence of a soft fault device event in the same or substantially the same manner as described above.

[0243] In step S3748, the automatic shutdown decision subsystem 2650 controls the vapor indicator 2135 to output a display indicating that a soft fault device event has occurred. The automatic shutdown decision subsystem 2650 may control the vapor indicator 2135 to output a display in the same or substantially the same manner as described above with respect to step S3727.

[0244] In step S3750, the automatic shutdown decision subsystem 2650 determines whether a corrective action has been performed in response to a soft fault device event (for example, by a mature vapor within a threshold time interval). In embodiments where the soft fault device event is a low-voltage fault event of the power supply, the corrective action may include charging the power supply 2110 above a first threshold level.

[0245] If the automatic shutdown decision subsystem 2650 determines that a corrective action has been performed (for example, the voltage of the power supply 2110 has increased beyond a first (minimum) threshold level), the process proceeds to step S3729, in which the nicotine e-vaping device 500 returns to normal operation. In this case, with respect to step S3729, the automatic shutdown decision subsystem 2650 may enable the control device 2105 to exit sleep mode (for example, if an automatic shutdown operation is performed) and / or enable the vaping function in the nicotine e-vaping device 500, as described above.

[0246] Returning to step S3750, if no corrective action is performed in response to the soft fault device event, the process returns to S3748, and the soft fault device event indicator is continuously output to the adult vaper until a corrective action is performed or the nicotine e-vaping device 500 is manually powered off. If the automatic off operation is activated in step S3744, the soft fault device event indicator may be repeatedly output via the vaper indicator 2135 in response to the adult vaper's interaction with the nicotine e-vaping device 500 (e.g., pressing one or more buttons on the device) until a corrective action is performed.

[0247] Returning to step S3742, if the automatic shutdown decision subsystem 2650 determines that the fault event is not a soft fault event, then in step S3754, the automatic shutdown decision subsystem 2650 determines that the fault event is a hard fault event. As described above, hard fault events may include power supply charging fault events, the presence of current flowing through the heater when not in a vaping state ("unexpected heater current"), and power supply temperature faults indicating that the temperature of the power supply 2110 is outside the acceptable range, a combination thereof, or similar. "Unexpected heater current" is a hard fault event in which software (or hardware) leaves the heater 336 energized (for example, after the vaping conditions no longer exist for the nicotine e-vaping device 500), and is one example of why the nicotine e-vaping device 500 is reset in step S3768 as part of the resulting action.

[0248] According to at least one exemplary embodiment, the automatic shutdown decision subsystem 2650 may determine that a power supply temperature anomaly has occurred based on whether the estimated temperature of the power supply 2110 is above a maximum power supply temperature threshold or below a minimum power supply temperature threshold. The automatic shutdown decision subsystem 2650 may estimate the temperature of the power supply 2110 based on the output from the power supply temperature measurement circuit 21254, which will be described in more detail later.

[0249] If the automatic shutdown decision subsystem 2650 identifies the failure event as a hard fault device event, in step S376, the automatic shutdown decision subsystem 2650 performs one or more resulting actions in response to the hard fault device event.

[0250] As shown in Figures 33A and 33B, in at least one exemplary embodiment, in response to a hard fault device event, in step S3756, the automatic shutdown decision subsystem 2650 initiates / executes one or more of the following: a vaping-off operation, a charger-stopping operation, and / or an automatic-off operation.

[0251] In step S3758, the automatic shutdown decision subsystem 2650 records or saves the occurrence of a hard fault device event in the memory 2130. With respect to step S3726, the automatic shutdown decision subsystem 2650 may record or save the occurrence of a hard fault device event in the same or substantially the same manner as described above.

[0252] In step S3760, the automatic shutdown decision subsystem 2650 activates the reset timer. The reset timer may be the time interval after which the automatic shutdown decision subsystem 2650 causes the nicotine e-vaping device 500 to perform a soft reset. In this case, the reset timer may be a countdown timer that is executed using the clock circuit 2128.

[0253] In step S3762, the automatic shutdown decision subsystem 2650 controls the vapor indicator 2135 to output a display indicating that a hardware fault device event has occurred. The automatic shutdown decision subsystem 2650 may control the vapor indicator 2135 to output a display in the same or substantially the same manner as described above with respect to step S3727.

[0254] After outputting the display, in step S3764, the automatic shutdown decision subsystem 2650 determines whether the reset timer started in step S3760 has elapsed in step S3764.

[0255] If the reset timer has elapsed, in step S3768, the automatic shutdown decision subsystem 2650 performs a soft reset of the nicotine e-vaping device 500 to clear the hard fault device event. The soft reset may include closing all software applications running on the control unit 2105, erasing the random access memory (RAM) and / or any persistent memory if possible, and restarting the nicotine e-vaping device 500.

[0256] Although soft resets have been mentioned, the reset in step S3768 can be a soft (software) reset, a hard (hardware) reset, or a power-on reset (POR).

[0257] After performing a soft reset, in step S3770, the automatic shutdown decision subsystem 2650 determines whether the hard fault device event has been cleared (for example, whether the soft reset corrected the fault condition).

[0258] If a hardware failure device event is cleared by a soft reset in step S3768, the process proceeds to step S3729, where the automatic shutdown decision subsystem 2650 restores the nicotine e-vaping device 500 to normal operation by, for example, enabling charging, vaping, etc., as necessary.

[0259] According to one or more exemplary embodiments, a hardware failure device event may generally cover at least unexpected cases (e.g., software crashes) that can only be recovered by performing a reset.

[0260] Returning to step S3770, if the hard fault device event has not been cleared by the soft reset in step S3768, in step S3772, the automatic shutdown decision subsystem 2650 shuts down the nicotine e-vaping device 500. In this embodiment, similar to the automatic off operation, the automatic shutdown decision subsystem 2650 may cut off the power to the nicotine e-vaping device 500 by outputting one or more device power status signals to the subsystem of the nicotine e-vaping device 500.

[0261] According to at least one exemplary embodiment, the reset in step S3768 may be attempted three times before shutting off the nicotine e-vaping device 500 in step S3772.

[0262] According to at least some other exemplary embodiments, if the hard failure device event is not cleared after three reset attempts, the automatic shutdown determination subsystem 2650 may set a persistent bit in memory that prevents the nicotine e-vaping device 500 from being turned on.

[0263] Returning now to step S3764, if the reset timer has not expired, the automatic shutdown determination subsystem 2650 determines whether a corrective action has been performed in step S3766.

[0264] In embodiments where the hard failure device event is a power supply temperature failure, corrective actions may include moving the nicotine e-vaping device 500 to a warmer location (if the power supply temperature is below the minimum threshold) or moving the nicotine e-vaping device 500 to a cooler location (if the power supply temperature exceeds the maximum threshold). In this embodiment, the automatic shutdown determination subsystem 2650 may, as needed, determine whether a corrective action has been performed based on whether the temperature of the power supply 2110 rises or falls.

[0265] If a corrective action has been performed, the process proceeds to step S3729 and continues as described above.

[0266] Returning to step S3766, if the reset timer has not expired and the corrective action has not yet been performed, the process returns to S3762, and the indication of the hard failure device event is continuously output until the corrective action is performed or the nicotine e-vaping device 500 is manually powered off. The process then continues as described herein.

[0267] Figure 34 illustrates an exemplary embodiment of a heater voltage measurement circuit 21252.

[0268] Referring to Figure 34, the heater voltage measurement circuit 21252 includes resistors 3702 and 3704 connected in a voltage divider configuration between a terminal configured to receive the input voltage signal COIL_OUT and ground. The input voltage signal COIL_OUT is the voltage input to the heater 336 (at its input terminal). Node N3716 between resistors 3702 and 3704 is coupled to the positive input of the operational amplifier (Op-Amp) 3708. Capacitor 3706 is connected between node N3716 and ground, forming a low-pass filter circuit (R / C filter) to stabilize the voltage input to the positive input of the operational amplifier 3708. The filter circuit can also reduce inaccuracies due to switching noise induced by the PWM signal used to energize the heater 336 and has the same phase response / group delay for both current and voltage.

[0269] The heater voltage measurement circuit 21252 further includes resistors 3710 and 3712, and a capacitor 3714. Resistor 3712 is connected between node N3718 and a terminal configured to receive the output voltage signal COIL_RTN. The output voltage signal COIL_RTN is the voltage output from heater 336 (voltage at the output terminal).

[0270] Resistor 3710 and capacitor 3714 are connected in parallel between node N3718 and the output of op-amp 3708. The negative input of op-amp 3708 is also connected to node N3718. Resistors 3710 and 3712 and capacitor 3714 are connected in a low-pass filter circuit configuration.

[0271] The heater voltage measurement circuit 21252 uses an operational amplifier 3708 to measure the voltage difference between the input voltage signal COIL_OUT and the output voltage signal COIL_RTN, and outputs a scaled heater voltage measurement signal COIL_VOL representing the voltage across the heater 336. The heater voltage measurement circuit 21252 outputs the scaled heater voltage measurement signal COIL_VOL to the ADC pin of the control device 2105 for digital sampling and measurement by the control device 2105.

[0272] The gain of the operational amplifier 3708 is set based on the surrounding passive electrical elements (e.g., resistors and capacitors) to improve the dynamic range of the voltage measurement. In one embodiment, the dynamic range of the operational amplifier 3708 can be achieved by scaling the voltage so that the maximum voltage output matches the maximum input range of the ADC (e.g., about 1.8V). In at least one exemplary embodiment, the scaling may be about 267mV per V, and therefore the heater voltage measurement circuit 21252 can measure up to about 1.8V / 0.267V = 6.74V.

[0273] Figure 35 shows an exemplary embodiment of the heater current measurement circuit 21258 shown in Figure 29.

[0274] Referring to Figure 35, the output voltage signal COIL_RTN is input to a four-terminal (4T) measuring resistor 3802 connected to ground. The differential pressure across the four-terminal measuring resistor 3802 is scaled by an operational amplifier 3806, which outputs a heater current measuring signal COIL_CUR indicating the current through the heater 336. The heater current measuring signal COIL_CUR is output to the ADC pin of the control unit 2105 for digital sampling and measurement of the current through the heater 336.

[0275] In the exemplary embodiment shown in Figure 35, errors in current measurement can be reduced using the "Kelvin current measurement" technique with four terminal measuring resistors 3802. In this embodiment, noise on the voltage measurement path can be reduced by separating the current measurement path from the voltage measurement path.

[0276] The gain of the operational amplifier 3806 may be set to improve the dynamic range of the measurement. In this embodiment, the scaling of the operational amplifier 3806 may be approximately 0.577 V / A, and therefore the heater current measurement circuit 21258 can measure up to approximately

number

[0277] Referring more closely to Figure 35, the first terminal of the four-terminal measuring resistor 3802 is connected to the terminal of the heater 336 to receive the output voltage signal COIL_RTN. The second terminal of the four-terminal measuring resistor 3802 is connected to ground. The third terminal of the four-terminal measuring resistor 3802 is connected to a low-pass filter circuit (R / C filter) including resistor 3804, capacitor 3808, and resistor 3810. The output of the low-pass filter circuit is connected to the positive input of the operational amplifier 3806. The low-pass filter circuit can reduce inaccuracies due to switching noise induced by the PWM signal applied to energize the heater 336, and can have the same phase response / group delay for both current and voltage.

[0278] The heater current measurement circuit 21258 further includes resistors 3812 and 3814, and capacitor 3816. Resistors 3812 and 3814 and capacitor 3816 are connected to the fourth terminal of the four-terminal measuring resistor 3802 of the low-pass filter circuit configuration, the negative input of the operational amplifier 3806, and the output of the operational amplifier 3806, and the output of the low-pass filter circuit is connected to the negative input of the operational amplifier 3806.

[0279] The operational amplifier 3806 outputs the differential voltage as the heater current measurement signal COIL_CUR to the ADC pin of the control device 2105 for sampling and measuring the current passing through the heater 336 by the control device 2105.

[0280] According to at least this exemplary embodiment, the configuration of the heater current measurement circuit 21258 is similar to the configuration of the heater voltage measurement circuit 21252, except that a low-pass filter circuit including resistors 3804 and 3810 and a capacitor 3808 is connected to a terminal of the four-terminal measurement resistor 3802, and a low-pass filter circuit including resistors 3812 and 3814 and a capacitor 3816 is connected to another terminal of the four-terminal measurement resistor 3802.

[0281] The control device 2105 may average a plurality of samples (e.g., voltage) over a time window (e.g., about 1 millisecond) corresponding to a "tick" time used in the nicotine e-vaping device 500, and convert the average value into a mathematical expression of voltage and current across the heater 336 through application of a scaling value. The scaling value may be determined based on a gain setting implemented in each operational amplifier, which may be specific to the hardware of the nicotine e-vaping device 500.

[0282] The control device 2105 may filter the converted voltage and current measurement values to attenuate measurement noise, for example using a three-tap moving average filter. The control device 2105 then uses the filtered measurement values to calculate the resistance of the heater 336 [[Mathematical Formula]] power applied to the heater 336 [[Mathematical Formula]] [[Mathematical Formula]] and the like, wherein in the formulas, [[Mathematical Formula]] The efficiency is the power P delivered to the heater 336 under all operating conditions. in This is the ratio. In one embodiment, the efficiency can be at least 85%.

[0283] According to one or more exemplary embodiments, the gain settings of the passive elements in the circuit shown in Figure 34 and / or Figure 35 may be adjusted to match the output signal range to the input range of the control device 2105.

[0284] The fault detection subsystem 2630 may use heater voltage and / or heater current measurements to determine whether a hard fault pod event has occurred, for example, an open-circuit fault in heater 336.

[0285] Figures 36 and 37 show a pod temperature measurement circuit according to an exemplary embodiment.

[0286] Referring to Figure 36, the pod temperature measurement circuit 21250A includes a driver stage 3902A and a measurement stage 3904A. The driver stage 3902A is configured to generate a pod temperature measurement power signal HW_POWER in response to a pod temperature measurement control signal HW_ENB to deliver power to the pod sensor 2220. The pod temperature measurement power signal HW_POWER may be a PWM signal. The measurement stage 3904A is configured to generate a pod temperature measurement output signal HW_SIGNAL based on a DAC comparison signal HW_DAC from a DAC (not shown) of the control unit 2105 and a pod sensor signal SP_HW from the pod sensor 2220. The pod temperature measurement output signal HW_SIGNAL may be a differential pressure signal indicating the temperature of one or more elements of the nicotine pod assembly 300 (e.g., heater 336). The inputs and outputs up to an exemplary embodiment of the pod sensor 2220 will be described in more detail later.

[0287] To elaborate further with respect to Figure 36, the driver stage 3902A receives the pod temperature measurement control signal HW_ENB from the control unit 2105. In this embodiment, the pod temperature measurement control signal HW_ENB may be a PWM signal with a load cycle that is controlled by the control unit 2105 and changes power based on the pod sensor signal SP_HW from the pod sensor 2220. If the pod temperature measurement control signal HW_ENB is asserted (operating), the driver stage 3902A may be enabled and output the pod temperature measurement power signal HW_POWER; otherwise, the output of the driver stage 3902A may be disabled.

[0288] The pod temperature measurement control signal HW_ENB is input to the activation pin EN of the low dropout voltage controller (LDO) U10, which converts the pod temperature measurement control signal HW_ENB, which is a low current drive intensity processor signal, into the pod temperature measurement power signal HW_POWER, which is a high current drive intensity PWM signal.

[0289] Resistor R80 is connected as a pull-down resistor between the start pin EN of LDO U10 and ground to ensure that the output of driver stage 3902A is reliably disabled when the pod temperature measurement control signal HW_ENB is in an uncertain state.

[0290] The driver stage 3902A further includes capacitors C43 and C44. Capacitor C44 is connected to the input pin IN of the LDO U10 and the voltage source, providing storage and filtering, which can improve the speed at which the pod temperature measurement power signal HW_POWER reaches its ON voltage. Capacitor C43 is connected between the output pin and ground, providing filtering and storage for the pod temperature measurement power signal HW_POWER.

[0291] Resistors R60 and R61 form a feedback network 39028 in the form of a voltage divider circuit. The feedback network 39028 outputs a feedback voltage to the adjustment or feedback terminal ADJ of LDO U10. Based on the feedback voltage input to feedback terminal ADJ, LDO U10 sets a precise voltage output of the pod temperature measurement power signal HW_POWER. According to at least some exemplary embodiments, the precise voltage output and feedback voltage V are relative to the pod temperature measurement power signal HW_POWER. ADJ The relationship with the output is,

number

[0292] At measurement stage 3904A, the pod sensor signal SP_HW from the pod sensor 2220 is input to the negative input of op-amp U11A via resistor R66 to obtain voltage scaling of the pod sensor signal SP_HW for measurement by ADC in control unit 2105. Op-Amp U11A is an inverting amplifier with gain set with respect to the resistance of resistors R66 and R67, and is connected between the negative input and the output of Op-Amp U11A. Capacitor C47 is connected in parallel with resistor R67 to form a low-pass filter circuit for filtering high-frequency noise from the pod sensor signal SP_HW.

[0293] The DAC comparison signal HW_DAC from the DAC in the control unit 2105 is input to the positive input of the operational amplifier U11A via a voltage divider circuit 39042, which includes resistors R63 and R64. The DAC comparison signal HW_DAC sets the reference voltage level of Op-Amp U11A, which effectively selects the differential pressure applied to Op-Amp U11A and suppresses or prevents saturation of Op-Amp U11A. In other words, the DAC comparison signal HW_DAC sets the operating point of Op-Amp U11A to suppress saturation of the pod temperature measurement output signal HW_SIGNAL output by Op-Amp U11A. The voltage divider circuit 39042 reduces each DAC step of the voltage to provide finer control of the range setting. The ratio of resistors R63 and R64 can be approximated by the balance resistor and the pod sensor 2220 (e.g., at its maximum temperature). Capacitor C46 is connected in parallel with resistor R64 to form a low-pass filter circuit that filters noise from the DAC comparison signal HW_DAC. Resistor R69 is connected between the output of the voltage divider circuit 39042 and the positive input of the operational amplifier U11A.

[0294] The pod sensor signal SP_HW from the pod sensor 2220 may have a relatively small voltage level (e.g., about 2mV), and therefore, the relatively high gain of Op-Amp U11A can be used to match the pod temperature measurement signal HW_SIGNAL to the dynamic signal range of the ADC in the control unit 2105 (e.g., about 1.8V). Thus, Op-Amp U11A amplifies the pod sensor signal SP_HW and outputs the amplified signal to the ADC as the pod temperature measurement output signal HW_SIGNAL for sampling and measurement in the control unit 2105.

[0295] Referring to Figure 37, the pod temperature measurement circuit 21250B includes a driver stage 3902B and a measurement stage 3904B. In the exemplary embodiment shown in Figure 37, the driver stage 3902B and the measurement stage 3904B are similar to the driver stage 3902A and measurement stage 3904A shown in Figure 36, respectively, except that the driver stage 3902B further includes a measurement balance resistor R93, and the capacitance of capacitor C43 may be reduced to increase the rise / fall time of the pod sensor signal SP_HW. In at least one embodiment, the measurement balance resistor R93 may have a resistance of about 3 ohms and may be moved from the nicotine pod assembly electrical system 2200 to the device body electrical system 2100 to reduce the cost of the nicotine pod assembly 300. Furthermore, in at least the exemplary embodiment shown in Figure 37, passive elements may be arranged and adjusted to configure gain settings such that the output signal range matches the input signal range of the control device 2105.

[0296] According to one or more exemplary embodiments, the fault detection subsystem 2630 may use temperature measurements from the control device 2105 to estimate the temperature of, for example, the heater 336 or other parts of the nicotine pod assembly 300 and determine whether a soft fault pod event (e.g., a heater temperature fault event) has occurred.

[0297] Figure 38 is a circuit diagram showing a control circuit of a heating engine according to an exemplary embodiment. The heating engine control circuit shown in Figure 38 is an example of the heating engine control circuit 2127 shown in Figure 29.

[0298] Referring to Figure 38, the heating engine control circuit 2127A includes a CMOS charge pump U2 configured to supply a power rail (e.g., a power rail of about 7V (7V_CP)) to one or more gate driver integrated circuits (ICs) in order to control a power FET (a heater power control circuit, also referred to as a heating engine drive circuit or circuit, not shown in Figure 38) that conducts power to the heater 336 in the nicotine pod assembly 300.

[0299] In exemplary operation, the charge pump U2 is controlled (selectively started or stopped) based on a vaping cutoff signal COIL_SHDN (a device power state signal, also referred to as the vaping enable signal) from the control unit 2105. In the embodiment shown in Figure 38, the charge pump U2 is started in response to the output of the vaping cutoff signal COIL_SHDN, which has a logic low level, and stopped in response to the output of the coil cutoff signal COIL-SHDN, which has a logic high level. Once the power rail 7V_CP has stabilized after the charge pump U2 has started (e.g., after the settling time interval has ended), the control unit 2105 may enable the heater enable signal GATE_ON to supply power to the heater power control circuit and the heater 336.

[0300] According to at least one exemplary embodiment, the control unit 2105 (or the automatic shut-off decision subsystem 2650) performs a vaping-off operation by outputting (enabling) a vapor stop shut-off signal COIL_SHDN having a logic high level, and disables all power to the heater 336 until the vaping shut-off signal COIL_SHDN is deactivated (transitioned to a logic low level) by the control unit 2105.

[0301] In response to detecting the presence of vaping conditions in the nicotine e-vaping device 500, the control unit 2105 may output a heater enable signal GATE_ON (another device power status signal) with a logic high level. In this exemplary embodiment, when the control unit 2105 enables the heater enable signal GATE_ON to a logic high level, transistors (e.g., field-effect transistors (FETs)) Q5 and Q7A' are activated. The control unit 2105 may output a heater enable signal GATE_ON with a logic low level to disable power to the heater 336, thereby performing a heater-off operation.

[0302] If transistors Q5 and Q7A' fail to respond to the heater enable signal GATE_ON, resulting in a power stage fault event (hard fault device event), the control unit 2105 may perform a vaping-off operation by outputting a vaping-off signal COIL_SHDN with a logic high level to cut off power to the gate driver, which then cuts off power to the heater 336.

[0303] In another embodiment, if the control device 2105 fails to start properly, and as a result the vaping cutoff signal COIL_SHDN is in an uncertain state (startup failure), the heating engine control circuit 2127A automatically pulls the vaping cutoff signal COIL_SHDN to a logical high level and automatically cuts off power to the heater 336.

[0304] To elaborate further on Figure 38, capacitor C9, charge pump U2, and capacitor C10 are connected in a positive voltage doubler configuration. Capacitor C9 is connected between pins C- and C+ of charge pump U2 and functions as a storage for charge pump U2. The input voltage pin VIN of charge pump U2 is connected to the voltage source BATT at node N3801, and capacitor C10 is connected between ground and the output voltage pin VOUT of charge pump U2 at node N3802. Capacitor C10 provides a filter and storage for the output from charge pump U2, which can ensure a more stable voltage output from charge pump U2.

[0305] Capacitor C11 is connected between node N3801 and ground and provides a storage for the input voltage to the filter and charge pump U2.

[0306] Resistor R10 is connected between the positive voltage source and the cutoff pin SHDN. Resistor R10 acts as a pull-up resistor to ensure that the input to the cutoff pin SHDN is high, thereby disabling the output (VOUT) of charge pump U2 and cutting off power to heater 336 when the vaping cutoff signal COIL_SHDN is in an uncertain state.

[0307] Resistor R43 is connected between ground and the gate of transistor Q7A' at node N3804. Resistor R43 acts as a pull-down resistor to ensure that transistor Q7A' is in a high impedance (off) state, thereby disabling the power rail 7V_CP and cutting off power to heater 336 when the heater enable signal GATE_ON is in an uncertain state.

[0308] Resistor R41 is connected between node N3802 and node N3803, which is between the gate of transistor Q5 and the drain of transistor Q7A'. Resistor R41 acts as a pull-down resistor, ensuring that transistor Q5 switches off more reliably.

[0309] Transistor Q5 is configured to selectively isolate the power rail 7V_CP from the VOUT charge pump U2 pin. The gate of transistor Q5 is connected to node N3803, the drain of transistor Q5 is connected to the output voltage terminal VOUT of the charge pump U2 at node N3802, and the source of transistor Q5 functions as the output terminal of the power rail 7V_CP. This configuration allows capacitor C10 to reach its operating voltage more quickly by isolating the load, and generates a failsafe as long as both the vaping cutoff signal COIL_SHDN and the heater enable signal GATE_ON are in the correct state in order to supply power to heater 336.

[0310] Transistor Q7A is configured to control the operation of transistor Q5 based on the heater enable signal GATE_ON. For example, when the heater enable signal GATE_ON is at a high logic level (e.g., about 2V or higher), transistor Q7A is in its low impedance (ON) state, which pulls the gate of transistor Q5 to ground, thereby causing transistor Q5 to transition to the low impedance (ON) state. In this case, the heating engine control circuit 2127A outputs the power rail 7V_CP to the heating engine drive circuit (not shown), thereby enabling power to the heater 336.

[0311] If the heater enable signal GATE_ON has a logic low level, transistor Q7A transitions to a high impedance (off) state, which in turn discharges the gate of transistor Q5 through resistor R41, thereby causing transistor Q5 to transition to a high impedance (off) state. In this case, the power rail 7V_CP is not output, and power to the heating engine drive circuit (and heater 336) is cut off.

[0312] In the embodiment shown in Figure 38, the control unit 2105 does not directly control transistor Q5 because transistor Q5 needs to be in a high-impedance (off) state with a gate voltage the same height as the source voltage (approximately 7V). Transistor Q7A provides a mechanism for controlling transistor Q5 based on a lower voltage from the control unit 2105.

[0313] Figure 39 is a circuit diagram showing a control circuit of a heating engine according to an exemplary embodiment. The heating engine control circuit shown in Figure 39 is another embodiment of the heating engine control circuit 2127 shown in Figure 29.

[0314] Referring to Figure 39, the heating engine control circuit 2127B includes a rail converter circuit 39020 (also referred to as a boost converter circuit) and a gate driver circuit 39040. The rail converter circuit 39020 is configured to output a voltage signal 9V_GATE (also referred to as a power signal or input voltage signal) to power the gate driver circuit 39040 based on a vaping enable signal COIL_VGATE_PWM (also referred to as a vaping cutoff signal). The rail converter circuit 39020 may be software defined by the vaping enable signal COIL_VGATE_PWM, which is used to adjust the 9V_GATE output.

[0315] The gate driver circuit 39040 uses the input voltage signal 9V_GATE from the rail converter circuit 39020 to drive the heating engine drive circuit 3906.

[0316] In the exemplary embodiment shown in Figure 39, the rail converter circuit 39020 generates the input voltage signal 9V_GATE only when the vaping enable signal COIL_VGATE_PWM is asserted (present). The control device 2105 may deactivate the 9V rail to cut off power to the gate driver circuit 39040 by deasserting (stopping or terminating) the vaping enable signal COIL_VGATE_PWM. Similar to the vaping cutoff signal COIL_SHDN in the exemplary embodiment shown in Figure 38, the vaping enable signal COIL_VGATE_PWM may function as a device state power signal to perform a vaping-off operation in the nicotine e-vaping device 500. In this embodiment, the control device 2105 may perform a vaping-off operation by deasserting the vaping enable signal COIL_VGATE_PWM, thereby deactivating all power to the gate driver circuit 39040, the heating engine drive circuit 3906, and the heater 336. The control device 2105 may then enable vaping in the nicotine e-vaping device 500 by asserting the vaping enable signal COIL_VGATE_PWM to the rail converter circuit 39020 again.

[0317] Similar to the heater enable signal GATE_ON in Figure 38, the control unit 2105 may output a first heater enable signal GATE_ENB having a logic high level that enables power to the heating engine drive circuit 3906 and heater 336 in response to detecting vaping conditions in the nicotine e-vaping device 500. The control unit 2105 may also output a first heater enable signal GATE_ENB having a logic low level that disables power to the heating engine drive circuit 3906 and heater 336, thereby performing a heater off operation.

[0318] Referring more closely to the rail converter circuit 39020 in Figure 39, capacitor C36 is connected between the voltage source BATT and ground. Capacitor C36 functions as a storage unit for the rail converter circuit 39020.

[0319] The first terminal of coil L1006 is connected to node Node1, which is between the voltage source BATT and capacitor C36. Coil L1006 functions as the main energy storage element of the rail converter circuit 39020.

[0320] The second terminal of coil L1006, the drain of transistor Q1009 (e.g., an enhancement-mode MOSFET), and the first terminal of capacitor C1056 are connected at node Node2. The source of transistor Q1009 is connected to ground, and the gate of transistor Q1009 is configured to receive the vaping enable signal COIL_VGATE_PWM from control unit 2105.

[0321] In the embodiment shown in Figure 39, transistor Q1009 functions as the main switching element of the rail converter circuit 39020.

[0322] Resistor R29 is connected between the gate of transistor Q1009 and ground and acts as a pull-down resistor to ensure that transistor Q1009 switches off more reliably and that heater 336 does not operate when the vaping enable signal COIL_VGATE_PWM is in an uncertain state.

[0323] The second terminal of capacitor C1056 is at node Node3 and is connected to the cathode of Zener diode D1012 and the anode of Zener diode D1013. The anode of Zener diode D1012 is connected to ground.

[0324] The cathode of the Zener diode D1013 is connected at node 4 to the terminal of capacitor C35 and the input of the voltage divider circuit, which includes resistors R1087 and R1088. The other terminal of capacitor C35 is connected to ground. The voltage at node 4 is also the output voltage 9V_GATE output from rail converter circuit 39020.

[0325] Resistor R1089 is connected to the output of the voltage divider circuit at node 5.

[0326] In exemplary operation, the vaping enable signal COIL_VGATE_PWM is asserted at a high logic level, switching transistor Q1009 to a low impedance state (on), thereby allowing current to flow from the voltage source BATT and capacitor C36 through coil L1006 and transistor Q1009 to ground. This causes the current to increase linearly over time, and energy is stored in coil L1006.

[0327] When the vaping enable signal COIL_VGATE_PWM is at a logic low level, transistor Q1009 switches to a high impedance state (off). In this case, coil L1006 maintains current flow (decreases linearly), and the voltage at node Node2 increases.

[0328] The voltage rise for a given load is determined by the load cycle of the vaping enable signal COIL_VGATE_PWM. Therefore, the vaping enable signal COIL_VGATE_PWM is controlled by the closed-loop control device 2105 using the feedback signal COIL_VGATE_FB output by the voltage divider circuit at node Node5 as feedback. The above switching occurs at a relatively high speed (e.g., about 2 MHz, but different frequencies may be used depending on the required parameters and element values).

[0329] Referring further to the rail converter circuit 39020 in Figure 39, capacitor C1056 is an AC coupling capacitor that provides a DC block to remove DC levels. Capacitor C1056 cuts off current from the voltage source BATT through coil L1006 and diode D1013 to the gate driver circuit 39040 when the vaping enable signal COIL_VGATE_PWM is low to conserve battery life (e.g., when the nicotine e vaping device 500 is in standby mode). The capacitance of capacitor C1056 may be selected to provide a relatively low impedance path at the switching frequency.

[0330] The Zener diode D1012 establishes the ground level of the switching signal. Since the capacitor C1056 removes the DC level, the voltage at node Node3 can typically be bipolar. In one embodiment, the Zener diode D1012 can clamp the negative half-cycle of the signal approximately 0.3V below ground.

[0331] Capacitor C35 functions as an output storage unit for the rail converter circuit 39020. Zener diode D1013 prevents current from capacitor C35 from flowing through capacitor C1056 and transistor Q1009 when transistor Q1009 is on.

[0332] As the decaying current from coil L1006 causes a voltage rise at node Node4 between Zener diode D1013 and capacitor C35, the current flows into capacitor C35. Capacitor C35 maintains the 9V GATE voltage while the energy is stored in coil L1006.

[0333] The voltage divider circuit, including resistors R1087 and R1088, reduces the voltage to an acceptable level for measurement at the ADC in the control unit 2105. This reduced voltage signal is output as the feedback signal COIL_VGATE_FB.

[0334] In the circuit shown in Figure 39, the COIL_VGATE_FB voltage of the feedback signal is scaled by approximately 0.25x, and therefore the 9V output voltage is reduced to approximately 2.25V for input to the ADC in the control unit 2105.

[0335] Resistor R1089 provides current limiting against overvoltage faults at the output of rail converter circuit 39020 (for example, at node 4) to protect the ADC in control unit 2105.

[0336] The 9V output voltage signal 9V_GATE is output from the rail converter circuit 39020 to the gate driver circuit 39040, supplying power to the gate driver circuit 39040.

[0337] Next, referring more closely to the gate driver circuit 39040, the gate driver circuit 39040 includes, among other things, an integrated gate driver U2003 configured to convert one or more low-current signals from the control unit 2105 into high-current signals for controlling the switching of transistors (e.g., MOSFETs) in the heating engine drive circuit 3906. The integrated gate driver U2003 is also configured to convert a voltage level from the control unit 2105 into a voltage level required by the transistors in the heating engine drive circuit 3906. In the exemplary embodiment shown in Figure 39, the integrated gate driver U2003 is a half-bridge driver. However, exemplary embodiments should not be limited to this embodiment.

[0338] More specifically, the 9V output voltage from the rail converter circuit 39020 is input to the gate driver circuit 39040 through a filter circuit including resistor R2012 and capacitor C2009. The filter circuit including resistor R2012 and capacitor C2009 is connected at node 6 to the VCC pin (pin 4) of the integrated gate driver U2003 and the anode of Zener diode S2002. The second terminal of capacitor C2009 is connected to ground. The anode of Zener diode D2002 is connected at node 7 to the first terminal of capacitor C2007 and the boost pin BST (pin 1) of the integrated gate driver U2003. The second terminal of capacitor C2007 is connected at node 8 to the replacement node pin SWN (pin 7) of the integrated gate driver U2003 and to the heating engine drive circuit 3906 (e.g., between two MOSFETs). In the exemplary embodiment shown in Figure 39, the Zener diode D2002 and capacitor C2007 form part of a bootstrap charge pump circuit connected between the input voltage pin VCC and the boost pin BST of the integrated gate driver U2003. Since capacitor C2007 is connected to the 9V input voltage signal 9V_GATE from the rail converter circuit 39020, capacitor C2007 charges through diode D2002 to a voltage approximately equal to the voltage signal 9V_GATE.

[0339] Furthermore, referring to Figure 39, the high-side gate driver pin DRVH (pin 8), the low-side gate driver pin DRVL (pin 5), and the EP pin (pin 9) of the integrated gate driver U2003 are also connected to the heating engine drive circuit 3906.

[0340] Resistor R2013 and capacitor C2010 form a filter circuit connected to the input pin IN (pin 2) of the integrated gate driver U2003. The filter circuit is configured to remove high-frequency noise from the second heater enable signal COIL_Z input to the input pin. The second heater enable signal COIL_Z may be a PWM signal from the control unit 2105.

[0341] Resistor R2014 is connected to the filter circuit and input pin IN at node Node9. Resistor R2014 is used as a pull-down resistor so that when the second heater enable signal COIL_Z is floating (or indeterminate), the input pin IN of the integrated gate driver U2003 is held at a logic low level, preventing the heating engine drive circuit 3906 and heater 336 from starting.

[0342] The first heater enable signal GATE_ENB from the control unit 2105 is input to the OD pin (pin 3) of the integrated gate driver U2003. Resistor R2016 is connected to the OD pin of the integrated gate driver U2003 as a pull-down resistor so that if the first heater enable signal GATE_ENB from the control unit 2105 is floating (or indeterminate), the OD pin of the integrated gate driver U2003 is held at a logic low level, preventing the heating engine drive circuit 3906 and heater 336 from starting.

[0343] In the exemplary embodiment shown in Figure 39, the heating engine drive circuit 3906 includes a transistor (e.g., MOSFET) circuit including transistors (e.g., MOSFETs) 39062 and 39064 connected in series between the voltage source BATT and ground. The gate of transistor 39064 is connected to the low-side gate driver pin DRVL (pin 5) of the integrated gate driver U2003, the drain of transistor 39064 is connected to the replacement node pin SWN (pin 7) of the integrated gate driver U2003 at node Node 8, and the source of transistor 39064 is connected to ground GND.

[0344] When the low side gate drive signal output from the low side gate driver pin DRVL is high, transistor 39064 is in a low impedance state (on), thereby connecting node Node8 to ground.

[0345] As described above, since capacitor C2007 is connected to the 9V input voltage signal 9V_GATE from rail converter circuit 39020, capacitor C2007 charges through diode D2002 to a voltage equal to or approximately equal to the 9V input voltage signal 9V_GATE.

[0346] When the low side gate drive signal output from the low side gate driver pin DRVL is low, transistor 39064 switches to a high impedance state (off), and the high side gate driver pin DRVH (pin 8) is internally connected to the boost pin BST in the integrated gate driver U2003. As a result, transistor 39062 is in a low impedance state (on), thereby connecting the replacement node SWN to the voltage source BATT and pulling the replacement node SWN (node ​​8) to the voltage of the voltage source BATT.

[0347] In this case, node Node7 increases the gate-source voltage of transistor 39062 to a boost voltage V(BST) ≈ V(9V_GATE) + V(BATT), which can make the gate-source voltage of transistor 39062 identical or nearly identical to the voltage of the 9V input voltage signal 9V_GATE (e.g., V(9V_GATE)), regardless of (or independently of) the voltage from the voltage source BATT. As a result, the switching node SWN (node ​​8) provides a high-current switching signal that can be used to generate a voltage output on heater 336, which is nearly independent of the voltage output from the battery voltage source BATT.

[0348] Figures 40 and 41 show exemplary embodiments of a temperature-sensing transducer included in the pod sensor 2220.

[0349] Referring to Figure 40, the temperature sensing transducer 3600A includes a resistor R3602 and a sensor transducer R3604. In at least one exemplary embodiment, the resistor R3602 may have a fixed resistance of about 3 ohms. The sensor transducer R3604 may be a resistor having a variable resistance that changes with temperature. The resistor R3602 and the sensor transducer R3604 are placed in a voltage divider circuit so that the voltage across the sensor transducer R3604 (the voltage at measurement node N3606) can be output to the temperature measuring circuit 21250 so that it is used for scaling and then measuring the temperature of one or more elements of the nicotine pod assembly 300, such as the nicotine pod assembly 300 or the heater 336.

[0350] In an exemplary operation, the driver stage 3902A of the pod temperature measurement circuit 21250A (Figure 36) applies the pod temperature measurement power signal HW_POWER to the temperature sensing transducer 3600A, and the measurement stage 3904A of the pod temperature measurement circuit 21250A scales the sensing voltage of the pod sensor signal SP_HW at the measurement node N3606 and outputs the scaled voltage as the pod temperature measurement output signal HW_ to the control unit 2105. The control unit 2105 (or fault detection subsystem 2630) may then determine the temperature of the nicotine pod assembly 300 or one or more elements of the nicotine pod assembly 300 based on the pod temperature measurement output signal HW_SIGNAL.

[0351] In at least one exemplary embodiment, the voltage of the pod temperature measurement power signal HW_POWER may be fixed, and therefore the pod temperature measurement circuit 21250A can also calculate the current through resistors R3602 and R3604, since the resistance of resistor R3602 is a known resistance.

[0352] Referring to the exemplary embodiment shown in Figure 41, the temperature sensing transducer 3600B is similar to the temperature sensing transducer 3600A in Figure 40, except that, as described above with respect to Figure 37, resistor R3602 is omitted from the temperature sensing transducer 3600B and moved to the driver stage 3902B of the pod temperature measurement circuit 21250B in Figure 37. Moving resistor R3602 to the driver stage 3902B of the pod temperature measurement circuit 21250B can reduce the cost of the nicotine pod assembly electrical system 2200 and / or the number of pins required for the interface between the device body 100 and the nicotine pod assembly 300. Furthermore, the resistance of the sensor transducer R3606 in the exemplary embodiment shown in Figure 41 may be greater than the resistance of the sensor transducer R3604 in Figure 40 in order to reduce the current consumption by the temperature sensing transducer 3600B.

[0353] Figure 42A shows an exemplary embodiment of the power supply temperature measurement circuit 21254.

[0354] Referring to Figure 42A, the power supply temperature measurement circuit 21254A is configured to measure the temperature of the power supply 2110, for example, during charging. The power supply temperature measurement circuit 21254A estimates the battery temperature using the magnetic element of the RTH21254, which is placed relatively close to the power supply. The power supply temperature measurement circuit 21254A outputs the TEMP signal as a temperature signal EXT_TEMP to a dedicated charger IC, which may terminate charging, and if the temperature signal EXT_TEMP indicates that the temperature of the power supply 2110 exceeds the maximum temperature threshold, it may notify the fault detection subsystem 2630 of a fault.

[0355] The permissible temperature can be set by changing the ratio of resistors R21250 and R21252, thereby biasing the resistance of the voltage divider circuit including resistors R21250 and R21252. Capacitor C21254 is connected in parallel with resistors R21250, R21252 and thermistor RTH21254.

[0356] The power supply temperature measurement circuit 21254A can be powered by the USB voltage through the charger 2132 to eliminate any dependence on other system voltages (e.g., power supply voltage) during charging.

[0357] The power supply temperature measurement circuit 21254A may be a dedicated temperature measurement circuit for the charger IC of the charger 2132.

[0358] Figure 42B shows another exemplary embodiment of the power supply temperature measurement circuit 21254.

[0359] Referring to Figure 42B, the power supply temperature measurement circuit 21254B is functionally equivalent to the circuit shown in Figure 42A, but further includes a second power supply temperature sensor circuit configured to output a temperature signal BATT_TEMP_MCU to the control unit 2105 for determining whether the temperature of the power supply 2110 is outside its operating limits (e.g., exceeding the maximum threshold value or falling below the minimum threshold value) and whether a power supply temperature fault event has occurred.

[0360] More specifically, the power supply temperature measurement circuit 21254B includes a first power supply temperature sensor circuit that estimates the temperature of the power supply 2110 using a thermistor 21254B4 located relatively close to the power supply 2110. The first power supply temperature sensor circuit outputs a temperature signal BATT_TEMP_CHGR to a dedicated charger IC, which may terminate charging and notify the fault detection subsystem 2630 of a fault if the temperature of the power supply 2110 exceeds a maximum temperature threshold.

[0361] The power supply temperature measurement circuit 21254B further includes a second power supply temperature sensor circuit. The second power supply temperature sensor circuit is similar to the first power supply sensor circuit, except that the second power supply temperature sensor circuit outputs a temperature signal BATT_TEMP_MCU to the control device 2105.

[0362] More specifically, the second power supply temperature sensor circuit estimates the temperature of the power supply 2110 using a thermostat 21254B8, which is positioned relatively close to the power supply 2110. The second power supply temperature sensor circuit then outputs a temperature signal BATT_TEMP_MCU indicating the sensed temperature to the control unit 2105. The fault detection subsystem 2630 can determine, based on the temperature signal BATT_TEMP_MCU, whether a power supply temperature fault event has occurred in the nicotine e-vaping device 500. Capacitor C21254B is connected to ground and to the node between resistor 21254B9 and thermistor 21254B8.

[0363] The second power supply temperature sensor circuit also includes a temperature measurement control circuit 21254B6 configured to disable temperature measurement of the power supply 2110 and conserve power by isolating the voltage divider contained therein in a low-power mode (e.g., after automatic off operation). As shown in Figure 42B, the temperature measurement control circuit 21254B6 may include a transistor Q2001 connected between thermistor 21254B8 and ground. Transistor Q2001 can be selectively enabled and disabled based on the power measurement enable signal MEAS_EN from the control unit 2105 in order to selectively enable and disable the second power supply temperature sensor circuit.

[0364] Figure 43A shows an exemplary embodiment of the power supply voltage measurement circuit 21256.

[0365] Referring to Figure 43A, the power supply voltage measurement circuit 21256A uses a voltage divider circuit including resistors 21256A2 and 21256A4 to scale the power supply voltage measurement signal BATT_VOL and adjust it to match the input range of the ADC in the control unit 2105 (e.g., approximately 1.8V). Based on the power supply voltage measurement signal BATT_VOL, the control unit 2105 can determine the voltage level of the power supply 2110.

[0366] Capacitor C21256A is connected to ground and to the node between resistors 21256A2 and 21256A4.

[0367] The power supply voltage measurement circuit 21256A can reduce the additional drain of the power supply 2110 by utilizing a relatively large total resistance value (e.g., approximately 147 kΩ).

[0368] The control device 2105 may scale the power supply voltage measurement signal BATT_VOL to represent the actual voltage of the power supply 2110. The fault detection subsystem 2630 may determine that a power supply voltage fault has occurred if the power supply voltage falls below a minimum threshold level (e.g., approximately 3.6V).

[0369] Figure 43B shows another exemplary embodiment of the power supply voltage measurement circuit 21256. The exemplary embodiment shown in Figure 43B is similar to the exemplary embodiment shown in Figure 43A, but further includes a voltage measurement control circuit 21256B6 configured to disable the measurement of the voltage of the power supply 2110 and to conserve power by isolating the voltage divider contained therein in low-power mode. As shown in Figure 43B, the voltage measurement control circuit 21256B6 may include a transistor circuit including transistors Q3001 and Q3002, which are configured to be selectively enabled and disabled based on the power supply measurement enable signal MEAS_EN and to selectively enable and disable the power supply voltage sensor circuit 21256B.

[0370] Figure 44A shows an exemplary embodiment of the charger 2132.

[0371] Referring to Figure 44A, the charger 2132A includes a dedicated charging IC 4202A that provides multiple inputs / outputs (I / O) to manage the charging of the power supply 2110. Capacitors C2132A2 and C2132A4 are connected in parallel to each other between the VCC input and ground of the dedicated charging IC 4202A.

[0372] The dedicated charging IC 4202A is configured to output a power supply charging signal BATT_NCHRG to the control unit 2105. The power supply charging signal BATT_NCHRG may be a PWM modulated output configured to communicate one of four states: charging, charging complete, battery depleted, or battery temperature out of range. The fault detection subsystem 2630 may determine whether a fault event has occurred based on the power supply charging signal BATT_NCHRG. In one embodiment, a power supply charging signal BATT_NCHRG having a charging complete state may indicate a normal fault event (e.g., a complete fault event) to the fault detection subsystem 2630, and in response, the fault detection subsystem 2630 may output a normal fault event alarm to the automatic shutdown decision subsystem 2650. In another embodiment, a power charge signal BATT_NCHRG indicating a depleted battery state may indicate a hard fault device event (e.g., a power failure event) to the fault detection subsystem 2630, and in response, the fault detection subsystem 2630 may output a hard fault device event alarm to the automatic shutdown decision subsystem 2650. In yet another embodiment, a power charge signal BATT_NCHRG indicating an out-of-battery temperature range may indicate a hard fault device event to the fault detection subsystem 2630, and in response, the fault detection subsystem 2630 may output a hard fault device event alarm to the automatic shutdown decision subsystem 2650. The dedicated charging IC 4202A may output a power charge signal BATT_NCHRG indicating an out-of-battery temperature range in response to receiving a temperature signal BATT_TEMP_CHGR from the power temperature measurement circuit 21254.

[0373] The power control signal BATT_SUSP is an example of a device power status signal output by the control device 2105 to the dedicated charging IC 4202A, causing the charger 2132A to perform a stop operation, thereby stopping the charging of the power supply 2110 by the charger 2132A.

[0374] Charger 2132A is also configured to output a charging voltage signal BATT_V_ICHRG to control unit 2105. The charging voltage signal BATT_V_ICHRG represents the amount of current currently supplied to power supply 2110 by charger 2132A. Based on the charging voltage signal BATT_V_ICHRG, fault detection subsystem 2630 may monitor the current supplied to power supply 2110 by charger 2132A to determine whether the charging current is outside a range of values ​​(e.g., below a minimum threshold or above a maximum threshold, each of which may be determined based on empirical data). If fault detection subsystem 2630 determines that the charging current is outside a range of values, fault detection subsystem 2630 may output a hard fault device event alarm to automatic shutdown decision subsystem 2650.

[0375] According to at least some exemplary embodiments, a maximum overcurrent of about 105 percent of a specified maximum value may be used as an upper limit for the range of values. In one embodiment, for a maximum charging rate of 900 mA expected for the nicotine e-vaping device 500, a hard fault device event alarm would be output to the automatic shut-off decision subsystem 2650 at about 945 mA.

[0376] Since the charging current decreases as the battery approaches full charge, the lower limit of the range value does not necessarily need to be specified.

[0377] Figure 44B shows another exemplary embodiment of the charger 2132. The charger 2132B is similar to the circuit shown in Figure 44A, except that a different IC is used and the circuit further includes a charge rate selector 4404B. In the exemplary embodiment shown in Figure 44B, the capacitor 2132B is connected between the input IN and ground.

[0378] In the exemplary embodiment shown in Figure 44B, the dedicated charging IC 4402B maintains the same control and monitoring signals as described above with respect to Figure 44A (e.g., BATT_NCHRG, BATT_SUSP, BAT_V_ICHRG, etc.), but removes the built-in voltage regulator from the dedicated charging IC 4202A shown in Figure 44A.

[0379] The charging speed selector 4404B includes transistor Q2001A, and the control unit 2105 can select different charging currents using the charging current adjustment signal BATT_USB_TYP.

[0380] It should be understood that while exemplary embodiments are disclosed herein, other modifications are possible. Such modifications should not be considered to deviate from the scope of this disclosure, and all such modifications that would be obvious to those skilled in the art are intended to be included within the following claims.

Claims

1. Nicotine electronic vaping device, Nicotine pod assembly, A nicotine storage section for holding nicotine prevapor formulations, A nicotine pod assembly includes a heater configured to vaporize the nicotine prevapor formulation drawn from the nicotine storage section, A device body configured to engage with the nicotine pod assembly, A malfunction event in the nicotine electron vaping device is detected, The aforementioned failure event is classified as one of several types of failure events. The apparatus includes a control device configured to perform at least one resulting action based on the classification of the aforementioned failure events, The at least one resulting action includes an automatic shut-off operation, a heater shut-off operation, a vaping shut-off operation, a charging stop operation, or a combination thereof. The aforementioned failure event is one of the following: a soft failure pod event, a hard failure pod event, a soft failure device event, and a hard failure device event. A soft fault pod event is an abnormal condition within the nicotine pod assembly that does not require correction of the adult vapor interaction with the nicotine electronic vaping device, and a hard fault pod event is an abnormal condition within the nicotine pod assembly that requires correction of the adult vapor interaction with the nicotine electronic vaping device, and A nicotine electronic vaping device in which a soft malfunction event is an abnormal condition in the nicotine electronic vaping device in which vaping is disabled until a corrective action is performed, and a hard malfunction event is an abnormal condition in the nicotine electronic vaping device in which vaping is disabled at least and corrective action by adult vaper intervention is required.

2. The main body of the aforementioned device is The nicotine electronic vaping device according to claim 1, further comprising at least one vapor indicator configured to output a display indicating that the aforementioned malfunction has occurred.

3. The device body further includes memory, The control device is The power to the aforementioned heater is disabled, The occurrence of the aforementioned failure event is recorded in the memory, The nicotine electronic vaping device according to claim 2, configured to perform the at least one resulting action by causing the at least one vapor indicator to output the indication that the fault event has occurred.

4. The device body further includes memory, The control device is The vaping function of the aforementioned nicotine electronic vaping device is disabled, The occurrence of the aforementioned failure event is recorded in the memory, The nicotine electronic vaping device according to claim 2 or 3, configured to perform the at least one resulting action by causing the at least one vapor indicator to output the indication that the fault event has occurred.

5. The control device is The detachment of the nicotine pod assembly from the main body of the device is detected, The nicotine electronic vaping device according to claim 4, further configured to enable the vaping function in the nicotine electronic vaping device in response to detection of detachment of the nicotine pod assembly from the device body.

6. The nicotine electronic vaping device according to claim 3, 4, or 5, wherein the control device is further configured to cause the device body to enter sleep mode in response to determining that no corrective action has occurred in response to the malfunction event.

7. The device body further includes memory, The control device is The nicotine electronic vaping device enters sleep mode, activates an automatic shut-off function, The occurrence of the aforementioned failure event is recorded in the memory, The nicotine electronic vaping device according to any one of claims 2 to 6, configured to perform the at least one resulting action by causing the at least one vapor indicator to output the indication that the fault event has occurred.

8. The device body further includes memory, The control device is In the nicotine electronic vaping device, the vaping function, the charging operation, or the vaping function and the charging operation are disabled. The occurrence of the aforementioned failure event is recorded in the memory, The nicotine electronic vaping device according to claim 2, configured to perform the at least one resulting action by causing the at least one vapor indicator to output the indication that the fault event has occurred.

9. The control device is In response to detecting the aforementioned failure event, the reset timer is activated. The reset timer determines that the time has elapsed, The nicotine electronic vaping device according to claim 8, configured to reset the nicotine electronic vaping device in response to the reset timer determining that a time has elapsed.

10. The control device is It is determined that the aforementioned failure event has been cleared by the reset, The nicotine electronic vaping device according to claim 9, configured to enable the vaping function, the charging operation, or the vaping function and the charging operation in response to determining that the fault event has been cleared by the reset.

11. The aforementioned reset is A software application running on the aforementioned control device is reset, a soft reset. The software application running on the control device and the hardware of the nicotine electronic vaping device are reset, hard reset, or The nicotine electronic vaping device according to claim 9 or 10, comprising one of the power-on resets (PORs) that include generating a reset impulse in all the circuits of the nicotine electronic vaping device.

12. The control device is The corrective action in the nicotine electron vaping device is detected, A nicotine electronic vaping device according to any one of claims 8 to 11, configured to enable the vaping function, the charging operation, or the vaping function and the charging operation in response to detecting the correction action.

13. The nicotine pod assembly includes a memory configured to store threshold temperature values, The control device is The threshold temperature value is obtained from the memory, The temperature of the heater is estimated during the operation of the nicotine electron vaping device. A nicotine electron vaping device according to any one of claims 1 to 12, configured to detect a malfunction event in response to determining that the temperature of the heater is equal to or greater than the threshold temperature value.

14. The main body of the device further includes a power supply configured to supply power to the nicotine electronic vaping device, The aforementioned fault event is a low-voltage fault event of the power supply, indicating that the voltage of the power supply is below a minimum threshold. The nicotine electronic vaping device according to any one of claims 1 to 13, wherein the control device is further configured to perform the at least one resulting action by disabling the vaping function in the nicotine electronic vaping device in response to detecting a low-voltage fault event in the power supply.

15. The main body of the device further includes a power supply configured to supply power to the nicotine electronic vaping device, The aforementioned failure event is a temperature failure event of the power supply, indicating that the temperature of the power supply is above a maximum threshold. The nicotine electronic vaping apparatus according to any one of claims 1 to 14, wherein the control device is configured to perform at least one resulting action by preventing the charging of the power supply in response to detecting a temperature-related malfunction event of the power supply.

16. A method for operating a nicotine electronic vaping device, To detect malfunctions in the nicotine electron vaping device, Classifying the aforementioned failure event as one of several types of failure events, This includes performing at least one resulting action based on the classification of the aforementioned failure events, The at least one resulting action includes an automatic shut-off operation, a heater shut-off operation, a vaping shut-off operation, a charging stop operation, or a combination thereof. The aforementioned failure event is one of the following: a soft failure pod event, a hard failure pod event, a soft failure device event, and a hard failure device event. A soft fault pod event is an abnormal condition within the nicotine pod assembly that does not require correction of the adult vapor interaction with the nicotine electronic vaping device, and a hard fault pod event is an abnormal condition within the nicotine pod assembly that requires correction of the adult vapor interaction with the nicotine electronic vaping device, and A soft malfunction event is an abnormal condition in the nicotine electronic vaping device in which vaping is disabled until a corrective action is performed, and a hard malfunction event is an abnormal condition in the nicotine electronic vaping device in which vaping is disabled at least and corrective action by adult vaper intervention is required, in a method.

17. Performing at least one of the resulting actions is, Disabling the power to the heater in the aforementioned nicotine electronic vaping device, The occurrence of the aforementioned malfunction event is recorded in the memory of the nicotine electronic vaping device, and The method according to claim 16, which includes outputting a display indicating that the aforementioned malfunction has occurred.

18. Performing at least one of the resulting actions is, Disabling the vaping function in the aforementioned nicotine electronic vaping device, The occurrence of the aforementioned malfunction event is recorded in the memory of the nicotine electronic vaping device, and The method according to claim 16 or 17, further comprising outputting a message indicating that the aforementioned malfunction has occurred.

19. To detect the removal of the nicotine pod assembly from the nicotine electronic vaping device, and The method according to claim 18, further comprising enabling the vaping function in the nicotine electronic vaping device in response to detecting the removal of the nicotine pod assembly from the nicotine electronic vaping device.

20. The method according to any one of claims 16 to 19, further comprising, in response to the aforementioned malfunction event and in response to determining that no corrective action has occurred, causing the nicotine electronic vaping device to enter sleep mode.

21. Performing at least one of the resulting actions is, The nicotine electronic vaping device enters sleep mode, and an automatic shut-off operation is activated. The occurrence of the aforementioned malfunction event is recorded in the memory of the nicotine electronic vaping device, and The method according to any one of claims 16 to 20, which includes outputting a display indicating that the aforementioned malfunction has occurred.

22. Performing at least one of the resulting actions is, Disabling the vaping function, charging operation, or the vaping function and charging operation in the nicotine electronic vaping device. The occurrence of the aforementioned malfunction event is recorded in the memory of the nicotine electronic vaping device, and The method according to claim 16, which includes outputting a display indicating that the aforementioned malfunction has occurred.

23. In response to detecting the aforementioned failure event, the reset timer is activated. The reset timer determines that the time has elapsed, and The method according to claim 22, further comprising performing a reset of the nicotine electronic vaping device in response to the reset timer determining that the time has elapsed.

24. It is determined that the aforementioned failure event has been cleared by the reset. The method according to claim 23, further comprising enabling the vaping function, the charging operation, or the vaping function and the charging operation in the nicotine electronic vaping device in response to determining that the fault event has been cleared by the reset.

25. The aforementioned reset is The software application running on the control unit is reset, a soft reset. The software application running on the control device and the hardware of the nicotine electronic vaping device are reset, hard reset, or The method according to claim 23 or 24, which is one of the power-on resets (PORs) that includes generating a reset impulse to all circuits of the nicotine electronic vaping device.

26. To detect the corrective effect in the nicotine electron vaping device, and The method according to claim 23, 24, or 25, comprising enabling the vaping function, the charging operation, or the vaping function and the charging operation in the nicotine electronic vaping device in response to detecting the corrective action.

27. The detection of the failure event is The threshold temperature value is obtained from the memory of the nicotine electron vaping device. To estimate the temperature of the heater in the nicotine electron vaping device, and The method according to any one of claims 16 to 26, further comprising detecting the failure event in response to determining that the temperature of the heater is equal to or greater than the threshold temperature value.

28. The aforementioned fault event is a low-voltage power supply fault event indicating that the power supply voltage in the nicotine electronic vaping device is below a minimum threshold. The method according to any one of claims 16 to 27, wherein performing the at least one resulting action includes disabling the vaping function in the nicotine electron vaping device in response to detecting a low-voltage fault event in the power supply.

29. The aforementioned failure event is a power supply temperature failure event indicating that the temperature of the power supply in the nicotine electronic vaping device is above the maximum threshold. The method according to any one of claims 16 to 28, wherein performing the at least one resulting action includes preventing charging of the power supply in response to detecting a temperature fault event in the power supply.

Images