Aerosol delivery device and method of operation thereof
Patent Information
- Application Number
- JP2023071702
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2018-12-17
- Filing Date
- 2023-04-25
- Publication Date
- 2025-03-03
- Estimated Expiration
- 2039-12-17
Smart Images
Figure 0007638320000001 
Figure 0007638320000002 
Figure 0007638320000003
Abstract
Description
Field and Background
[0001] FIELD OF THE DISCLOSURE
[0001] This disclosure relates to built-in connectivity, and particularly, but not exclusively, to electronic nicotine delivery devices and methods having selectively operable connectivity features.
[0002]
[0002] Known electronic delivery (END) devices can make it possible to provide an inhalable aerosol containing nicotine on demand. Such END devices can be provided with a wireless communication interface for communicating data collected within the device to an external base station or dock.
[0003]
[0003] Examples of known approaches are described in US Patent Application Publication No. 2016 / 0029697, German Utility Model No. 202013009601, US Patent Application Publication No. 2013 / 0284192, US Patent Application Publication No. 2014 / 0174459, US Patent Application Publication No. 2011 / 0265806, US Patent Application Publication No. 2013 / 0340775, and in a post from the XDA developers forum entitled "[Q] Automatically turn on WiFi ONLY when charging?" posted by kingkeld on April 3, 2011. Overview
[0004]
[0004] Some particular aspects and embodiments are set out in the accompanying claims.
[0005]
[0005] In view of a first aspect, an electronic nicotine delivery (END) device may be provided, comprising a wireless local area network (WLAN) or wireless telecommunications connection interface configured to establish a wireless data connection to a wireless local area network access point to provide data connectivity from the END device to a remote management service, a charging connector configured to receive a power input for recharging a power source of the END device, and a circuit configured to selectively activate the connection interface in response to an ongoing or predicted receipt of power via the charging connector. Thus, it is enabled that a relatively simple END device may be able to control power consumption to enable the device to directly connect to the Internet and transmit data when the power source is effectively unlimited or predicted to be sufficient for the device's primary function.
[0006]
[0006] In view of a further aspect, there may be provided a method of operating an END device, the END device comprising a wireless local area network (WLAN) or wireless telecommunications connection interface configured to establish a wireless data connection to a WLAN or wireless telecommunications network to provide data connectivity from the END device to a remote management service, the method including receiving, via a charging connector, a power input for recharging a power source of the END device, and selectively activating the connection interface in response to an ongoing receipt of power via the charging connector, thereby conserving power for END functions in that battery drain due to data transmission is avoided.
[0007]
[0007] In view of another aspect, a method of operating an END device may be provided, the END device comprising a wireless local area network (WLAN) or wireless telecommunications connection interface configured to establish a wireless data connection to a WLAN or wireless telecommunications network to provide data connectivity from the END device to a remote management service, the method including the steps of determining a predicted time for receiving a power input for recharging a power source of the END device via a charging connector, and selectively activating the connection interface in response to a determination that a power consumption caused by activation of the connection interface is replenished at a predicted time prior to depletion of a power source due to use of the connection interface and END use of the END device, thereby conserving power for END functions in that a load on a power supply due to data transmission is controlled such that excessive depletion of the power supply is avoided.
[0008]
[0008] In view of a further aspect, a method for managing an END device may be provided, the method including the steps of: detecting or predicting application of a charging power supply to the END device to activate a connection interface of a wireless local area network (WLAN) wireless telecommunication of the END device or a power supply depending on the presence of the power supply; activating the connection interface in response to the detection or prediction of application of charging power to detect whether the END device is within the service range of a WLAN or wireless telecommunication network, the network providing data connectivity to a remote management service; and enabling the END device to connect to the network when the connection interface is activated to enable the END device to connect to the remote management service and receive data from and / or provide data to the remote management service. Thus, power can be conserved for the END functions in that the load on the power supply due to data transmission is controlled to maintain a sufficient charge to cover expected END function usage.
[0009]
[0009] Embodiments of the present teachings will now be described, by way of example only, with reference to the accompanying drawings, in which: [Brief description of the drawings]
[0010] [Figure 1] FIG. 1 is a schematic diagram of connectivity to an END device.
[0011] [Diagram 2] FIG. 2 is a schematic diagram of an END device.
[0012] [Diagram 3] FIG. 3 is a schematic diagram of connectivity in access point mode.
[0013] [Figure 4] FIG. 4 is a schematic diagram of a user interface.
[0014] [Diagram 5] FIG. 5 is a schematic diagram of a method for determining when data communication should occur.
[0015] [Figure 6] FIG. 6 is a schematic diagram of a method for determining when data communication should occur.
[0016] [Figure 7] FIG. 7 is a schematic diagram of a method for determining when data communication should occur.
[0017] While the techniques described herein are susceptible to various modifications and alternative forms, specific embodiments are shown by way of example in the drawings and are described in detail below. It should be understood, however, that the drawings and detailed description of the drawings are not intended to limit the scope to the particular forms disclosed. On the contrary, the scope is intended to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims. DETAILED DESCRIPTION
[0018]
[0018] The present embodiment is directed to providing data connectivity to / from an END device in a manner that emphasizes the primary device function (the END function) versus power consumption caused by auxiliary functions (data connectivity) within the device.
[0019] 1, according to the present approach, an END device 2 is configured to be connected to receive charging power from a power supply 4. The supply of power from the power supply 4 to the END device 2 may be wired (e.g., using a connector cable or a docking connector) or wireless (e.g., using inductive charging from a charging station, dock or housing).
[0020]
[0020] The END device 2 is also configured to be connected to an access point 8 via a data connection 6. The access point 8 is configured to communicate via a data connection 10 to a connecting network 12. The connecting network 12 is configured to communicate via a data connection 14 to a remote service 16. The remote service 16 provides one or more services to which the END device may request access, e.g. an error condition recording service, a user account service, etc.
[0021]
[0021] According to one envisaged embodiment, the data connection 6 is a Wi-Fi connection (e.g., an IEEE 802.11x connection) and the access point 8 is a Wi-Fi access point or router. The data connection 10 provides onward data connectivity to a network 12 representing the Internet or a part of the Internet. According to another envisaged embodiment, the data connection 6 is a wireless telecommunications connection (e.g., a 2G, GRPS, 3G, 3.5G, EDGE, 4G or 5G cellular communication interface) and the access point 8 is a base station or access point of a wireless telecommunications network. The data connection 10 provides onward data connectivity through the telecommunications network to a network 12 representing the Internet or a part of the Internet. In some embodiments, the network 12 alternatively represents a private network such as a WAN.
[0022]
[0022] As is evident from the connectivity examples provided, the connectivity type is a relatively long-range data connectivity option that allows access to a data infrastructure to ultimately reach remote services. As is also evident, the connectivity type is relatively high power intensive (e.g., when compared to Bluetooth, BTLE, or Zigbee). Thus, the inventive approach provides a mechanism for managing power usage using the above relatively high power connection interfaces such that data connectivity avoids depleting the power reserve of the power source (e.g., battery) in the END device to a level where END functionality is hindered or inhibited.
[0023]
[0023] Figure 2 provides a schematic diagram of components within the END device 2. The END module 20 is configured to generate an aerosol containing nicotine upon activation. The END module can be configured to generate the aerosol by evaporating a nicotine-containing liquid into an airflow using a heater. The aerosol containing nicotine is then delivered to the user through the mouthpiece of the END device 2. Activation of the END module is triggered using an activation switch 22. The activation switch may be a physical switch or button accessible on the surface of the END device 2 to facilitate manual activation, or alternatively, a switch configured to detect the intended use of the END device 2, such as, for example, a pressure switch configured to detect airflow into or through the END module 20 triggered by the user initiating an inhale through the mouthpiece. In some examples, the activation switch 22 may be integrated into the END module 20. In some embodiments, the END module may be composed of multiple sub-modules, such as separate aerosol generation and nicotine-containing liquid reservoir modules.
[0024]
[0024] As also shown in FIG. 2, a power source 24 (such as a battery) is provided in the END device. The power source 24 is connected to power the END module 20 via an activation switch 22. To enable the power store in the power source 24 to be replenished, a charging connector 26 is provided that is configured to receive power from a power supply (such as the power supply 4 shown in FIG. 1). As mentioned above, power may be provided via a wired connection (such as a cable connector or a dock connector). In such cases, the charging connector 26 includes a physical connector that corresponds to the wired supply. As also mentioned above, power may be provided by a wireless supply (such as an inductive charging station, dock or housing). In such cases, the charging connector 26 includes a wireless charging receiver that corresponds to the wireless supply. In some examples, the END device may be provided with both wired and wireless charging connectors and / or multiple wired connectors that match multiple different power supply connector formats.
[0025]
[0025] Once charging power is received by charging connector 26, charging module 28 enables charging of power source 24. Charging module 28 enables controlled charging of power source 24 in accordance with any applicable power management guidance of power source 24, for example, providing a charge rate and / or overcharge protection that maximizes battery life. In some examples, charging module 28 may be integrated into charging connector 26 or power source 24.
[0026]
[0026] As further shown in FIG. 2, the charging module 28 is also connected to a control circuit 30. The control circuit 30 is further connected to a wireless connection interface 32, such as a wireless local area network (WLAN) or wireless telecommunications connection interface. If the connection interface 32 is a WLAN connection interface, it may include a Wi-Fi interface (e.g., an IEEE 802.11x connection). If the connection interface 32 is a wireless telecommunications connection interface, it may include a wireless telephone communication connection interface (e.g., a 2G, GRPS, 3G, 3.5G, EDGE, 4G or 5G cellular telephone communication interface). The connection interface includes both WLAN and wireless telecommunications capabilities in some embodiments. The control circuit 30 is configured to operate the connection interface 32 in response to charging power actually being received or predicted to be received at the charging connector 26. The determination that charging power is actually being received at the charging connector 26 may be enabled by a connection from the charging module 28. The determination that charging power is expected to be received at charging connector 26 may be enabled by one or more determinations by control circuitry 30, as described further below. The control circuitry may be provided by one or more elements capable of performing control tasks based on various inputs, such as a microprocessor, a microcontroller, an application specific integrated circuit, and / or discrete analog and / or digital circuit elements.
[0027]
[0027] The control circuit 30 of this embodiment is further connected to the END module 20, the activation switch 22, and the power source 24. Through these connections (some of which may be omitted in different embodiments), the control circuit 30 can collect information from and / or provide control inputs to any of the elements or modules to which the control circuit is connected. For example, the connection to the activation switch 22 can enable the control circuit to count the number of activations of the END module, the duration of each activation of the END module, read or set the sensitivity of the activation switch 22, etc. Also, for example, the connection to the END module 20 can enable the control circuit 30 to read or set the current heater power of the heater in the END module 20, read the current hold of nicotine-containing fluid in the END module, etc. Furthermore, for example, the connection to the power source 24 can enable the control circuit 30 to read the power reserve level.
[0028]
[0028] The control circuitry 30 may store data collected from the various connected elements and modules for transmission to a remote service, such as the remote service 16 shown in Figure 1. The control circuitry may also store the current settings of the controllable parameters of the various connected elements and modules. When the END device accesses the remote service using the connection interface 32, any collected data and / or the stored current settings may be transmitted and / or the remote service may provide updates regarding the current settings.
[0029]
[0029] The communication between the connection interface 32 of the END device 2 and the remote service 16 may use conventional communication protocols associated with WLAN and / or remote communication networks, compatible with eventual transmission to the remote service 16 via the Internet (or WAN). The encoding of data for transmission over a data link established using the above protocols may be end-to-end encrypted to provide data security. Additionally or alternatively, the data may be encoded in a proprietary format that anonymizes or obscures potentially identifiable or confidential information carried by the data.
[0030]
[0030] In some embodiments, the connection interface 32 is configured to allow connection only to pre-configured networks, e.g., networks whose access details are pre-stored by the END device (e.g., stored by the control circuitry 30 or the connection interface 32). This can allow data connections to be provided only via known (e.g., trusted) networks. In an example where the connection interface 32 includes a WLAN interface, the WLAN interface can be operable in an access point mode. In the access point mode, the END device can be capable of wirelessly interfacing with a computing device, as shown in FIG. 3.
[0031]
[0031] As shown in Fig. 3, the END device 2 (with the connection interface 32 in WLAN access point mode) can be connected to a WLAN-enabled computing device 42 via a data connection 40. The computing device may be, for example, a desktop computer, a laptop computer, a tablet computer, a phablet device, or a smartphone device. The computing device 42 includes a user interface display 44 and may include one or more buttons 46. The user interface display 44 may additionally (or alternatively to providing the optional button 46) be a touch-sensitive input device. The user interface display 44 and any buttons and / or touch-sensitive input device may be used to connect to a WLAN network broadcast from an END device connection interface operating in WLAN access point mode, and then used to display a user interface provided by the END device for use in the access point mode. The user interface may be used to pre-configure settings of a WLAN and / or wireless telecommunications network that may be used to connect to a remote service 16.
[0032] An exemplary user interface 50 that may be provided by the END device for display on the user interface display 44 of the computing device 42 is shown in FIG. 4. The exemplary user interface 50 includes a number of field labels 52 (52a, 52b, 52c, 52d) and a number of corresponding field data areas 54 (54a, 54b, 54c, 54d) in which data for the respective field 52 may be entered. For example, when configuring for access to a WLAN such as an IEEE 802.11x network, the field label 52a may be an SSID and the field data 54a may be used to enter the SSID of the intended network for which the END device is configured. Similarly, other fields may relate to a username, password, other forms of network identifiers, security type settings, etc. The number of field labels and field data areas may vary depending on the type of network being configured. The illustrated user interface also includes a save or execute selector 56 that may be actuated to complete the network pre-configuration. Entering data into the field data areas 54 and selecting the save selector 56 may be performed using the controls of the particular computing device 42. The user interface may also present multiple sets of fields and data fields, all on a single page, or on multiple navigable pages, to pre-configure multiple different networks, such that an END device may be connectable to a variety of networks, for example, corresponding to multiple different anticipated usage locations of the END device.
[0033]
[0033] In some embodiments, the END device may include functionality for a personal area network data connection, such as Bluetooth™, BTLE™ or Zigbee™. Such functionality may be provided by the connection interface 32 or a separate additional connection interface. Such personal area network data connection may be used to present a user interface for pre-configuration of a WLAN and / or wireless telecommunications network instead of (or in addition to) presenting such an interface using the access point mode of the connection interface.
[0034]
[0034] If an approach is used to allow pre-configuration of an END device for one or more wireless networks, the END device may be restricted to only allow data connections to remote services to be made using the pre-configured WLAN and / or telecommunications network.
[0035]
[0035] Using such an END device, various intelligent power management techniques can be deployed. In this embodiment, the END device has a primary function of delivering an electronically generated nicotine-containing output. The END device therefore utilizes power management to conserve power for this primary function. In addition, the END device has an auxiliary function of providing remote data access for transmitting and receiving data related to the operation and / or configuration of the device, such as log data, error condition data, setting data and / or usage data. The implementation of the remote data access function relies on a wireless connection interface that utilizes a remote communication technology, such as WLAN or wireless remote communication technology. Such remote communication technology tends to require relatively high power consumption compared to the intermittent operation of a small heating element in the END module used to vaporize small amounts of nicotine-containing fluid. Thus, the power management approach of this embodiment is directed to controlling the operation of the wireless connection interface to manage power consumption so as to reduce or minimize the risk that the auxiliary function of remote data access consumes too much power, making it impossible to use power for the primary function.
[0036] 5 shows an example control flow for managing power consumption with remote data access to conserve power for primary functions. In this embodiment, the control flow is implemented in the control circuit 30, but in other embodiments, the control flow may be distributed among one or more separate control elements of the END device or may be distributed within the END device.
[0037] Beginning at step S5-1, control circuitry 30 monitors the connection to charging module 28 to detect when delivery of charging power begins. If it is detected at step S5-3 that power is being received, processing continues at step S5-5; if not, monitoring continues at S5-1. Monitoring may take the form of receiving a trigger signal (such as an interrupt signal or a simple signal level signal) upon connection from the charging module. Monitoring may also monitor that power delivery has occurred for a certain threshold continuous duration before a determination is made that power delivery has commenced, to allow processing to continue at step S5-5, to allow power delivery to stabilize, and / or to allow a certain amount of power reserve to be replenished before wireless communication begins.
[0038]
[0038] After power delivery is initiated, in step S5-5, the control circuitry 30 controls the connection interface 32 to be activated. The connection interface is then activated to search for or monitor available networks (such as preconfigured WLANs or telecommunications networks) to which a connection to the remote service 16 may be established. In step S5-7, the control circuitry determines whether a connection is possible based on a response from or behavior of the connection interface 32. For example, the connection interface may provide a positive report of connectability, or the control circuitry may assume that a connection is not possible if a report of a possible connection is not received within a timeout period. If a connection is not possible, the connection interface is deactivated and monitoring of power receipt is resumed.
[0039]
[0039] If, in step S5-7, it is determined that a connection is possible, then, in step S5-9, data communication is commenced by establishing a connection to the remote service 16 for the transmission and / or reception of data and / or configuration information. The data communication continues between the END device and the remote service 16 in step S5-11.
[0040]
[0040] During data communication, an optional step S5-13 may be performed of monitoring whether power delivery is interrupted. When step S5-13 is performed, one or more power delivery monitoring techniques can be applied. The simplest monitoring is to determine whether there is an interruption in power delivery. More complex monitoring techniques can provide resistance to temporary interruptions caused, for example, by the power cable being accidentally disconnected for a short duration or by disturbances to the wireless charging station. For example, a pause in power delivery can be determined if the interruption in power delivery exceeds a threshold duration and / or if a threshold number of short duration interruptions have occurred (e.g., each short duration interruption is shorter than the threshold duration).
[0041]
[0041] When step S5-13 is performed, if no power interruption is detected, data communication is allowed to continue to be performed in step S5-13. On the other hand, if a power delivery interruption is detected, an orderly pause of data communication can be performed in step S5-17. An orderly pause can include, for example, completing the transmission of a current data exchange, such as an updated configuration package or a batch of report data, but not necessarily completing the transmission of the entire hold of data or configuration that is intended to be transmitted but has not yet begun. By implementing an orderly pause of data communication, the possibility of suboptimal performance or malfunction that may be caused by an incomplete configuration update can be reduced. In another example, for example, if the END device control circuitry is tolerant of the above errors, the orderly pause can be omitted, and the connection interface is disabled regardless of the state of the transmission queue or the session status. Regardless of which approach is taken to pause data communication in step S5-17, the connection interface is disabled and processing returns to S5-1 to continue monitoring for the presence of a power supply.
[0042]
[0042] Assuming there is no power supply interruption which would cause premature cessation of data communication, data communication continues until completion which is identified at S5-15. Once data communication is completed, processing continues at step S5-17 for data communication to be halted, except that established links to remote connections are closed and connection interfaces are disabled, and processing returns to S5-1 to continue monitoring for the presence of power supply.
[0043]
[0043] It can therefore be seen that the control circuit can enable a relatively high load wireless interface implementing a remote data communication technology, such as WLAN or wireless telecommunication technology, to be operated when charging power is received, so as to enable the relatively high load to avoid depleting power reserves that may be required for the primary function of the END device.
[0044]
[0044] Another embodiment of power management for data communication is shown in relation to Fig. 6. This embodiment applies the same principle of avoiding that data communication causes depletion of the power reserve so as to interfere with the primary functionality of the END device. The method of Fig. 6 can be used in combination with the method of Fig. 5 to allow both data communication when charging power is received (as in Fig. 5) and data communication based on the prediction that charging power will be received (as explained below).
[0045]
[0045] In this embodiment, the control circuitry may include or have access to a clock that keeps track of time, for example using conventional time-of-day or time-difference techniques. The control circuitry may also store or have access to a memory in the END device that stores patterns of previous usage of the END device with respect to primary functions and receipt of charging power. By comparing the stored patterns to the clock, a prediction may be made as to when the next charging is expected (e.g., if historical data indicates that charging occurred periodically at approximately the same time of day over many days, or at intervals of a certain number (or range) of hours). Also, by comparing the patterns to the clock, a prediction may be made as to the amount of usage of the primary functions that may be expected between the current time and the next expected charging time, which may utilize patterns of expected usage in addition to or instead of using patterns of previous usage. The prediction may be based, for example, on a default typical usage pattern, or may represent usage by the same user of different END devices, or other users with a similar lifestyle to the user.
[0046]
[0046] By determining the amount of power usage predicted for the primary function between the current time and the next predicted charging time, and knowing the predicted power load of the data transmission session (which may be estimated based on knowing the size of the current log of data waiting to be transmitted to the remote service and the predicted power load over time of the connection interface), a determination may be made as to whether communication can occur without jeopardizing power availability for the predicted primary function usage. The calculation may include providing a contingency power reserve below which both predicted data communication and predicted primary function usage prior to the predicted charging time will not cause the power reserve to drop.
[0047]
[0047] Thus, as shown in Figure 6, in step S6-1 a determination is made of the amount of data for transmission, and the estimated power consumption of the transmission of that data is determined in S6-3. The determination may include an assumed amount of data for reception, such as the amount of data contained in a complete configuration update that may be provided by a remote service. Also, in S6-5, the current power reserve is determined. Further, in S6-7, a predicted time until the next charge is determined, for example, using a clock and stored usage patterns as described above. In S6-9, another determination of predicted END (i.e. primary function) usage until the next charge point is made. As will be appreciated, the order of steps S6-1 to S6-9 may be changed (or the steps may be performed in parallel), except that S6-3 uses the result of S6-1 and S6-9 uses the result of S6-7.
[0048]
[0048] Then, in S6-11, all of the decisions made in S6-1 through S6-9 are utilized to determine the amount of power reserve remaining if a predicted END usage and data transmission occurs prior to the next predicted charging time point. This remaining power reserve is then compared in S6-13 to a threshold power reserve to be maintained (which, as discussed above, may be greater than zero to maintain a contingency reserve in case charging is delayed).
[0049]
[0049] If it is determined that the remaining power reserve is greater than the threshold, then in S6-15 data transmission is performed by activating the connection interface, establishing a connection to the remote service, and communicating the data as previously described. If there is no network available to effect the transmission at the time the connection interface is activated, the data transmission will be delayed. In that situation, a retry of activation of the connection interface to establish a connection to the remote service may be performed after a delay time without necessarily re-performing steps S6-1 to S6-13, since it has already been determined that the power reserve situation is acceptable.
[0050] On the other hand, if in S6-13 it is determined that the remaining power reserve will be below the threshold, then in S6-17 a decision is made to wait for a charging event before attempting data communication.
[0051]
[0051] Thus, it can be seen that the control circuit can enable a relatively high load wireless interface implementing a remote data communication technology, such as a WLAN or wireless telecommunication technology, to be operated when the power reserve is not excessively depleted prior to a predicted charging event, so as to enable the relatively high load to avoid depleting the power reserve that may be required for the primary function of the END device.
[0052]
[0052] The approach can also take into account that different data for transmission may have different priorities. For example, data recording usage statistics may be considered a low priority, while data requiring earlier attention, such as data indicating imminent depletion of the nicotine-containing liquid in the END module, may be transmitted earlier and considered a higher priority, to avoid operational inactivity occurring without notification. Another example of higher priority data may be operational data indicating actual or potential malfunctions, such as those that may be caused by misuse or damage of the END device.
[0053]
[0053] To reflect the different priorities, the control circuitry may have the ability to activate the connection interface to transmit high priority data without reference to the charging and / or power reserve status. For example, if the data indicates that the END device may be inoperable for primary functions for reasons other than power reserve, the communication of that data may be appropriately performed regardless of the power reserve status. Also, the user may have the option to indicate, using a setting in the device, that certain categories of data should be fed back with high priority. One example of such data may be that the user is utilizing the END device to reduce nicotine dependence and wishes to be alerted if the delivery of nicotine over a given time exceeds a certain threshold, to alert the user that they may need to reduce their use of the END device.
[0054]
[0054] Thus, as shown in Figure 7, at step S7-1 a decision is made as to the priority of the data waiting to be transmitted.
[0055]
[0055] A test is performed (S7-3) to determine whether any of the data waiting to be transmitted has high priority, and if the data does have high priority, then in S7-5 data transmission is performed for the high priority data by activating the connection interface, establishing a connection to the remote service, and communicating the data as previously described. If at the time the connection interface is activated there is no network available to effect the transmission, then the data transmission will be delayed. In that situation, since the high priority has already been determined, a retry of activation of the connection interface to establish a connection to the remote service may be performed after a delay time without necessarily re-performing steps S7-1 to S7-3.
[0056]
[0056] Data that does not have high priority is retained for later transmission in S7-5. Thereafter, or if it is determined in S7-3 that there is no data that has high priority, power-based data transmission is performed in S7-7, for example based on either or both of a current charging power approach as shown in Figure 5 and a projected charging power approach as shown in Figure 6.
[0057]
[0057] Thus, it can be seen that the control circuit can provide a high data priority to enable relatively high priority data to be communicated in a timely manner, to alleviate concerns about a relatively high load wireless interface implementing a remote data communication technology, such as a WLAN or wireless remote communication technology, excessively depleting the power reserve prior to an anticipated charging event.
[0058] Thus, various techniques have been described for maintaining power reserve for the primary functions of the END device by controlling the activation of data communications to remote services via a remote communications interface.
[0059]
[0059] Although it is discussed above that the END device itself includes a wireless connection interface, the present approach also applies to situations in which the END device is associated with a portable docking station (e.g., a carry case) that includes a wireless connection interface, in which the END device, when docked in the docking station, can access the wireless connection interface via a wired or wireless (e.g., personal area network) connection to the docking station.
[0060]
[0060] Thus, from one perspective, the described approach can be seen to relate to the concept of controlling power consumption of simple (i.e., low processing power, limited UI) devices that can connect directly to the Internet (i.e., without using a mobile application that proxies the connection). However, due to the lack of a substantial UI on the device and the potential power requirements of interfaces such as WiFi, the approach has a manner in which the device becomes connected and transmits data only when the power source is effectively unlimited or predicted to be sufficient for the primary functionality of the device.
[0061]
[0061] The device has a WLAN or wireless telecommunication interface (or works with a docking station having such an interface). A particular example of a device is an aerosol delivery device (e-cigarette), but alternative devices can also benefit from the connectivity control. The device can be programmed to connect to one or more predefined networks, but the connection can be restricted when the device is charging (whether by charging cable, docking station charging or wireless charging) or when the predicted power reserve after the connection is complete is sufficient to cover the predicted level of primary functionality usage before the next charge. Such power-dependent constraints may be overridden by the transmission of high priority data.
[0062]
[0062] Programming of a given network can be accomplished by operating a WiFi control on the device that causes a WiFi network to be broadcast by the device, which can be accessed by a user's WiFi-enabled mobile device or computer, which shows the user the WiFi networks visible to the device in an interface on the mobile device or computer, one or more of the visible networks can be configured for access, and the access information is stored within the device for later use.
[0063]
[0063] The connection established as described above can then be used to upload status / usage data from the device to a central (cloud) service, and to download configuration information from the service to the device.
[0064]
[0064] The various embodiments described herein are presented only to aid in the understanding and teaching of the claimed features. The embodiments are provided only as a representative sample of embodiments and are not intended to be exhaustive and / or exclusive. It is to be understood that the advantages, embodiments, examples, functions, features, structures, and / or other aspects described herein should not be considered limitations on the scope of the disclosure defined by the claims or limitations on the equivalents of the claims, and that other embodiments may be utilized and modifications may be made without departing from the scope and / or spirit of the claims.
[0065]
[0065] Various embodiments within the scope of the claims may suitably comprise, consist of, or consist essentially of any suitable combination of the disclosed elements, components, features, parts, steps, means, etc., other than as specifically described herein. In addition, the present disclosure may include other concepts not claimed herein but which may be claimed in the future, either in combination with the features claimed herein or separately.
[0066]
[0066] Although the present specification is described with reference to an electronic nicotine delivery (END) device, it will be appreciated that the teachings herein may also be more generally applicable to aerosol delivery devices that do not necessarily contain or use nicotine. In such more general aerosol delivery devices, the aerosol delivery device (which may include an electronic cigarette (e-cigarette) and / or an END device in some embodiments) may contain an aerosol precursor, such as a reservoir of feedstock liquid, typically but not necessarily containing a formulation, or a solid material, such as a tobacco-based product, from which an aerosol is generated for inhalation by a user, for example through thermal vaporization. Thus, the aerosol delivery device typically includes a vaporizer, such as a heating element, configured to vaporize a portion of the precursor to generate an aerosol in an aerosol-generating region of an air channel through the aerosol delivery device. When a user inhales on the device and power is supplied to the vaporizer, air is drawn into the device through one or more inlet holes and along the air channel to the aerosol-generating region, where the vaporized precursor and the air mix to form a condensed aerosol. Air drawn through the aerosol-generating region continues along the air channel, carrying a portion of the aerosol with it, to the mouthpiece opening through which it exits for inhalation by the user.
[0067]
[0067] Similarly, when this specification refers to an END module, it will be appreciated that in some broader embodiments that do not necessarily use nicotine, the END module may be an aerosol delivery device module. In other words, in some narrower embodiments, the aerosol delivery device module may include an END module. [Item of invention] [Item 1] 1. An aerosol delivery device comprising: a wireless local area network (WLAN) or wireless telecommunications connection interface configured to establish a wireless data connection to a wireless local area network access point to provide data connectivity from the aerosol delivery device to a remote management service; a charging connector configured to receive a power input for recharging a power source of the aerosol delivery device; a circuit configured to selectively activate the connection interface in response to an ongoing or anticipated receipt of power via the charging connector; and An aerosol delivery device comprising: [Item 2] an aerosol delivery device module configured to generate an aerosol upon actuation of the aerosol delivery device module; a charging module configured to receive a power input from the charging connector; Further equipped with 2. The aerosol delivery device of item 1, wherein the WLAN connection interface is provided in the aerosol delivery device module or the charging module. [Item 3] 3. The aerosol delivery device of claim 2, wherein the aerosol comprises nicotine. [Item 4] 4. The aerosol delivery device of any one of claims 1 to 3, wherein the WLAN connection interface comprises a Wi-Fi interface. [Item 5] 5. The aerosol delivery device of any one of claims 1 to 4, wherein the wireless remote communication connection interface comprises a wireless telephone communication connection interface. [Item 6] 6. The aerosol delivery device of any one of claims 1 to 5, wherein the connection interface is configured to connect only to a preconfigured network. [Item 7] An aerosol delivery device described in any one of items 1 to 6, wherein the WLAN connection interface is configured to be selectively operated as an access point to provide a user interface for configuring the aerosol delivery device. [Item 8] 8. The aerosol delivery device of item 7, wherein the WLAN connection interface is configured to connect only to a preconfigured WLAN network, and the user interface is configured to accept data defining the WLAN network and to save the accepted data defining the WLAN network as a preconfigured WLAN network. [Item 9] The aerosol delivery device of item 8, wherein the wireless telecommunications connection interface is configured to connect only to a preconfigured wireless telecommunications network, and the user interface is configured to accept data defining a WLAN network and to store the accepted data defining the wireless telecommunications network as a preconfigured wireless telecommunications network. [Item 10] 10. The aerosol delivery device of any one of claims 1 to 9, wherein the charging connector comprises a wired connector. [Item 11] 11. The aerosol delivery device of any one of claims 1 to 10, wherein the charging connector is equipped with a wireless charging receiver. [Item 12] The aerosol delivery device of any one of items 1 to 11, wherein the circuit configured to selectively activate the connection interface in response to ongoing or anticipated receipt of power via the charging connector is configured to activate the WLAN connection interface in response to detecting continuous receipt of power via the charging connector for a period of time longer than a threshold duration. [Item 13] 13. The aerosol delivery device of any one of claims 1 to 12, wherein the circuitry configured to selectively activate the connection interface in response to ongoing or anticipated receipt of power via the charging connector is further configured to disable the connection interface in response to detecting a cessation of receipt of power via the charging connector. [Item 14] the circuitry configured to selectively activate the connection interface in response to ongoing or anticipated receipt of power through the charging connector, in response to detecting an absence of receipt of power via the charging connector for a period of time greater than a threshold duration; and / or in response to detecting a predetermined number of interruptions in receiving power via the charging connector, each interruption having a duration less than a predetermined threshold duration; Item 14. The aerosol delivery device of item 13, further configured to disable the connection interface. [Item 15] 15. The aerosol delivery device of any one of claims 1 to 14, wherein the remote management service is an Internet hosted management service. [Item 16] a memory for storing past or predicted usage patterns of the aerosol delivery device; A clock showing the current time; circuitry configured to compare the stored usage pattern to the current time to determine when a period of anticipated receipt of power via the charging connector occurs; 16. The aerosol delivery device of any one of claims 1 to 15, further comprising: [Item 17] comparing the stored usage pattern with the current time to determine whether a predicted power consumption caused by operation of the connection interface in combination with a predicted power consumption of an aerosol delivery device usage of the aerosol delivery device specified in the stored usage pattern will cause depletion of the power source before a next predicted receipt of power; in response to determining that the depletion has not occurred, causing operation of the connection interface. Item 17. The aerosol delivery device of item 16, further comprising a circuit configured to: [Item 18] 18. The aerosol delivery device of item 17, wherein the actuation of the connection interface is triggered in response to a determination that a threshold percentage of power remains in the power source above a level indicative of depletion. [Item 19] 19. The aerosol delivery device of any one of items 1 to 18, further comprising a circuit configured to selectively activate the connection interface in response to detection of information queued for transmission having a high priority. [Item 20] 20. The aerosol delivery device of item 19, further configured to utilize the circuitry configured to selectively activate the connection interface in response to ongoing or anticipated receipt of power via the charging connector for the transmission of information queued for delivery having a low priority and / or according to a predetermined activation schedule. [Item 21] 21. The aerosol delivery device of any one of items 1 to 20, wherein each aerosol delivery device comprises an electronic nicotine delivery (END) device. [Item 22] 22. The aerosol delivery device of any one of claims 1 to 21, further dependent on item 2, wherein the aerosol delivery device module comprises an END module. [Item 23] 1. A method of operating an aerosol delivery device, comprising: The aerosol delivery device includes a wireless local area network (WLAN) or wireless telecommunications connection interface configured to establish a wireless data connection to a WLAN or wireless telecommunications network to provide data connectivity from the aerosol delivery device to a remote management service, and the method includes: receiving a power input via a charging connector for recharging a power source of the aerosol delivery device; selectively activating the connection interface in response to ongoing receipt of power via the charging connector; A method comprising: [Item 24] 1. A method of operating an aerosol delivery device, comprising: The aerosol delivery device includes a wireless local area network (WLAN) or wireless telecommunications connection interface configured to establish a wireless data connection to a WLAN or wireless telecommunications network to provide data connectivity from the aerosol delivery device to a remote management service, and the method includes: determining a predicted time point for receiving a power input via a charging connector for recharging a power source of the aerosol delivery device; selectively activating the connection interface in response to determining that power consumption caused by activation of the connection interface will be replenished at the predicted time prior to depletion of the power source due to use of the connection interface and use of the aerosol delivery device; A method comprising: [Item 25] 25. The method according to claim 23 or 24, further comprising the step of operating the device according to any one of items 1 to 22. [Item 26] 1. A method of administering an aerosol delivery device, comprising: Detecting or predicting the application of a charging power supply to the aerosol delivery device to activate a wireless local area network (WLAN) connection interface that is dependent on the presence of a wireless telecommunication or power supply of the aerosol delivery device; In response to detecting or predicting application of charging power, operating the connection interface to detect whether the aerosol delivery device is within coverage of a WLAN or wireless telecommunications network, the network providing data connectivity to a remote management service; enabling the aerosol delivery device to connect to the network when the connection interface is activated to enable the aerosol delivery device to connect to a remote management service and receive data from and / or provide data to the remote management service; A method comprising: [Item 27] 27. The method of claim 26, wherein the step of activating the connection interface to detect includes a step of detecting whether the aerosol delivery device is within the service range of a WLAN or wireless telecommunications network for which the aerosol delivery device was previously configured. [Item 28] operating a connection interface of the WLAN of the aerosol delivery device in an access point mode; connecting a WLAN enabled computing device to the aerosol delivery device; using the WLAN-enabled computing device to access a user interface of the aerosol delivery device accessible in the access point mode; using the user interface to configure details of a WLAN or telecommunications network and saving the details of the network as a network for which the aerosol delivery device was previously configured; 28. The method of claim 27, further comprising: [Item 29] 30. The method of claim 26, 27 or 28, wherein the detecting step includes detecting a connection of a charging power supply to the aerosol delivery device. [Item 30] 30. The method according to any one of claims 26 to 29, wherein the step of predicting includes a step of comparing a current time to a schedule indicating a predicted charging time. [Item 31] 31. The method of claim 30, wherein the step of predicting further comprises the step of determining that the current time falls within a predicted charging time. [Item 32] The method of any one of items 30 and 31, wherein the predicting step further includes a step of determining that power consumption caused by operation of the connection interface and predicted aerosol delivery device usage prior to the predicted charging time will be less than the currently remaining power supply level of the aerosol delivery device. [Item 33] detecting a priority of data waiting to be transmitted over said connection interface; For low priority data, basing operation of the connection interface on detection or prediction of application of a charging power supply to the aerosol delivery device; activating said connection interface for high priority data; The method according to any one of items 26 to 32, further comprising: [Item 34] 34. The method of any one of items 24 to 33, wherein each aerosol delivery device comprises an electronic nicotine delivery (END) device.
Claims
1. 1. An aerosol delivery device comprising: a connection interface configured to establish a data connection to a network access point to provide data connectivity from the aerosol delivery device to a remote service or computing device; a charging connector configured to receive a power input for recharging a power source of the aerosol delivery device; a circuit configured to disable the connection interface in response to detecting a cessation of receipt of power via the charging connector; and An aerosol delivery device comprising:
2. The aerosol delivery device of claim 1 , wherein the circuitry is further configured to disable the connection interface in response to detecting an cessation of receipt of power through the charging connector for a period of time longer than a threshold duration.
3. The circuit, The aerosol delivery device of claim 1 or 2, further configured to disable the connection interface in response to detecting an interruption in receiving power via the charging connector a predetermined number of times.
4. The aerosol delivery device of claim 3 , wherein each interruption has a duration less than a predetermined threshold duration.
5. the circuitry is configured to disable the connection interface in response to detecting a cessation of receipt of power via the charging connector; enabling the connection interface to complete a current data exchange from the aerosol delivery device to the remote service or computing device; deactivating said connection interface once said current data exchange is completed; The aerosol delivery device of any one of claims 1 to 4, comprising a circuit configured to:
6. an aerosol delivery device module configured to generate an aerosol upon actuation of the aerosol delivery device module; a charging module configured to receive a power input from the charging connector; Further equipped with The aerosol delivery device according to any one of claims 1 to 5, wherein the connection interface is provided on the aerosol delivery device module or the charging module.
7. The aerosol delivery device of claim 6 , wherein the aerosol comprises nicotine.
8. The aerosol delivery device of any one of claims 1 to 7, wherein the connection interface comprises a wireless local area network (WLAN) or wireless telecommunications interface and the data connection is a wireless data connection.
9. The aerosol delivery device of any one of claims 1 to 8, wherein the connection interface is configured to connect only to a preconfigured network.
10. The aerosol delivery device of any one of claims 1 to 9, wherein the charging connector comprises a wired connector.
11. The aerosol delivery device of any one of claims 1 to 10, wherein the charging connector comprises a wireless charging receiver.
12. The aerosol delivery device of any one of claims 1 to 11, wherein the circuitry is further configured to selectively activate the connection interface in response to ongoing or anticipated receipt of power via the charging connector.
13. The aerosol delivery device of any one of claims 1 to 12, wherein the data is encoded in a format that anonymizes or obscures the information carried by the data.
14. The aerosol delivery device of any one of claims 1 to 13, wherein the data is encrypted.
15. The aerosol delivery device of any one of claims 1 to 14, wherein the computing device comprises a smartphone device.
16. The aerosol delivery device of any one of claims 1 to 15, wherein the aerosol delivery device comprises an electronic nicotine delivery (END) device.
17. 1. A method of operating an aerosol delivery device, comprising: The aerosol delivery device includes a connection interface configured to establish a data connection to a network to provide data connectivity from the aerosol delivery device to a remote service or computing device, and the method includes: receiving a power input via a charging connector for recharging a power source of the aerosol delivery device; in response to detecting a cessation of receipt of power via the charging connector, disabling the connection interface; A method comprising:
18. Disabling the connection interface in response to detecting a cessation of receipt of power via the charging connector; enabling the connection interface to complete a current data exchange from the aerosol delivery device to the remote service or computing device; deactivating said connection interface once said current data exchange is completed; 20. The method of claim 17, further comprising:
19. The method further comprises: before the connection interface is disabled, Providing data from the aerosol delivery device to the remote service or computing device using the connection interface.
19. The method of claim 17 or 18, further comprising:
20. 20. The method of claim 19, wherein the data is encoded in a format that anonymizes or obscures information carried by the data.
21. The method of any one of claims 17 to 20, wherein the aerosol delivery device comprises an electronic nicotine delivery (END) device.
Citation Information
Patent Citations
Trigger-based radio broadcasting for aerosol delivery devices
JP2018527904A
electronic vapor feeder
JP2018533923A
Electronic vapor provision system
US20180271155A1