Aerosol Generator

Abstract

An aerosol generating device (2) capable of generating an aerosol for inhalation by a user is disclosed. The device (2) includes a data storage device (114) configured to store data related to user interactions and an interface (118) configured to establish a communicative pairing with a user computing device (4, 6, 8). The processor (108) is configured to delete all data related to user interactions with the aerosol generating device that was previously stored in the data storage device if the user computing device associated with a new user is successfully paired with the interface. In another configuration, a flag may be set in the data storage device (114) if the user computing device is successfully paired with the interface (118), thereby allowing data to be stored in the data storage device if the flag is set and prohibiting data from being stored in the data storage device otherwise.

Description

[Technical field]

[0001] The present invention relates to an aerosol generating device, and more particularly to an aerosol generating device capable of pairing with a user computing device such as a smartphone. [Background technology]

[0002] Aerosol generating devices such as electronic cigarettes are becoming increasingly popular. Various types of aerosol generating mechanisms are available depending on consumer preference. Some devices involve heating, without combustion, an aerosol generating substrate to generate an aerosol for inhalation. Other devices may store a vaporizable liquid in a reservoir, typically using an electric heater to vaporize the liquid in an airflow channel. Summary of the Invention [Problem to be solved by the invention]

[0003] An attractive feature of some of these devices is their ability to "connect" with other user computing devices, such as smartphones and personal computers. This may allow the user to have a more immersive experience and to synchronize interactions with the aerosol generating device with other devices and with events in the user's life. Thus, the aerosol generating device can record data regarding user interactions and share these data with other connected devices. It is an object of the present invention to increase the security with which these data are handled and accessed. [Means for solving the problem]

[0004] According to one aspect of the present invention, there is provided an aerosol generating device configured to generate an aerosol for inhalation by a user, the device including a data storage device configured to store data related to user interaction with the aerosol generating device, an interface configured to establish a communicative pairing with a user computing device, and a controller configured to perform an action related to the data storage device based on a flag set in the data storage device, the flag indicating a status of the pairing between the interface and the user computing device.

[0005] In this way, the status of the data storage device may change depending on the connection between the aerosol generating device and the user computing device, which may improve data security within the aerosol generating device.

[0006] Preferably, performing an action related to the data storage device based on a flag being set in the data storage device comprises changing a status of the data storage device based on a status of a flag being set in the data storage device. In other words, the controller may be configured to change the status of the data storage device based on a status of a flag being set in the data storage device, the flag indicating a status of the pairing between the interface and the user computing device.

[0007] In one configuration, the controller may be configured to delete all data related to user interactions with the aerosol generating device that was previously stored in the data storage device if the flag indicates that the user computing device associated with the new user has successfully paired with the interface. In this manner, if the user computing device associated with the new user has successfully paired, stored data that may be related to the previous user may be deleted. This may prevent potentially sensitive data created by one user from being communicated to a device associated with another user. The new user is preferably identifiable by being different from the previous user of the device. Alternatively, if there is no previous user, the new user may be the first identifiable user of the device. The data that is deleted is preferably data stored in read-only memory (e.g., data stored in a solid-state storage device).

[0008] The aerosol generating device is preferably an electronic cigarette. The user computing device is preferably a smartphone. Various alternative interactive user computing devices may also be used, for example a laptop computer or a wearable computing device (such as a watch).

[0009] The controller is preferably configured to store data relating to interactions with the aerosol generating device after data deletion. These stored interactions are therefore considered as interactions by the new user. The aerosol generating device may store these data in memory for transfer to a user computing device associated with the user the next time a suitable device is paired with the aerosol generating device.

[0010] The controller may be configured to send the stored data to the user computing device associated with the new user using the interface if the user computing device is paired, thereby ensuring that data is only sent to the new user's device if it can be reasonably concluded that the usage data was collected by that user. Sending the stored data may include accessing the stored data from the user computing device.

[0011] Preferably, the controller is configured to store an indication of the new user if the user computing device associated with the new user has successfully paired with the interface. For example, the indication may correspond to a unique user ID. Notably, the user ID may be independent of any particular user computing device. This may allow the same user to interface with the aerosol generating device using different devices (e.g., a smartphone and a personal computer, or two different smartphones) without deleting stored data associated with each interface with the aerosol generating device.

[0012] The indication is preferably received from the user computing device via an interface. For example, the indication may be an electronic token associated with the new user's account. The indication may be stored in the data store in the form of a flag.

[0013] The controller may be configured to compare the indication received from the user computing device with the indication stored in the data storage device to determine whether the communicative pairing is associated with a new user. This comparison may also reveal that the indication received from the user computing device is associated with the current user of the aerosol generating device (i.e., the user's identity has not changed and the indication received from the user computing device matches the stored indication). In such a situation, the historical usage data is not deleted because it is securely transferred to the user computing device associated with the current user of the device.

[0014] The interface is preferably configured to establish a communicative pairing with the user computing device using a wireless protocol, preferably Bluetooth®, although other protocols such as Wi-Fi may also be used depending on the circumstances. In an alternative configuration, a wired connection may be established between the aerosol generating device and the user computing device.

[0015] In one configuration, the controller may be configured to set a flag in the data storage device when the user computing device is successfully paired with the interface, allowing data to be stored in the data storage device if the flag is set, and prohibiting data from being stored in the data storage device otherwise, thereby allowing protection of sensitive data since the user computing device is prohibited from storing data unless it is successfully paired, i.e., sensitive data generated by a user cannot be accessed by another party that has paired their respective device with an aerosol generating device, even if no data is stored in the data storage device, unless at least one communicative pairing has been established.

[0016] The device preferably includes one or more sensors configured to detect user interaction, the one or more sensors being deactivated when storage of data in the data storage device is prohibited. In one alternative, the one or more sensors may be activated, but storage of data related to detected user interaction may be electronically prevented.

[0017] According to another aspect of the present invention, there is provided a method of using an aerosol generating device capable of generating an aerosol for inhalation by a user, the method including the steps of providing a data storage device configured to store data relating to user interaction with the aerosol generating device, establishing a communicative pairing with a user computing device associated with a new user using an interface of the aerosol generating device, and performing an action related to the data storage device based on a status of a flag in the data storage device, the flag indicating a status of the pairing between the interface and the user computing device.

[0018] Preferably, performing an action relating to the data storage device based on a status of a flag in the data storage device comprises changing a status of the data storage device based on a status of a flag set in the data storage device. In other words, the method may comprise changing a status of the data storage device based on a status of a flag set in the data storage device, the flag indicating a status of pairing between the interface and the user computing device.

[0019] According to yet another aspect of the present invention, a non-transitory computer-readable memory product is provided that includes executable instructions that, when executed by a computer, cause a computer to perform steps including: establishing a communicative pairing with a user computing device associated with a new user using an interface of the aerosol generating device; and performing an action associated with a data storage device configured to store data related to user interactions with the aerosol generating device based on the status of a flag in the data storage device, the flag indicating the status of the pairing between the interface and the user computing device.

[0020] Preferably, the step of performing an action related to the data storage device comprises changing a status of the data storage device based on a status of a flag set in the data storage device. In other words, these steps may include changing a status of a data storage device configured to store data related to user interaction with the aerosol generating device based on a status of a flag set in the data storage device, the flag indicating a status of pairing between the interface and the user computing device.

[0021] According to another aspect, an aerosol generating device configured to generate an aerosol for inhalation by a user is provided, the device including a data storage device configured to store data related to user interaction with the aerosol generating device, an interface configured to establish a communicative pairing with a user computing device, and a controller configured to: allow saving of data in the data storage device if a status of a flag set in the data storage device indicates that the user computing device has successfully paired with the interface; prohibit saving of data in the data storage device if a status of a flag set in the data storage device indicates that the user computing device has not paired with the interface; and allow generation of aerosol using the aerosol generating device regardless of the status of the flag.

[0022] The aerosol generating device may include one or more sensors configured to detect user interaction.

[0023] In some instances, the one or more sensors are deactivated when storing data in the data storage device is prohibited.

[0024] In another example, when storing data in the data storage device is prohibited, the one or more sensors are activated but data related to the detected user interaction is prevented from being stored in the data storage device.

[0025] The controller may be configured to send the stored data to the user computing device using the interface if the user computing device is paired.

[0026] According to yet another aspect, a method of using an aerosol generating device capable of generating an aerosol for inhalation by a user is provided, the method including the steps of: providing a data storage device configured to store data relating to user interaction with the aerosol generating device; using an interface of the aerosol generating device to establish a communicative pairing with a user computing device associated with a new user; allowing data to be stored in the data storage device if a status of a flag set in the data storage device indicates that the user computing device has successfully paired with the interface; prohibiting data from being stored in the data storage device if a status of a flag set in the data storage device indicates that the user computing device has not paired with the interface; and allowing aerosol generation using the aerosol generating device regardless of the status of the flag.

[0027] According to yet another aspect, a non-transitory computer-readable memory product is provided that includes executable instructions that, when executed by a computer, cause a computer to perform steps including: establishing a communicative pairing with a user computing device associated with a new user using an interface of the aerosol generating device; allowing data associated with user interaction with the aerosol generating device to be stored in the data storage device if a status of a flag set in the data storage device indicates that the user computing device has successfully paired with the interface; prohibiting data associated with user interaction with the aerosol generating device from being stored in the data storage device if a status of a flag set in the data storage device indicates that the user computing device has not paired with the interface; and allowing aerosol generation using the aerosol generating device regardless of the status of the flag set in the data storage device.

[0028] Embodiments of the invention will now be described, by way of example only, with reference to the drawings in which: [Brief description of the drawings]

[0029] [Figure 1] FIG. 1 is a schematic diagram of an aerosol generation device in communication with one or more user computing devices in one embodiment of the present invention. [Diagram 2] FIG. 2 is a schematic diagram of a control system in an aerosol generating device in one embodiment of the present invention. [Diagram 3] FIG. 2 is a flow diagram showing the sequence of steps performed in an aerosol generating device in one embodiment of the present invention. [Figure 4] FIG. 2 is a flow diagram showing the sequence of steps performed in an aerosol generating device in accordance with another embodiment of the present invention. [Diagram 5]1 is an example of a flag that can be set in the data storage device of an aerosol generating device in accordance with one embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0030] 1 is a schematic diagram of an aerosol generating device 2, i.e., an electronic cigarette. The aerosol generating device 2 is configured to wirelessly communicate with one or more user computing devices 4, 6, 8. In this schematic example, the user computing devices include a first smartphone 4, a second smartphone 6, and a laptop computer 8. Any number of different types of user computing devices may be used, including wearable devices such as smart watches or headsets.

[0031] In this embodiment, the aerosol generating device 2 has a body 104 and a mouthpiece portion 102. The body 104 includes a battery 106 for powering the device and a processor 108 or controller for controlling operation. The body 104 may further include a user operable button 110 for functions such as turning the device 2 on and off and engaging a heater in an atomizer (not shown) to vaporize vaporizable liquid from a liquid reservoir. The present invention is not limited to use with aerosol generating devices that vaporize vaporizable liquid. Similarly, the present invention may be used with aerosol generating devices capable of generating aerosols based on other operating principles (e.g., heating a tobacco substrate without burning it).

[0032] In the context of this disclosure, aerosol and vapor may be considered interchangeable terms; that is, aerosol is vapor and vapor is aerosol. Aerosol for smoking may refer to an aerosol with a particle size of 0.5 to 7 microns. The particle size may be less than 10 or 7 microns.

[0033] Further electronic components within the aerosol generation device 2 are apparent from the schematic diagram of Figure 2. The processor 108 receives power from the battery 106 and is operatively connected to the aerosol generator 112 (e.g., an atomizer or a heater). The processor 108 is further connected to a data storage device 114 and one or more sensors 116. The data storage device 114 is typically a solid-state storage device. Finally, the processor 108 is connected to a communication interface 118, which may enable communication between the aerosol generation device 2 and one or more user computing devices 4, 6, 8. In some embodiments, the processor 108 may be a microcontroller.

[0034] The sensor 116 is configured to detect data associated with the use of the aerosol generating device 2. For example, the sensor 116 can detect puff record data, which may include information about a user inhalation event, such as the duration of the inhalation, the maximum flow rate recorded, the rate of change of the flow rate, the evolution of the flow rate, the temperature in the aerosol generator, the amount of nicotine or liquid consumed, the amount of energy consumed, the time of the puff, and the length of the depression of the activation button 110. The sensor 116 may thus include, for example, a temperature sensor, a flow rate sensor, an electrical resistance detector, etc. The sensor 116 may also detect event data, which may also be related to some kind of user interaction with the device 2. Examples of event data include the insertion of a capsule removal or the occurrence of an error. The sensor 116 may thus include a contact sensor, an electrical sensor, a Hall effect sensor, or a photovoltaic sensor to detect the insertion or removal of a capsule. The sensor 116 may also be implemented in software to detect events such as errors. Each instance of puff record data or event record data recorded by the sensor 116 may be associated with a timestamp.

[0035] 3 is a flow diagram showing a sequence of steps that can be performed in an exemplary embodiment of the present invention. In step S100, the device 2 is used for its normal purpose, i.e., generating an aerosol for a user to inhale. The user can inhale through the mouthpiece 102 while pressing the user-operable button 110. The aerosol generator 112 generates the aerosol using power provided by the battery 106. In step S102, the processor 108 checks the data storage 114 to see if the device 2 has ever been paired with a user computing device 4, 6, 8. This is possible because, after being paired with a user computing device 4, 6, 8, the MAC address of the device is stored in the data storage 114 in the form of a whitelist or flag. Thus, in step S102, the processor 108 may check whether the MAC address is missing from the whitelist or flag in the data storage 114. Thus, if the stored MAC address is missing from the whitelist or flag, it means that the user computing device 4, 6, 8 has never been successfully paired with the aerosol generating device 2. In such circumstances, in step S104, the processor 108 may prohibit any usage data from being stored in the data storage device 114.

[0036] Inhibiting the storage of usage data may be done in a number of possible ways. In one example, the processor 108 may deactivate the sensor 116 so that no data is recorded for any usage events. In another example, the sensor 116 may remain activated, but data records of detected puffs and events are not committed to read-only memory in the data storage device 114.

[0037] If, in step S105, it is determined that the MAC address exists in the data storage device 114, thereby indicating that the device has been successfully paired with a user computing device in the past, a flag may be set in the data storage device 114 to allow usage data to be stored in the data storage device 114. The usage data is then stored in the data storage device 114 in step S106. The usage data may include puff data records and event data records detected by the sensor 116.

[0038] The data storage device 114 is designed to store up to 6000 puff records and 4000 event records. These data records are kept in the data storage device 114 until it is possible to transfer the data records to the user device through a communicative pairing. Once a data record has been successfully sent to the user device, it is deleted from the data storage device 114. This frees up storage space for new data records.

[0039] In step S108 of this exemplary flow diagram, the aerosol generating device 2 is paired with one of the user computing devices 4, 6, 8. This is accomplished by a communication interface 118 in the aerosol generating device. In one embodiment, the user computing device, such as the first smartphone 4, is paired wirelessly using a protocol such as Bluetooth. Of course, several alternative wireless protocols may be used. It would also be possible to establish a communicative pairing by directly connecting the first smartphone 4 and the aerosol generating device 2 via a wired connection, but this is generally less convenient for the user.

[0040] The processor 108 is configured to check, in step S110, whether there has been a change in the identity of the paired user computing device. This is accomplished by checking the MAC address of the paired user computing device and comparing it with the MAC address stored in the data store 114, which represents the user computing device most recently paired with the aerosol generating device 2. If such a change is identified, then in step S112, the processor 108 deletes all usage data, including puff data records and event data records, in the data store 114. This can prevent potentially sensitive data from being communicated to another user computing device that may be associated with the new user. Then in step S112, the MAC address of the newly paired user computing device is stored in the data store 114. In some configurations, only one MAC address can be stored in the whitelist of the data store 114 at any one time.

[0041] If the MAC address of the paired user computing device matches the MAC address stored in the data storage device 114, it may be concluded in step S110 that there has been no change in the paired user computing device. In other words, it may be concluded that the currently paired user computing device is the same as the most recently already paired user computing device. In such a situation, in step S114, data transfer with the user computing device is initiated. The processor 108 is configured to transfer the data records one by one from the data storage device 114 to the paired user computing device via the communication interface 118 in step S114. This may enable the user to review the usage records in an application on the user computing device and to display graphics and statistics regarding the user's usage. The data records are deleted from the data storage device 114 after being transferred to the paired user computing device.

[0042] The flow diagram then returns to step S100. Of course, continued use of the device 2 can still generate aerosol, and normal use of the device is not precluded by performance of the steps of the flow diagram of Figure 3, which diagram merely illustrates one embodiment of use.

[0043] The user can also delete all stored data from the data storage device 114, including all MAC addresses on the whitelist, by selecting a "Factory Reset" button. The factory reset button may be provided on the aerosol generating device 2. Alternatively or additionally, the factory reset functionality may be provided in a software application on the paired user computing device.

[0044] 4 is another exemplary flow diagram illustrating a sequence of steps that can be performed in another embodiment of the present invention. In step S200, the device 2 is used for its normal purpose, i.e., generating an aerosol for inhalation by a user. Usage data is collected by the sensor 116 and in step S202 the usage data, including puff data records and event data records, is stored in the data storage device 114.

[0045] In step S204, the aerosol generating device 2 is paired with the user computing device 4, 6, 8 as described above in relation to step S108. If pairing is successful, the user computing device 4, 6, 8 sends a user ID, or some other token or key representing the user, to the aerosol generating device 2. The user ID is received in the aerosol generating device 2 in step S206 and stored in the data storage device 114. The user ID is typically generated when a user account is set up for the aerosol generating device 2 using an application on the user computing device.

[0046] To pair a user computing device with an aerosol generating device, the user needs a user account with a unique user ID in an application associated with the aerosol generating device, which is downloaded and installed on the user's computing device. In one embodiment, each pairing requires the user to enter a user ID in the application running on the computing device and also accept terms and conditions to enable storage and transfer of usage data related to the aerosol generating device. In another embodiment, the user account is created and stored on a remote server. The user account may include various user information in addition to the user ID, such as the user's name, the user's age, the user's birth date, the user's email, and the user's password. The account creation process on the remote server includes receiving the user's identification information to authenticate the user, and also the user's confirmation that the terms and conditions have been accepted to enable usage data related to the aerosol generating device to be created and sent to the computing device associated with the same user account. A user registration request is sent from the personal computing device to the remote server. The remote server creates the account and stores the user identification information in a user database. Each time a user wants to pair a computing device with an aerosol generating device, the user is required to log in to an application running on the computing device, and a user identification associated with the log-on data is transferred from a remote server to the computing device. The computing device then transfers the received user identification to the aerosol generating device for comparison with a user ID stored locally on the aerosol generating device. Alternatively, the user ID is stored on the computing device by the application, and after the user logs on to the application, the computing device retrieves the user ID associated with the log-on data from its local storage and transmits the user ID to the aerosol generating device.

[0047] In step S208, processor 108 determines whether the user ID is the first one received by device 2. This is achievable because user IDs for successfully paired devices are automatically stored in data storage 114. If no user ID is stored in data storage 114, then in step S208 it may be determined that no user ID has ever been received, and in step S210 all usage data stored in data storage 114 is deleted. This ensures that data recorded before the user ID was received is protected.

[0048] In step S212, the processor 108 determines whether the received user ID has changed. This is accomplished by comparing the received user ID with the most recently stored user ID in the data store 114. If the processor 108 detects a difference, it may determine that a user change has occurred. In such a situation, in step S210, all usage data stored in the data store 114 is deleted. This ensures that usage data created by one user cannot be transferred to or accessed from a user computing device associated with another user.

[0049] It is also possible in step S212 that the processor 108 may determine that the received user ID matches the user ID most recently stored in the data storage device 114. In such a situation, it may be concluded that there is no change in the user ID, and in step S214, the usage data stored in the data storage device 114 is uploaded to the paired user computing device 4, 6, 8. The data records are uploaded one by one and immediately deleted from the data storage device 114 after being uploaded. The flowchart then returns to step S200, and the user may again use the device to generate aerosol.

[0050] It is worth noting that the user ID received in step S206 may not depend on the user computing device. For example, the same user may have multiple user computing devices (e.g., a work smartphone, a personal smartphone, and a personal computer). The user may not want to delete the usage data stored in the data storage device 114 when pairing the aerosol generating device 2 with any one of these user computing devices. This may allow the user to start using a new phone without deleting any usage data. In the embodiment of FIG. 4, this is achieved by deleting the usage data only if the user ID changes. This is achieved even if the aerosol generating device 2 is paired with another user computing device 4, 6, 8.

[0051] It is worth noting that steps S208 and S212 can be combined into one step. In step S212, the processor 108 determines whether there has been a change in the received user ID. A change in the received user ID can only be detected once the user ID is received. This would mean that there is a difference between the received user ID and the empty slots for the user ID in the data storage device 114 that can be detected. Only one step is required after this procedure.

[0052] The usage data is protected if the user misplaces the aerosol generating device 2. In such a situation, the usage data is detected when another person attempts to pair a user computing device with the aerosol generating device. In the embodiment of FIG. 3, this is achieved in step S110 by determining that the MAC address of the new user computing device does not match the MAC address of the most recently paired user computing device. In the embodiment of FIG. 4, the same result is achieved in step 212 by determining that the user ID has changed when a new person pairs the user computing device. Both situations lead to the previous usage data being deleted in favor of the original user.

[0053] Of course, the steps of the flowcharts of Figures 3 and 4 may be combined as desired. For example, aspects of steps S102 and S104 could be inserted into Figure 4 to prohibit storage of usage data in the aerosol generating device 2 until an initial user ID is received from a paired user computing device.

[0054] 5 is an example of a flag 120 that can be stored in the data storage device 114. The properties of the flag 120 can be dynamically adjusted by the processor 108. In this example, the flag 120 includes a header 122 of one bit (i.e., set to 0 or 1). The header 122 can be set to 0 to indicate that the aerosol generating device 2 has never been paired with any user computing device. The processor 108 can change the header 122 to 1 when the user computing device is paired with the communication interface 118 for the first time. In this way, the processor 108 can check the header 122 of the flag 120 in step S102 to determine whether the device 2 has been paired with a user computing device. The flag 120 includes a first data portion 124, which stores the MAC address of the most recently paired user computing device. The first data portion 124 is typically 6 bytes and includes 6 groups of 2-digit hexadecimal numbers, but this can be modified as necessary depending on the expected properties of the user computing device. In one example, the MAC address is a standard EUI-48 address that includes six groups of two hexadecimal digits, e.g., CE:51:7E:EA:17:E0. In this way, the processor 108 can check the first data portion 124 of the flag 120 in step S110 to determine whether there has been a change in the identification information of the paired user computing device. The flag 120 further includes a second data portion 126, which stores the user ID received in step S206. Typically, the user ID is 24 or 32 bits, but this may be adjusted depending on the preferred properties of the user ID. In this way, in step S208, the processor 108 can determine whether the received user ID is the user ID originally received. Furthermore, in step S212, by examining the second data portion 126, it can be made clear to the processor 108 whether the user ID has changed.

[0055] Thus, the flag header 122 serves as the status of the flag 120 that is set in the data store 114. The status of the flag can be one of two statuses: a status indicating that the user computing device 4 has successfully paired with the interface 118 (in which case the header 122 is set to 1), and a status indicating that the user computing device 4 has not paired with the interface 118 (in which case the header 122 is set to 0).

[0056] The status of flag 120 is used to determine whether data storage device 114 will or will not store data. Thus, the status of flag 120 may be considered as at least partially controlling at least one function of data storage device 114. Specifically, if the flag status indicates that user computing device 4 has successfully paired with interface 118, data is allowed to be stored in data storage device 114. Conversely, if the flag status indicates that user computing device 4 has not paired with interface 118, data is prohibited from being stored in data storage device 114.

[0057] However, the status of the flag does not determine (or control) whether data is initially collected from the sensor 116. The status of the flag only determines whether this data is saved to the data store 114.

[0058] For example, in some developments, if the flag status indicates that the user computing device 4 is not paired with the interface 118, usage data may still be collected by the sensor 116, but this data is not saved to the data storage device 114. In this case, the sensor 116 remains activated, or is activated if it is not already activated, but the detected data (such as puff data and event data) is not committed to read-only memory in the data storage device 114.

[0059] Alternatively, in other developments, if the flag status indicates that the user computing device 4 is not paired with the interface 118, then no usage data may be collected by the sensor 116. In this case, the sensor 116 is deactivated, or remains deactivated if already deactivated, and no data is recorded for any usage events.

[0060] The status of the flag 120 also does not determine (or control) whether the aerosol generating device 2 is usable. In fact, the aerosol generating device 2 may be operated by a user regardless of the status of the flag 120. In other words, a user is allowed to use the aerosol generating device 2 to generate aerosol regardless of the status of the flag 120. For example, a user can use the aerosol generating device to generate vapor even if the flag status indicates that the user computing device 4 is not paired with the interface 118. Furthermore, despite no computing device 4 being paired with the interface 118, usage data can still be collected by the sensor 116 as described above, but this data is not stored in the data storage device 114.

[0061] Therefore, the function of operating the aerosol generating device 2 and the function of how to operate the data storage device 114 are two completely separate functions of the aerosol generating device 2, and they are unrelated to each other. Therefore, whether the aerosol generating device 2 can be used is not in any way disabled or affected by whether the data storage device 114 can store data, i.e., whether the data storage function of the data storage device 114 is enabled or disabled. This is important because a user must be able to use the aerosol generating device 2 even if he or she does not want his or her usage data to be stored. Usage data is private data associated with a particular user, and this data must not be stored unless the user has authorized the aerosol generating device to store this data. If the aerosol generating device 2 were to store usage data associated with a user without authorization, the data may be leaked to unauthorized persons.

[0062] As mentioned above, upon successful pairing, the user computing device 4 sends a form of a user ID uniquely associated with the user to the aerosol generating device 2, which stores the received user ID in the data storage device 114. The user ID is typically generated when a user account is created for the aerosol generating device 2. In addition to authenticating the user, the account creation process includes receiving the user's acceptance of terms and conditions regarding usage data, including storage and transfer of usage data.

[0063] Thus, the authentication process, including acceptance of the terms and conditions, is only performed once when the user first pairs the aerosol generating device 2 with the user computing device 4. These steps are not performed every time the user uses the aerosol generating device 2.

[0064] Advantageously, the use of the aerosol generating device 2 is not dependent on or linked to the authentication process. That is, the user can continue to use the aerosol generating device 2 even if the authentication process has not been performed, since the authentication process only concerns data storage. In short, the aerosol generating device 2 described herein only stores data if the user has successfully paired the aerosol generating device 2, but the user can continue to actually use the aerosol generating device 2 (and not store data) regardless of whether the aerosol generating device 2 is paired or not. Use of the device is not dependent on the user agreeing to the terms and conditions.

Claims

1. 1. An aerosol generating device configured to generate an aerosol for inhalation by a user, comprising: a data storage device configured to store data relating to user interactions with the aerosol generating device; an interface configured to establish a communicative pairing with a user computing device; a controller configured to change a status of the data storage device based on a status of a flag set in the data storage device, the flag indicating a status of pairing between the interface and a user computing device, and the status of the data storage device representing a function of the data storage device to allow or prohibit the storage of new user data; An aerosol generating device comprising:

2. The aerosol generating device of claim 1, wherein the controller is configured to delete all data relating to user interactions with the aerosol generating device already stored in the data storage device if the flag indicates that a user computing device associated with a new user has successfully paired with the interface.

3. The aerosol generating device of claim 2 , wherein the controller is configured to store data relating to interactions with the aerosol generating device after the data deletion.

4. The aerosol generating device of claim 3, wherein the controller is configured to send stored data to the user computing device associated with the new user using the interface if the user computing device is paired.

5. An aerosol generating device as described in any one of claims 2 to 4, wherein the controller is configured to store an indication of the new user if the user computing device associated with the new user has successfully paired with the interface.

6. The aerosol generating device of claim 5 , wherein the indication is received from the user computing device via the interface.

7. The aerosol generating device of claim 6, wherein the controller is configured to compare the indication received from the user computing device with an indication stored in the data storage device to determine whether the communicative pairing is associated with the new user.

8. An aerosol generating device as described in any one of claims 1 to 7, wherein the interface is configured to establish communicative pairing with a user computing device using a wireless protocol.

9. An aerosol generating device as described in any one of claims 1 to 8, wherein the controller is configured to allow data to be stored in the data storage device if the flag indicates that the user computing device has successfully paired with the interface, and to prohibit storing data in the data storage device if not.

10. 10. The aerosol generating device of claim 9, further comprising one or more sensors configured to detect user interaction, the one or more sensors being deactivated when storing data in the data storage device is prohibited.

11. An aerosol generating device as described in claim 9 or claim 10, comprising one or more sensors configured to detect user interaction, and wherein if storing data in the data storage device is prohibited, storing data related to the detected user interaction in the data storage device is prevented.

12. An aerosol generating device as described in any one of claims 9 to 11, wherein the controller is configured to use the interface to send stored data to the user computing device when the user computing device is paired.

13. 1. A method of using an aerosol generating device capable of generating an aerosol for inhalation by a user, comprising: providing a data storage device configured to store data relating to user interaction with the aerosol generating device; establishing a communicative pairing with a user computing device associated with a new user using an interface of the aerosol generating device; changing a status of the data storage device based on a status of a flag set in the data storage device, the flag indicating a status of pairing between the interface and a user computing device, and the status of the data storage device representing a capability of the data storage device to allow or prohibit the storage of new user data; The method includes:

14. When executed by a computer, establishing a communicative pairing with a user computing device associated with the new user using an interface of the aerosol generating device; changing a status of a data storage device configured to store data related to user interactions with the aerosol generating device based on a status of a flag set in the data storage device, the flag indicating a status of pairing between the interface and a user computing device, and the status of the data storage device representing a function of the data storage device to enable or prohibit the storage of new user data; 23. A non-transitory computer readable memory product comprising executable instructions for causing said computer to perform steps including:

15. 1. An aerosol generating device configured to generate an aerosol for inhalation by a user, comprising: a data storage device configured to store data relating to user interactions with the aerosol generating device; an interface configured to establish a communicative pairing with a user computing device; A controller, if a status of a flag set in the data storage device indicates that a user computing device has successfully paired with the interface, enabling data to be saved in the data storage device; prohibiting data from being stored on the data storage device if a status of a flag set on the data storage device indicates that a user computing device is not paired with the interface; enabling the aerosol generating device to be used to generate aerosol regardless of the status of the flag; and The controller configured to: An apparatus comprising:

16. 16. The aerosol generating device of claim 15, further comprising one or more sensors configured to detect user interaction, the one or more sensors being deactivated when storing data in the data storage device is prohibited.

17. The aerosol generating device of claim 15, further comprising one or more sensors configured to detect user interaction, wherein when storing data in the data storage device is prohibited, the one or more sensors are activated but storing data related to the detected user interaction in the data storage device is prevented.

18. An aerosol generating device as described in any one of claims 15 to 17, wherein the controller is configured to use the interface to send stored data to the user computing device if the user computing device is paired.

19. 1. A method of using an aerosol generating device capable of generating an aerosol for inhalation by a user, comprising: providing a data storage device configured to store data relating to user interaction with the aerosol generating device; establishing a communicative pairing with a user computing device associated with a new user using an interface of the aerosol generating device; if a status of a flag set in the data storage device indicates that a user computing device has successfully paired with the interface, enabling data to be saved in the data storage device; prohibiting data from being stored on the data storage device if a status of a flag set on the data storage device indicates that a user computing device is not paired with the interface; enabling the aerosol generating device to generate aerosol regardless of the status of the flag; The method includes:

20. When executed by a computer, establishing a communicative pairing with a user computing device associated with the new user using an interface of the aerosol generating device; if a status of a flag set in a data storage device indicates that a user computing device has been successfully paired with the interface, enabling data relating to user interaction with the aerosol generating device to be stored in the data storage device; prohibiting storage of data associated with user interaction with the aerosol generating device in the data storage device if a status of a flag set in the data storage device indicates that the user computing device is not paired with the interface; and enabling generation of aerosol using the aerosol generating device regardless of the status of the flag set in the data storage device.

23. A non-transitory computer readable memory product comprising executable instructions for causing said computer to perform steps including:

Images