Methods for diagnosing the device

Abstract

A system for device diagnostics of an aerosol generating device and a charging device associated with the aerosol generating device is disclosed. The system includes a near field communication module including a non-volatile memory and a control unit. The control unit is configured to receive an indication of an error occurrence and update an error data log stored in the non-volatile memory by storing an error data entry associated with said error occurrence in the error data log. The error data entry is configured to be read by an external device even when the device including the near field communication module is not powered.

Description

Technical Field

[0004] , , , , ,

[0003] , ,

[0001] The present disclosure relates to the diagnosis of portable electronic devices, and more particularly to devices such as a charging device associated with an aerosol generator and an aerosol generator including a dynamic short-range wireless communication tag.

Background Art

[0002] An electronic device can generate an error log including diagnostic information of detected problems such as an error state. Such error logs stored on the electronic device are used for device diagnosis to track the cause of device failures. Such solutions support device maintenance. Portable electronic devices such as aerosol generators are carried around with the user's daily activities and are exposed to significant damage risks, such as mechanical stress from dropping on the road or contact with water on rainy days. As a result, the components of a portable electronic device may become irreparable unless they can access the error log stored in the device. In other cases, the components of a portable electronic device may fail because the components of the device have been replaced with inappropriate components. In such cases, the error log provides insights into why the device has failed, but is unavailable because the error log cannot be read unless power is supplied to the electronic device or the electronic device is inoperable.

Summary of the Invention

[0003] According to one aspect of the present invention, a system including a device is provided. The system includes a short-range wireless communication module including a non-volatile memory, and a control unit configured to receive an indication of an error occurrence and update an error data log stored in the non-volatile memory by storing error data input associated with the error occurrence in the error data log. The error data input is configured to be read by an external device even when the device is not powered. The device may be an aerosol generator or a charging device associated with the aerosol generator.

[0004] Accordingly, according to the disclosed invention, the control unit dynamically updates the contents of the data stored in the near-field wireless communication module with error data input. Since the near-field wireless communication module is relatively robust against environmental damage compared to other electronic components of the device, the present invention provides robust storage of error logs. Furthermore, since the near-field wireless communication module consumes energy from the external device that reads the module, error data input can be read even from a completely damaged device. Thus, the present invention provides robust storage of error logs.

[0005] The near-field wireless communication module may also be a near-field wireless communication tag. The system may also include a near-field wireless communication controller. A control unit that updates the error data log may include a control unit that transmits error data input to the near-field wireless communication controller. The near-field wireless communication controller may be configured to store the received error data input in the error data log.

[0006] The non-volatile memory may include a near-field communication data exchange format record configured to include at least one or both of the following: a unified resource location identifier and Bluetooth Low Energy pairing configuration data.

[0007] Saving error data inputs to an error data log may include saving the error data inputs in relation to the error type and timestamp. Saving error data inputs to an error data log may also include saving the error data inputs in relation to the device identification information.

[0008] The charging device may include a short-range wireless communication module and a control unit. The control unit may be configured to detect when the charging device has received and / or connected to an associated aerosol generator, and in response, to obtain an error data log associated with at least one error occurrence in the aerosol generator. The control unit may then update the error data log with the error data log associated with at least one error occurrence in the aerosol generator.

[0009] The system may include an aerosol generator, which is configured to detect at least one error occurring on the aerosol generator. The aerosol generator may be configured to update the error data log associated with at least one error occurring on the aerosol generator, which is stored in volatile memory, by saving the error data input associated with at least one error occurring on the aerosol generator to the error data log associated with at least one error occurring on the aerosol generator.

[0010] The control unit may also be configured to encrypt the error data log.

[0011] In another embodiment, a method for maintaining error data on a device is disclosed. The method includes monitoring for errors occurring in the device and updating an error data log stored in the non-volatile memory of the device's near-field wireless communication module by saving the error data input associated with the error occurrence to the error data log in response to the detection of an error occurrence. The method further includes transmitting the error data log to an external device via near-field wireless communication for diagnostic purposes.

[0012] Since short-range wireless communication modules are relatively robust under mechanical and chemical stress, the method of this disclosure enables the storage of error logs with improved robustness against environmental damage. The short-range wireless communication module also provides reliable access to the error log because an external device reading the short-range wireless communication module supplies the energy to activate the short-range wireless communication module's circuitry.

[0013] Updating the error data log may include transmitting the received error data input to a near-field wireless communication controller in order to save the error data input to the error data log. Monitoring error occurrences in an aerosol generator or charging device may include monitoring the device for error occurrences corresponding to multiple error conditions.

[0014] The method may include receiving an associated aerosol generator and / or a connected charging device, obtaining an error data log associated with at least one error occurrence of the aerosol generator, and updating the error data log with the error data log associated with at least one error occurrence of the aerosol generator. The method may further include encrypting the error data log.

[0015] According to another aspect of the present invention, a method for recovering error data from an apparatus is disclosed. The method discloses displaying a prompt on the user interface of the external apparatus to move the external apparatus closer to the aerosol generator and / or charging device. The method further includes, in response to detecting that the external apparatus is close to the aerosol generator or charging device, retrieving an error data log from the non-volatile memory of the apparatus's near-field wireless communication module via near-field wireless communication, and displaying the error data input from the error data log on the user interface.

[0016] By allowing access to error logs via short-range wireless communication, the present invention provides a method for rapidly analyzing a device without disassembling it. In particular, the present invention makes it possible to obtain error data logs even when the device's main circuit and power supply are not functioning.

[0017] As used herein, the term “aerosol generator” refers to a device that generates an aerosol by interacting with an aerosol-forming substrate. An aerosol generator may interact with one or both of the following: an aerosol-generating article containing an aerosol-forming substrate and / or a capsule containing an aerosol-forming substrate. In some embodiments, an aerosol generator may heat the aerosol-forming substrate to facilitate the release of volatile compounds from the substrate. An electrically operated aerosol generator may include an atomizer, such as an electric heater, for heating the aerosol-forming substrate to form an aerosol.

[0018] As used herein, the term “aerosol-forming substrate” refers to a substrate having the ability to release volatile compounds that can form aerosols. Volatile compounds may be released by heating or burning the aerosol-forming substrate. As an alternative to heating or burning, in some cases, volatile compounds may be released by chemical reactions or by mechanical stimuli such as ultrasound. The aerosol-forming substrate may be solid or liquid, or may contain both solid and liquid components. The aerosol-forming substrate may be part of an aerosol-generating article.

[0019] The present invention is defined in the claims. However, a non-exclusive list of non-limiting embodiments is provided below. One or more features of these embodiments may be combined with one or more features of other embodiments, forms, or aspects described herein. [Examples]

[0020] Example 1: A system comprising an aerosol generator and / or a charging device associated with an aerosol generator, wherein the system comprises a short-range wireless communication module including non-volatile memory, and a control unit configured to update an error data log stored in the non-volatile memory by receiving an indication of an error occurrence and saving an error data input associated with the error occurrence to the error data log, wherein the error data input is configured to be read by an external device even when the device comprising the short-range wireless communication module is not powered. Example 2: The system according to Example 1, wherein the short-range wireless communication module is a short-range wireless communication tag. Example 3: The system according to Example 1 or Example 2, wherein the aerosol generator and / or charging device includes a connection to a battery or external power source that supplies power to the control unit and the short-range wireless communication module, and the unpowered device includes a connection to a battery or external power source that does not supply power to the control unit and the short-range wireless communication module. Example 4: The system according to Embodiment 2, wherein a short-range wireless communication tag is configured to be read by an external device in accordance with a short-range wireless communication protocol. Example 5: The system according to any one of Examples 1 to 4, wherein the system includes a short-range wireless communication controller, a control unit that updates an error data log, a control unit that transmits error data input to the short-range wireless communication controller, and the short-range wireless communication controller is configured to store the received error data input in an error data log. Example 6: The system according to any one of Examples 1 to 5, wherein the control unit is configured to receive an indication of an error occurrence by being configured to monitor multiple error conditions. Example 7: The system according to any one of Examples 1 to 6, wherein the device including the short-range wireless communication module is an aerosol generator or a charging device associated with an aerosol generator. Example 8: The system according to any one of Examples 1 to 7, wherein error data logs are stored in a non-volatile memory as raw data and / or error data logs are stored in a non-volatile memory as a ring buffer. Example 9: The system according to any one of Examples 1 to 8, wherein the size of the error data log is 256 bytes. Example 10: The system according to any one of Examples 1 to 9, wherein the non-volatile memory further includes a short-range wireless communication data exchange format record configured to include identification information of a tobacco product. Example 11: The system according to any one of Examples 1 to 10, wherein the non-volatile memory further includes at least one or both of a short-range wireless communication data exchange format record configured to include a uniform resource locator and configuration data for Bluetooth Low Energy pairing. Example 12: The system according to any one of Examples 1 to 11, wherein storing error data input in an error data log includes storing the error data input in relation to an error type and a timestamp. Example 13: The system according to any one of Examples 1 to 12, wherein storing error data input in an error data log includes storing the error data input in relation to identification information of an aerosol generator and / or a charging device. Example 14: The system according to Example 13, wherein the identification information of the aerosol generator includes at least one of a product code, a serial number of the device, and a manufacturing plant code. Example 15: The system according to any one of Examples 1 to 14, wherein the control unit is configured to filter error data input before storing the error data input in an error log. Example 16: The system according to any one of Examples 1 to 15, wherein the short-range wireless communication module is configured to transmit a signal to the control unit indicating that an external device is currently reading from non-volatile memory. Example 17: The system according to Embodiment 16, wherein the control unit is further configured to avoid writing error data input in response to receiving an indication that an external device is currently reading nonvolatile memory. Example 18: The system according to any one of Examples 1 to 17, wherein the charging device includes a short-range wireless communication module and a control unit. Example 19: The system according to Embodiment 18, wherein the control unit is configured to receive an indication of an error occurring by monitoring the charging devices for error conditions of multiple charging devices. Example 20: The system according to Example 19, wherein the error conditions of multiple charging devices include a battery replacement error. Example 21: The system according to any one of Examples 1 to 20, wherein the control unit is configured to receive or connect to a charging device associated with an aerosol generator, to obtain an error data log associated with at least one error occurrence in the aerosol generator, and to update the error data log with the error data log associated with at least one error occurrence in the aerosol generator. Example 22: The system according to Example 21, wherein updating the error data log with an error data log associated with at least one error occurrence of the aerosol generator includes saving the error data input from the error data log associated with at least one error occurrence of the aerosol generator, associated with the serial number of the aerosol generator. Example 23: The system according to Example 21 or Example 22, wherein the control unit is configured to update the error data log using only error data inputs from the error data log associated with an error occurring in an aerosol generator that is not currently stored in the error data log. Example 24: The system according to any one of Examples 21 to 23, wherein the system further comprises an aerosol generator, the aerosol generator is configured to detect the occurrence of at least one error on the aerosol generator and update the error data log associated with the occurrence of at least one error on the aerosol generator, which is stored in volatile memory, by saving the error data input associated with the occurrence of at least one error on the aerosol generator to the error data log associated with the occurrence of at least one error on the aerosol generator. Example 25: The aerosol generator is a system according to any one of Examples 1 to 17, comprising a short-range wireless communication module and a control unit. Example 26: The system according to Example 22 or Example 25, wherein the error is a coil replacement error or a battery replacement error. Example 27: The system according to any of Examples 1 to 26, wherein the control unit is further configured to encrypt the error data log. Example 28: The system according to any one of Examples 1 to 27, further comprising an external device for diagnosing an aerosol generator or a charging device associated with an aerosol generator, wherein the external device is configured to retrieve an error data log from the nonvolatile memory via short-range wireless communication in response to determining that the nonvolatile memory corresponds to the nonvolatile memory of the aerosol generator or a charging device associated with an aerosol generator. Example 29: The system according to Embodiment 28, further configured with an external device to decode error data logs, sort the decoded error data logs, and display the decoded error logs in a user interface. Example 30: A method for maintaining error data on an aerosol generator and / or a charging device associated with an aerosol generator, the method comprising: monitoring for an error occurrence in the aerosol generator and / or charging device; updating an error data log stored in the non-volatile memory of the aerosol generator and / or charging device's near-field wireless communication module by storing an error data input associated with the error occurrence in the error data log in response to the error occurrence; and transmitting the error data log to an external device for diagnostic purposes via near-field wireless communication. Example 31: The method according to Embodiment 30, wherein the short-range wireless communication module is a short-range wireless communication tag. Example 32: The method according to Example 30 or Example 31, wherein updating the error data log includes transmitting the received error data input to a near-field wireless communication controller in order to save the error data input to the error data log. Example 33: The method according to any one of Examples 30 to 32, wherein monitoring for error occurrences in an aerosol generator and / or charging device includes monitoring the device for error occurrences in multiple error conditions. Example 34: The method according to any one of Examples 30 to 33, wherein saving the error data input to the error data log includes saving the error data input to the error data log as raw data. Example 35: The method according to any one of Examples 30 to 34, wherein the error data log is stored in non-volatile memory as a ring buffer. Example 36: The method according to any one of Examples 30 to 35, further comprising storing a Near Field Wireless Communication Data Exchange format record configured to include identification information of a tobacco product in a non-volatile memory. Example 37: The method according to any one of Examples 30 to 36, further comprising storing a Near Field Radio Data Exchange format record configured to include at least one or both of a Unified Resource Location identifier and a Near Field Radio Data Exchange format record related to Bluetooth Low Energy pairing configuration data in a non-volatile memory. Example 38: The method according to any one of Examples 30 to 37, wherein saving the error data input to an error data log includes saving the error input in relation to the error type and timestamp. Example 39: The method according to any one of Examples 30 to 38, wherein saving the error data input in an error data log is related to saving the error data input in relation to the identification information of the aerosol generator. Example 40: The method according to Example 39, wherein the identification information of the aerosol generator includes at least one of the following: a product code, a serial number of the device, and a manufacturer code. Example 41: The method according to any one of Examples 30 to 40, further comprising filtering the error data input before saving the error data input to the error log. Example 42: The method according to any one of Examples 30 to 40, further comprising receiving a notification that an external device is currently reading an error data log. Example 43: The method according to any one of Examples 30 to 42, wherein the error conditions of multiple charging devices include a battery replacement error. Example 44: The method according to any one of Examples 30 to 42, further comprising: in response to a charging device receiving an associated aerosol generator, obtaining an error data log associated with at least one error occurrence of the aerosol generator, and updating the error data log with the error data log associated with at least one error occurrence of the aerosol generator. Example 45: The method according to Example 44, wherein updating the error data log with an error data log associated with an error occurrence in the aerosol generator includes saving error data input from the error data log associated with at least one error occurrence in the aerosol generator, in relation to the serial number of the aerosol generator. Example 46: The method according to Example 44 or Example 45, wherein updating the error data log with error data logs associated with at least one error occurrence of the aerosol generator includes updating the error data log only with error data input from error data logs associated with an error occurrence of the aerosol generator that is not currently stored in the error data log. Example 47: The method according to any one of Examples 44 to 46, further comprising detecting the occurrence of at least one error on the aerosol generator and updating the error data log associated with the occurrence of at least one error on the aerosol generator, which is stored in volatile memory, by storing the error data input associated with the occurrence of at least one error on the aerosol generator in the error data log associated with the occurrence of at least one error on the aerosol generator. Example 48: The system according to Example 47, wherein the error is a coil replacement error or a battery replacement error. Example 49: The method according to any one of Examples 30 to 48, further comprising encrypting the error data log. Example 50: A method for recovering error data from an aerosol generator and / or a charging device associated with an aerosol generator, the method comprising: displaying a prompt on the user interface of an external device to move the external device closer to the device in response to detection that the external device is near the device; obtaining an error data log from the non-volatile memory of the device's near-field communication module via near-field communication; and displaying the error data input from the error data log on the user interface. Example 51: The method according to Example 50, wherein obtaining an error data log includes decoding the error data input from the error data log. Example 52: The method according to Example 50 or Example 51, further comprising decoding the error data input. Example 53: The method according to any one of Examples 50 to 52, further comprising sorting the error data inputs and displaying the error data inputs, comprising displaying a sorted list of error data inputs. [Brief explanation of the drawing]

[0021] Here, we will further describe the examples with reference to the figures.

[0022] [Figure 1A] Figure 1A shows a system that includes a device equipped with a short-range wireless communication module for device diagnostics. [Figure 1B] Figure 1B shows a non-volatile memory device maintained on a short-range wireless communication module for device diagnostics. [Figure 2A] Figure 2A shows an aerosol generator equipped with a short-range wireless communication module for device diagnostics. [Figure 2B] Figure 2B shows an aerosol generator equipped with a short-range wireless communication module for device diagnostics. [Figure 3] Figure 3 shows a charging device equipped with a short-range wireless communication module for device diagnostics. [Figure 4] Figure 4 shows a graphical user interface for device diagnostics. [Figure 5] Figure 5 shows a flowchart of the device diagnostic method. [Figure 6] Figure 6 shows a flowchart illustrating the method for obtaining diagnostic data from the device. [Modes for carrying out the invention]

[0023] Figure 1A shows a system comprising device 100 and an external device 140, the external device 140 configured to read error logs stored in the short-range wireless communication module 110 of device 100. Device 100 may be an aerosol generator or a charging device associated with an aerosol generator, as will be described in more detail below. Device 100 is controlled by a control unit 120. Device 100 comprises a communication module 130, a control unit 120, and a short-range wireless communication module 110. The control unit 120 may be configured to receive indications of error occurrences. The control unit 120 may be configured to monitor components of device 100 for multiple error conditions. In response to receiving an indication of an error occurrence, the control unit 120 may receive or generate data associated with the error occurrence. In Figure 1A, arrows indicate the data flow of data related to the error condition.

[0024] For example, an error could be caused by replacing the battery in device 100. An error indication might indicate the insertion of an inappropriate battery with battery characteristics that pose a risk of malfunction of device 100. For example, an inappropriate battery may have the wrong voltage, wrong capacity, or wrong discharge curve. Another error could be associated with replacing the coil used to generate aerosols from the aerosol generating article. Replacing a coil can also pose a risk to the safety of the operation of the aerosol generating device. Therefore, the control unit 120 may receive an indication that the coil has been replaced.

[0025] When an error occurs, the control unit 120 is configured to update the error data log 118 stored in the non-volatile memory 116 of the short-range wireless communication module 110 by saving data related to the error that occurred to the error data log 118. The error data log 118 may be configured as a ring buffer such that a fixed number of error data inputs are held and old data inputs are overwritten by new error data inputs. The configuration of the data error log 118 is described in more detail below. The non-volatile memory 116 may further store dynamic data related to improving the user experience, such as logging on to a product website or providing Bluetooth Low Energy pairing of the device 100 to an external device 140, as disclosed in European Patent Application No. 20 182 038.8.

[0026] More specifically, the control unit 120 may be a microcontroller unit. Storing error data input associated with the indicated error occurrence in an error data log may, more specifically, include the control unit 120 communicating with a near-field wireless communication controller 112, for example, by employing the I2C communication protocol. The near-field wireless communication controller 112 may be configured to receive error data input from the control unit 120 and write the error data input to an error data log 118. Specifically, the control unit 120 instructs the near-field wireless communication controller 112 to write the error data input to a specific address in the non-volatile memory 116.

[0027] Therefore, the control unit 120 dynamically updates the contents of the data stored in the near-field wireless communication module 110. Thus, communication between the control unit 120 and the near-field wireless communication controller 112 enables read and write access to the control unit 120's non-volatile memory 116. The near-field wireless communication module 110 includes an antenna 114 configured to be read by an external device 140, for example, according to a near-field wireless communication protocol or other radio frequency identification technology. The near-field wireless communication protocol or other radio frequency identification technology includes the near-field wireless communication module being powered by the external device 140. In particular, the power supplied to the near-field wireless communication module 110 from the external device 140 enables communication between the near-field wireless communication module 110 and the external device 140 without the near-field wireless communication module being connected to the power supply of the device 100. In particular, communication between the near-field wireless communication module 110 and the external device 140 does not involve the control unit 120 or any communication port such as a fragile USB port. Therefore, the external device 140 can read the non-volatile memory 116 even if the device 100 is not charged or is damaged.

[0028] The external device 140 may be a mobile terminal such as a mobile phone, smartphone, computer laptop, table computer, or personal digital assistant. The external device 140 comprises a near-field communication reader circuit 144, a memory 142 for storing software instructions 143, a communication module 146, and a processor 148. The external device 140, which executes the software instructions 143 using the processor 148, may receive a message from the near-field communication module 110 when the near-field communication reader circuit 144 of the external device 140 is activated and the distance between the external device 144 and the near-field communication module 110 is within the range that enables near-field communication. The near-field communication reader circuit 144 may then receive data stored in the non-volatile memory 116, including an error data log 118 and structured data records 117 such as website unified resource location identifiers and data related to Bluetooth Low Energy pairing.

[0029] The control unit 120 may send a request to the near-field wireless communication controller 112 to ask whether an external device, such as device 140, is currently reading the non-volatile memory 116. If the near-field wireless communication controller 112 indicates that an external device is currently reading the non-volatile memory 116, the control unit 120 may be configured to avoid instructing the near-field wireless communication controller 112 to update the error data log 118 with new error data input, in order to avoid data inconsistency.

[0030] Therefore, the near-field wireless communication module 110 may enable read-only access to the non-volatile memory 116 by the external device 140. However, in other embodiments, the near-field wireless communication module 110 may also be configured to enable read and write access to the non-volatile memory 116 by the external device 140.

[0031] Figure 1B shows a block diagram of the structure of the non-volatile memory 116. In addition to the error data log 118, the non-volatile memory includes a list 117 of structured data records 117a, 117b, and 117c. The format of the error data log 118 may differ from the formats of the structured data records 117a, 117b, and 117c. The format of the error data log 118 may be raw data. Raw data corresponds to data without a standard data format so that external viewers cannot understand the meaning or purpose of the data. To further enhance information security, the error data log 118 may be encrypted. In particular, since the raw data is provided to a dedicated application on an external device without prior processing, the dedicated application may be configured to decode the error data log according to a predetermined custom structure. The format of the structured data records 117a, 117b, and 117c may be a Near Field Wireless Communication Data Exchange Format Record.

[0032] Table 1 shows a specific example of the structural configuration of the non-volatile memory 116. The non-volatile memory 116 may be an EEPROM that includes an area 1 that can correspond to a list of lists of records 117, and an area 2 for storing error data logs 118 as raw memory. [Table 1]

[0033] Error data log 118 may contain an index of the error data input corresponding to the sequential number of the recorded error. The first recorded error receives an index of 1.

[0034] The error data log 118 may be further used to store the error type, which is the product code of the device 100, and is usually part of the device's serial code. The product code identifies what kind of device 100 it is, such as whether it is a charger or a holder. The error data log 118 may also indicate a unique device identifier. Thus, two different holder devices may have the same product code but different device numbers. The error data log 118 may also include a site code that identifies where the device was manufactured.

[0035] The error data log 118 may further include a timestamp identifying the date on which the recorded error was detected, for example, the date on which the battery of the device 100 was replaced. The date on which the recorded error was detected may correspond to the date and time recorded when the control unit 120 received an indication that an error had occurred.

[0036] Therefore, the error data log 118 may contain comprehensive information about the error to enable reliable device diagnostics.

[0037] In particular, in the example in Table 1, the size of the dedicated memory area 2 corresponding to the error data log 118 is 256 bytes, and therefore the error data log 118 can store 16 error data inputs.

[0038] The following describes the list of records 117 in more detail. When transferred to the external device 140, the list of records 117 can configure the external device to perform specific actions. The list of records 117 may include an NDEF record containing the URL of a website that the external device 140 may use to navigate to a designated website in order to improve the user experience. The list of records 117 may further include an NDEF record containing configuration data for Bluetooth Low Energy pairing, which may be used to establish Bluetooth communication between device 100 and the external device 140. The list of records 117 may also include an NDEF record configured to include identification information for tobacco products, such as a coded string.

[0039] The list of record 117 includes at least two records that are placed in the list.

[0040] The list of records 117 corresponds to a message containing lists of three records: the first record 117a, the second record 117b, and the third record 117c. At least the first record 117a and the second record 117b are of different record types. Therefore, at least the first record 117a and the second record 117b are associated with different operations performed by the external device 140.

[0041] The third record 117c may be of text type. The third record 117c may include an identification number, for example, the serial number of the device 100. The identification number may be used, for example, during the manufacture of the device or in other processes that require the identification of the device.

[0042] When the external device 140 is positioned near the device 100, the near-field wireless communication module 110 transmits message 117 to the external device 140. In other words, the external device 140 receives message 117 from the near-field wireless communication module 110 when the distance between the external device 140 and the near-field wireless communication module 110 falls below a threshold distance.

[0043] Since software instruction 143 automatically executes the operation associated with the record at the top of the list, the order of the records in the list defines the operation that is automatically executed by software instruction 143 of the external device 140. In other words, the order of the first record 117a and the second record 117b in the list defines whether the operation associated with the first record 117a or the operation associated with the second record 117b is automatically executed by the external device 140.

[0044] For example, Figure 1B shows that the first record 117a is at the beginning of the list, meaning that the first record 117a is at the top of the list. The second record 117b is second in the list, meaning that the second record 117b is in the middle of the list. The third record 117c is third in the list, meaning that the third record 117c is at the bottom of the list. However, naturally, records 117a, 117b, and 117c may be arranged in any order. Specifically, as will be explained in more detail below, the order of the records in the list is at least in part based on the detection of a predetermined state of the device 100. Thus, the operations performed automatically by the external device 140 depend at least in part on the state of the device 100.

[0045] Therefore, in response to receiving message 117, the application and / or operating system software 143 installed on the external device 140 executes the first record in the list of records (i.e., the top of the list). The external device 140 then executes the action associated with the executed record. Thus, as shown in Figure 1B, when the first record 117a is at the beginning of the list, the external device 140 automatically executes the action associated with the first record 117a. The actions associated with the second record 117b and the third record 117c are not executed automatically. When the second record 117b is at the beginning of the list, the external device 140 automatically executes the action associated with the second record 117b. The actions associated with the first record 117a and the third record 117c are not executed automatically.

[0046] The short-range wireless communication module 110 is configured such that the contents written to and stored in the short-range wireless communication module 110 during manufacturing can be changed during use of the short-range wireless communication module 110. Therefore, initially, the list of records in the message 117 stored by the short-range wireless communication module 110 may be in a first order. When the list of records is in the first order, the first action associated with the first record in the list is performed by the external device 140. Secondly, the message 117 stored by the short-range wireless communication module may be overwritten so that the list of records is in a second order. When the list of records is in the second order, the second action associated with the first record in the list, which is different from the first action, is performed by the external device 140.

[0047] More specifically, the control unit 120 is configured to configure a list of records in message 117, defining the order of the first record 117a and the second record 117b in the list. The control unit 120 configures the list of records in response to detecting a predetermined state of the device 100. The order of the records in the list is based on the specific predetermined state detected. For example, in response to detecting a first predetermined state of the device 100, the control unit 120 configures the list such that the first record 117a is at the beginning of the list, i.e., the first record 117a is at the top of the list. Next, when the control unit 120 detects a second predetermined state of the device, the control unit 120 configures the list such that the second record 117b is at the beginning of the list, i.e., the second record 117b is at the top of the list. Once the control unit 120 configures the list of records, message 117 containing the configured list of records is stored in the near-field communication module 110, thereby dynamically overwriting any previously stored messages 117 in the near-field communication module 110.

[0048] The first predetermined state may be an advertising state. In the advertising state, device 100 is in a mode that allows an external device 140, or any other suitable device, to connect communicatively with device 100. For example, when device 100 is in the advertising state, communication module 130 broadcasts advertising packets via communication module 146 of external device 140 that allow external device 140 to connect communicatively with device 100. Device 100 enters the advertising state when communication module 130 is turned on or otherwise activated. Communication modules 130 and 146 may be Bluetooth modules or Bluetooth Low Energy modules. The advertising state may be a Bluetooth advertising state or a Bluetooth Low Energy advertising state.

[0049] When the control unit 120 detects the advertising status of the device 100, the control unit 120 configures the list so that the first record 117a is at the top of the list. The first record 117a may be a multipurpose Internet mail extended media type. If the first record 117a is a multipurpose Internet mail extended media type, the first record 117a includes data that enables the external device 140 to connect to the device 100 in a communicative manner when the external device 140 performs the first record 117a. For example, the first record 117a may include a Bluetooth address or a Bluetooth Low Energy address.

[0050] Therefore, when the distance between the external device 140 and the short-range wireless communication module 110 falls below a threshold distance, the short-range wireless communication module 110 sends a message 117 to the external device 140. The message is configured such that the first record 117a is at the beginning of the list of records, so the external device 140 performs the first record 117a and becomes communicatively paired with the device 100.

[0051] The second predetermined state may be a communicated-coupled state, that is, the device 100 and the external device 140 are communicated-coupled to each other via their respective communication modules 130 and 146. For example, when the device 100 automatically pairs with the external device 140, the device 100 leaves the advertising state and enters a communicated-coupled state. The communicated-coupled state may be a Bluetooth connection state or a Bluetooth Low Energy connection state.

[0052] Alternatively or additionally, the second predetermined state may be an off state, which means that the communication module 130 is off or not activated.

[0053] When the control unit 120 detects that the device 100 is in a communicably coupled state or an off state, the control unit 120 configures a list of records such that the second record 117b is at the top of the list. The second record 117b may be of a unified resource identifier type. The second record 117b may contain data that enables the external device 135 to open an application or open an internet browser and navigate to a website. For example, the second record 117b may contain a unified resource location identifier.

[0054] Therefore, when the distance between the external device 140 and the short-range wireless communication module 110 falls below a threshold distance, the short-range wireless communication module 110 sends a message 117 to the external device 140. Since message 117 is configured such that the second record 117b is the first in the list of records, the operating system software and / or application software 150 installed on the external device 140 executes the second record 117b. As a result of executing the second record 117b, the software 150 causes the internet browser to automatically open and navigate to the website associated with the unified resource location identifier contained in the second record 117b. Alternatively, or additionally, as a result of executing the second record 117b, other application software may be launched.

[0055] A website or application launched in response to the execution of the second record 117b may allow a user to register the device 100. For example, the unified resource location identifier included in the second record 117b may include a link to an account associated with the device 100. Once the device 100 is registered, the external device 140 may send a registration confirmation message to the device 100. In response to receiving the registration confirmation message, the control unit 120 is configured to begin unlocking the device 100 so that it can be operated by a user. For example, when the device 100 is shipped after manufacturing, the device 100 may be in a locked state, meaning it cannot be operated by a user. When the device 100 receives the registration confirmation message, the control unit 120 configures the device 100 to be operable by a user. In other words, the control unit unlocks the device 100, and the device 100 is now in an unlocked state.

[0056] The control unit 120 may be configured to encrypt the error data input before saving them to the error data log on the short-range wireless communication module 110.

[0057] In other embodiments, the control unit 120 may filter out errors occurring on the device 100 to limit the number of error data inputs stored in the error data log 118, taking into account the limited size of the non-volatile memory device 116.

[0058] The system described with reference to Figures 1A and 1B can be implemented in an aerosol generator such as the aerosol generator 200A shown in Figure 2A or the aerosol generator 200B shown in Figure 2B. The system may also be implemented in a charging device associated with an aerosol generator, such as the charging device 300 shown in Figure 3.

[0059] Referring to Figure 2, the aerosol generator 200A is configured to receive an aerosol generating article 220. Specifically, the aerosol generator 200A includes a cavity 210 for receiving the aerosol generating article 220. The aerosol generating article 220 may include an aerosol forming substrate. The aerosol forming substrate of the aerosol generating article 220 may be a solid such as a cigarette stick. The aerosol generator 200A further includes a heating element 230. The heating element 230 is configured to heat the aerosol forming substrate to form an aerosol.

[0060] The aerosol generator 200B is configured to receive a cartridge 280. In particular, the aerosol generator 200B includes a cavity 270 for receiving the cartridge 280. The cartridge 280 may contain an aerosol-forming substrate. The aerosol-forming substrate of the cartridge 280 may be a liquid. The aerosol generator 200B further includes a heating element 290. The heating element 290 is configured to heat the aerosol-forming substrate to form an aerosol.

[0061] Preferably, aerosol generators 200A and 200B each include a power supply configured to supply power to their respective heating elements 230 and 290. The power supply is preferably a power supply 240, which is preferably a battery such as a lithium-ion battery. Alternatively, power supply 240 may be another form of charge storage device such as a capacitor. Power supply 240 may require recharging. For example, power supply 240 may have sufficient capacity to enable continuous aerosol generation for approximately six minutes, or for a time period that is a multiple of six minutes. In another example, power supply 240 may have sufficient capacity to enable a predetermined number of fume extractions or discontinuous starts of the heater assembly. Aerosol generators 200A and 200B each may include a power contact 250 for recharging power supply 240. Power supply 240 of aerosol generators 200A and 200B may be recharged using a charging device such as the charging device 300 shown in Figure 3.

[0062] The power supply 240 may include a control electronic circuit. The control electronic circuit may include a microcontroller. Preferably, the microcontroller is a programmable microcontroller. The electrical circuit may include further electronic components. The electrical circuit may be configured to regulate the supply of power to the heater assembly. Power may be supplied to the heater assembly continuously after the system is started up, or intermittently (for example, each time smoke is extracted). Power may be supplied to the heater assembly in the form of current pulses.

[0063] In these embodiments, the aerosol generators 200A and 200B include a short-range wireless communication module 110, which is indicated by a dashed line. In these embodiments, the aerosol generators 200A and 200B correspond to the device 100 described above with reference to Figure 1A. In these embodiments, the control unit 120 is configured to receive an indication of an error occurring in the aerosol generators 200A and 200B, as described above with reference to Figure 1A, and to update an error data log maintained in the non-volatile memory on the short-range wireless communication module 110.

[0064] In other embodiments, the aerosol generators 200A and 200B do not have a short-range wireless communication module, while the charging device 300 associated with the aerosol generators 200A and 200B includes a short-range wireless communication module 110 for storing error data inputs from both the aerosol generators 200A and 200B and the charging device 300. The charging device 300 is described in more detail in Blow with reference to Figure 3. In these embodiments, the aerosol generators 200A and 200B include a memory 280 which may be volatile or non-volatile memory. In these embodiments, the control unit 120 is configured to receive an indication of an error occurrence in the aerosol generators 200A and 200B and to store an error data input associated with the error occurrence in the memory 280. The error data input stored in the memory 280 may be retrieved from the aerosol generators 200A and 200B to the charging device 300 when the aerosol generators 200A and 200B are inserted into the charging device 300. When used regularly, the aerosol generators 200A and 200B are frequently recharged within the charging device 300. Therefore, obtaining error data input from the aerosol generators 200A and 200B to the charging device 300 makes it possible to collect reliable diagnostic information.

[0065] In further embodiments, both the aerosol generators 200A, 200B and the associated charging device 300 include a near-field communication module 110. In such embodiments, the aerosol generators 200A, 200B do not include memory 280, but store error data inputs in the near-field communication module 110 as described above. When the aerosol generators 200A, 200B are inserted into the charging device 300, the error data inputs stored in the near-field communication module 110 on the aerosol generators 200A, 200B may be retrieved by the charging device 300. Thus, both the aerosol generators 200A, 200B and the associated charging device 300 provide a fail-safe error log.

[0066] Figure 3 shows a charging device 300 including the short-range wireless communication module 110 described above with reference to Figure 1A. The charging device 300 includes a cavity 310 configured to receive an aerosol generator, such as an aerosol generator 200A and an aerosol generator 200B. Within the cavity 310 there may be a power contact 320 configured to contact the corresponding power contact 250 of the aerosol generator. Specifically, when an aerosol generator 200A or an aerosol generator 200B is received into the cavity 310, the power contact 250 contacts the power contact 320 so that the charging device 300 can charge the rechargeable power supply 240 of the aerosol generator 200A or an aerosol generator 200B.

[0067] Furthermore, the charging device 300 and the aerosol generator 200A or 200B may be configured to exchange data with each other. For example, the charging device 300 and the aerosol generator 200A or 200B may be configured to exchange data wirelessly with each other. For example, the charging device 300 and the aerosol generator 200A or 200B may exchange data via their respective communication modules 130.

[0068] Additionally or alternatively, the charging device 300 may include a data contact interface 330 for communicating with aerosol generators 200A and 200B. Referring again to Figures 2A and 2B, aerosol generators 200A and 200B are shown as including a data contact interface 260. When aerosol generator 200A or aerosol generator 200B is received in the cavity 310, the data contact interface 330 makes contact with the data contact interface 260, and data can be exchanged. For example, aerosol generator 200A or 200B may communicate data, such as usage data, to the charging device 300 via the data contact interfaces 260 and 330.

[0069] In particular, the charging device 300 may receive error data input stored in the memory 280 via communication through contact interfaces 330 and 260. The aerosol generator 200A or 200B may also communicate usage data to the charging device 300 via data contact interfaces 260 and 330.

[0070] After receiving error data input from aerosol generators 200A and 200B, the control unit 120 of the charging device 300 is configured to store the received error data input in an error data log 118 maintained in non-volatile memory 116, along with error data input previously received from other aerosol generators and error data input related to errors occurring in the charging device 300 itself. In this embodiment, only error data input not currently stored on the short-range wireless communication module 110 is written to the error data log 116, saving memory space. Errors obtained from the received aerosol generators 200 may be associated with the product code and serial number of a specific aerosol generator 200A or 200B, so that when the charging device 300 receives a different aerosol generator, the error can be traced back to the specific aerosol generator 200A or 200B where the error occurred. Thus, the charging device 300 collects all errors from the charging device 300 itself and from aerosol generators inserted into the charging device 300.

[0071] This disclosure further describes a user interface for recovering errors from a near-field wireless communication module of an aerosol generator or a charger associated with an aerosol generator. Figure 4 shows user interfaces 410 and 420 provided on an external device, such as the external device 140 discussed with reference to Figure 1A. User interface 410 displays an instruction 415 that instructs the user to move the external device closer to the device, such as the aerosol generator or charger, by tapping the near-field wireless communication reader in the area of ​​the device.

[0072] Next, the application may configure an external device to retrieve an error data log from the non-volatile memory of the device's near-field wireless communication module. Optionally, the application then configures the external device to decode the error data log and decode the error data input. The external device may be configured to sort the decoded error data input. Next, the external device may render a user interface 420. The user interface 420 displays a list 424 of charger errors related to errors that occurred in the charging device, as described above with reference to Figure 3. The list 424 may be sorted according to the error code.

[0073] The user interface 420 further displays a list 426 of holder errors related to errors in aerosol generators 200A and 200B, obtained from aerosol generators 200A and 200B by the charging device 300, as described above. The list 426 can be sorted by grouping the errors according to the serial number of the aerosol generator 200A and 200B that experienced the particular error.

[0074] Figure 5 shows a flowchart of method 500 for maintaining error data on devices such as devices 200A, 200B described above with reference to Figures 2A and 2B, or device 300 described above with reference to Figure 3. Method 500 includes step 510 of monitoring for the occurrence of errors in the device. For example, monitoring the device may include monitoring a set of predetermined error conditions.

[0075] In response to receiving an indication of an error occurrence, method 500 further includes step 520 updating the error data log stored in the non-volatile memory of the device's near-field radio communication module by saving the error data input associated with the error occurrence to the error data log. As described above, saving the error data input to the error data log may include storing the error data input in the error data log as described above, and optionally, encrypting the error data input.

[0076] When Method 500 is carried out by the charging device 300 described above with reference to Figure 3, Method 500 may optionally include a step 530 of receiving an aerosol generator associated for charging. In response to step 530, the charging device may, in step 540, acquire an error data log associated with an error occurring on the aerosol generator. The error data log of the aerosol generator may be stored in a volatile memory device 280 as described above with reference to Figures 2A and 2B, and may be acquired by using communication between the respective wireless communication modules 130, or by using communication via the data contact interface 330 and the data contact interface 260. The acquired error data log may be combined with an error data log maintained in the non-volatile memory of the near-field wireless communication module on the charging device.

[0077] Method 500 may also include step 550 of transmitting an error data log via short-range wireless communication to an external device near the aerosol generator or charging device, enabling the external device to retrieve the error data log even if the device ceases to function after the last update of the non-volatile memory.

[0078] Figure 6 shows a flowchart of a method 600 for recovering error data from an aerosol generator or a charging device associated with an aerosol generator, such as by using an external device 140 including a short-range wireless communication reader.

[0079] Method 600 includes step 610 of displaying a prompt on the user interface of an external device to move the external device closer to the device, such as by displaying instruction 415 on the user interface 410. The application can then detect the presence of the device's near-field communication module.

[0080] In response, in step 620, the application retrieves an error data log from the non-volatile memory of the detected near-field communication module.

[0081] In step 630, the application decodes the error data input. Optionally, step 630 may include decrypting the error data input as described in more detail above.

[0082] Method 600 further includes step 640 of displaying the recovered error data input. Displaying the error data input may include sorting the error data input by, for example, product type and device serial number. Step 640 may include rendering graphical user interfaces 410 and 420 as described above with reference to Figure 4.

[0083] With respect to Figures 5 and 6, some or all of the method steps described above can be carried out by a computer, in that they are performed (or used) by a processor, microprocessor, electronic circuit, or processing circuit. For example, the implementation can be carried out using a non-temporary storage medium such as a computer-readable storage medium. Such a computer-readable medium may be any available medium accessible by a general-purpose computer system or a dedicated computer system.

[0084] In general, the embodiments described herein can be implemented as computer program products having program code or computer executable instructions, the program code or computer executable instructions being operable to perform one of the methods when the computer program product is executed on a computer. The program code or computer executable instructions may be stored, for example, on a computer-readable storage medium.

[0085] In one embodiment, a storage medium (or data carrier, or computer-readable medium) stores a computer program or computer-executable instruction for performing one of the methods described herein when executed by a processor. In a further embodiment, the apparatus comprises one or more processors and the storage medium described above.

[0086] In further embodiments, the apparatus includes, for example, processing circuit means such as a processor that communicates with memory, and the means is configured or adapted to carry out one of the methods described herein.

[0087] Further embodiments include a computer on which a computer program or instructions for carrying out one of the methods described herein is installed.

[0088] The specific embodiments and examples described above illustrate, but do not limit, the present invention. Other embodiments of the present invention may be made, and it should be understood that the specific embodiments and examples described herein are not exhaustive.

[0089] For the purposes of this specification and the appended claims, unless otherwise indicated, all figures representing amounts, quantities, percentages, etc., should be understood in all cases to be modified by the term “approximately.” Furthermore, all ranges include the disclosed maximum and minimum points and any intermediate ranges therebetween, which may or may not be specifically listed herein.

Claims

1. A system comprising an aerosol generator and / or a charging device associated with the aerosol generator, wherein the system A short-range wireless communication module including non-volatile memory, The system includes a control unit configured to receive a notification of an error and update the error data log stored in the non-volatile memory by saving the error data input associated with the error to the error data log, A system configured such that the error data input can be read by an external device even when the device equipped with the short-range wireless communication module is not powered.

2. The system according to claim 1, wherein the short-range wireless communication module is a short-range wireless communication tag, and optionally the system comprises a short-range wireless communication module system including a short-range wireless communication controller, the control unit that updates the error data log comprises a control unit that transmits the error data input to the short-range wireless communication controller, and the short-range wireless communication controller is configured to store the transmitted error data input in the error data log.

3. The system according to claim 1 or 2, wherein the non-volatile memory further comprises a short-range wireless communication data exchange format record configured to include a unified resource location identifier and configuration data for Bluetooth Low Energy pairing.

4. The system according to any one of claims 1 to 3, wherein saving the error data input to the error data log includes saving the error data input in relation to the error type and timestamp.

5. The system according to any one of claims 1 to 4, wherein storing the error data input in the error data log includes storing the error data input in relation to the identification information of the aerosol generator or the charging device.

6. The system according to claims 1 to 5, wherein the device including the short-range wireless communication module is the aerosol generator or the charging device associated with the aerosol generator.

7. The system according to any one of claims 1 to 5, wherein the charging device includes the short-range wireless communication module and the control unit.

8. The system according to claim 7, wherein the control unit is configured to, in response to the charging device connected to the associated aerosol generator, acquire an error data log associated with at least one error occurrence in the aerosol generator, and update the error data log with the error data log associated with at least one error occurrence in the aerosol generator.

9. The system according to claim 7 or 8, wherein the system comprises the aerosol generator, the aerosol generator is configured to detect the occurrence of at least one error on the aerosol generator, and to update the error data log associated with the occurrence of at least one error on the aerosol generator stored in volatile memory by storing the error data input associated with the occurrence of at least one error on the aerosol generator in the error data log associated with the occurrence of at least one error on the aerosol generator.

10. The system according to any one of claims 1 to 9, wherein the control unit is further configured to encrypt the error data log.

11. A computer-implemented method for maintaining error data on an aerosol generator and / or a charging device associated with an aerosol generator, wherein the method is To monitor for errors occurring in the aerosol generator and / or the charging device, In response to an error occurring, the error data log stored in the non-volatile memory of the short-range wireless communication module of the aerosol generator and / or the charging device is updated by saving the error data input associated with the occurrence of the error to the error data log. A computer-implemented method comprising transmitting the error data log to an external device for diagnostic purposes via short-range wireless communication.

12. The computer-implemented method according to claim 11, wherein updating the error data log includes transmitting the error data input to a short-range wireless communication controller and storing the transmitted error data input in the error data log.

13. The computer-implemented method according to claim 11 or 12, wherein monitoring for errors in the aerosol generator and / or the charging device includes monitoring for errors in the device for a plurality of error conditions.

14. A computer-implemented method according to one of claims 11 to 13, further comprising: obtaining an error data log associated with at least one error occurrence of the aerosol generator in response to the charging device connected to the associated aerosol generator; and updating the error data log with the error data log associated with at least one error occurrence of the aerosol generator.

15. A computer-implemented method according to any one of claims 11 to 14, further comprising encrypting the error data log.

16. A computer-implemented method for recovering error data from an aerosol generator and / or a charging device associated with an aerosol generator, wherein the method is A prompt to move the external device closer to the aerosol generator and / or the charging device is displayed on the user interface of the external device, In response to detecting that the external device is near the aerosol generator or the charging device, error data logs are obtained via near-field wireless communication from the non-volatile memory of the near-field wireless communication module of the aerosol generator and / or the charging device. A computer-implemented method, which includes displaying error data input from the error data log on the user interface.

Images