Equipment Diagnosis Method

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]

[0001] The present disclosure relates to diagnostics for portable electronic devices, and more particularly to devices such as aerosol-generating devices and charging devices associated with aerosol-generating devices that include dynamic near-field communication tags. [Background technology]

[0002] Electronic devices can generate error logs that contain diagnostic information for detected problems, such as error conditions. Such error logs stored on the electronic device are used for device diagnostics to trace the cause of device failure. Such a solution supports device maintenance. Portable electronic devices, such as aerosol generating devices, are carried along with the user's daily activities and are exposed to significant risks of damage, for example mechanical stress from being dropped on the road or contact with water on rainy days. As a result, components of the portable electronic device may be unable to be recovered unless the error log stored on the device can be accessed. In other cases, components of the portable electronic device may fail because a component of the device has been replaced with an inappropriate component. In such cases, the error log provides insight into why the device is failing, but is unavailable because the error log cannot be read without power to the electronic device or because the electronic device is inoperable. Summary of the Invention

[0003] According to one aspect of the invention, there is provided a system including an apparatus, the system including a near field 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 an error data entry associated with said error occurrence in the error data log, the error data entry being configured to be read by an external device even when the apparatus is not powered. The apparatus may be an aerosol generating apparatus or a charging device associated with the aerosol generating apparatus.

[0004] Thus, in accordance with the disclosed invention, the control unit dynamically updates the data content stored in the short-range wireless communication module with error data inputs. Because the short-range wireless communication module is relatively robust to environmental damage compared to other electronic components of the device, the invention provides robust storage of the error log. Furthermore, because the short-range wireless communication module consumes energy from an external device that reads the short-range wireless communication module, the error data inputs can be read even from a completely damaged device. Thus, the invention provides robust storage of the error log.

[0005] The near field communication module may be a near field communication tag. The system may also include a near field communication controller. The control unit for updating the error data log may include a control unit for sending the error data entry to the near field communication controller. The near field communication controller may be configured to store the received error data entry in the error data log.

[0006] The non-volatile memory may comprise a near field communication data exchange format record configured to include at least one or both of a uniform resource locator and a near field communication data exchange format record configured to include configuration data for Bluetooth Low Energy pairing.

[0007] Storing the error data entry in the error data log may include storing the error data entry in association with an error type and a timestamp. Storing the error data entry in the error data log may include storing the error data entry in association with an identification of the device.

[0008] The charging device may include a near field 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 generating device and, in response, retrieve an error data log associated with at least one error occurrence in the aerosol generating device. 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 generating device.

[0009] The system may comprise an aerosol generating device configured to detect at least one error occurrence on the aerosol generating device, and the aerosol generating device may be configured to update an error data log associated with the at least one error occurrence on the aerosol generating device stored in a volatile memory by storing an error data entry associated with the at least one error occurrence on the aerosol generating device in an error data log associated with the at least one error occurrence on the aerosol generating device.

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

[0011] In another aspect, a method of maintaining error data on a device is disclosed. The method includes monitoring the device for an error occurrence and, in response to detecting the error occurrence, updating an error data log stored in a non-volatile memory of a near field communication module of the device by storing an error data entry associated with the error occurrence in the error data log. The method further includes transmitting, via near field communication, the error data log to an external device for diagnosis.

[0012] Because short-range wireless communication modules are relatively robust under mechanical and chemical stress, the disclosed method allows for the storage of an error log 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 provides energy to power the circuitry of the short-range wireless communication module.

[0013] Updating the error data log may include sending the error data entry to a near field communication controller for storing the received error data entry in the error data log. Monitoring the aerosol generating device or the charging device for error occurrences may include monitoring the device for error occurrences corresponding to a plurality of error conditions.

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

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

[0016] By allowing access to the error log via near field communication, the present invention provides a way to quickly analyze a device without disassembling the device. In particular, the present invention allows for the error data log to be obtained even if the device's main circuits and power supply are not functioning.

[0017] The term "aerosol-generating device" as used herein refers to a device that interacts with an aerosol-forming substrate to generate an aerosol. The aerosol-generating device may interact with one or both of an aerosol-generating article that includes an aerosol-forming substrate and a capsule that includes an aerosol-forming substrate. In some embodiments, the aerosol-generating device may heat the aerosol-forming substrate to facilitate the release of volatile compounds from the substrate. An electrically operated aerosol-generating device may include an atomizer, such as an electric heater, for heating the aerosol-forming substrate to form an aerosol.

[0018] The term "aerosol-forming substrate" as used herein refers to a substrate capable of releasing a volatile compound capable of forming an aerosol. The volatile compound may be released by heating or burning the aerosol-forming substrate. As an alternative to heating or burning, in some cases the volatile compound may be released by a chemical reaction or by mechanical stimulation such as ultrasound. The aerosol-forming substrate may be solid or liquid, or may include 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, below is provided a non-exhaustive list of non-limiting examples. Any one or more of the features of these examples may be combined with any one or more features of any other example, embodiment, or aspect described herein. EXAMPLES

[0020] Example 1: A system comprising an aerosol generating device and / or a charging device associated with the aerosol generating device, the system comprising a near-field 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 an error data entry associated with the error occurrence in the error data log, the error data entry being configured to be read by an external device even when the device comprising the near-field communication module is not powered. Example 2: 2. The system of claim 1, wherein the short-range wireless communication module is a short-range wireless communication tag. Example 3: A system as described in Example 1 or Example 2, wherein the aerosol generating device and / or charging device include a connection to a battery or external power source that powers the control unit and the near-field wireless communication module, and the unpowered device includes a connection to a battery or external power source that does not power the control unit and the near-field wireless communication module. Example 4: The system of example 2, wherein the near field communication tag is configured to be read by an external device according to a near field communication protocol. Example 5: The system of any one of Examples 1 to 4, wherein the system comprises a near field communication controller, the control unit for updating the error data log comprises a control unit for sending error data inputs to the near field communication controller, and the near field communication controller is configured to store the received error data inputs in the error data log. Example 6: The system of any one of the preceding embodiments, wherein the control unit is configured to monitor a plurality of error conditions and thereby receive an indication of an occurrence of an error. Example 7: The system according to any one of the first to sixth embodiments, wherein the device including the short-range wireless communication module is an aerosol generating device or a charging device associated with the aerosol generating device. Example 8: The system according to any one of the first to seventh embodiments, wherein the error data log is stored in the non-volatile memory as raw data and / or the error data log is stored in the non-volatile memory as a ring buffer. Example 9: The system according to any one of the first to eighth embodiments, wherein the size of the error data log is 256 bytes. Example 10: The system of any one of Examples 1 to 9, wherein the non-volatile memory further comprises a near-field communication data exchange format record configured to contain identification information of the tobacco product. Example 11: The system of any of Examples 1 to 10, wherein the non-volatile memory further includes a near field communication data exchange format record configured to include at least one or both of a uniform resource locator and a near field communication data exchange format record configured to include configuration data for Bluetooth Low Energy pairing. Example 12: 12. The system of any of claims 1-11, wherein storing the error data entry in the error data log includes storing the error data entry in association with an error type and a timestamp. Example 13: A system described in any of Examples 1 to 12, wherein storing the error data entry in an error data log includes storing the error data entry in association with identification information of the aerosol generating device and / or the charging device. Example 14: The system of Example 13, wherein the identification information of the aerosol generating device includes at least one of a product code, a device serial number, and a manufacturer code. Example 15: 15. The system of any one of embodiments 1 to 14, wherein the control unit is configured to filter the erroneous data input before storing the erroneous data input in the error log. Example 16: A system according to any one of the preceding embodiments, wherein the near field communication module is configured to transmit to the control unit an indication that an external device is currently reading the non-volatile memory. Example 17: 17. The system of example 16, wherein the control unit is further configured to avoid writing erroneous data inputs in response to receiving an indication that an external device is currently reading the non-volatile memory. Example 18: The system according to any one of the first to seventeenth embodiments, wherein the charging device includes a short-range wireless communication module and a control unit. Example 19: 20. The system of example 18, wherein the control unit is configured to monitor the charging devices for error conditions of the multiple charging devices, thereby receiving an indication of an error occurrence. Example 20: 20. The system of embodiment 19, wherein the error condition of the multiple charging devices includes a battery replacement error. Example 21: A system described in any of Examples 1 to 20, wherein the control unit is configured to obtain an error data log associated with at least one error occurrence in the aerosol generating device in response to a charging device receiving or connecting to an associated aerosol generating device, and to update the error data log with the error data log associated with at least one error occurrence in the aerosol generating device. Example 22: The system of Example 21, wherein updating the error data log with an error data log associated with at least one error occurrence in the aerosol generating device includes storing an error data entry from the error data log associated with at least one error occurrence in the aerosol generating device, associated with the serial number of the aerosol generating device. Example 23: A system as described in Example 21 or Example 22, wherein the control unit is configured to update the error data log using only error data entries from the error data log associated with error occurrences in the aerosol generating device that are not currently stored in the error data log. Example 24: The system of any of Examples 21 to 23, further comprising an aerosol generating device, the aerosol generating device being configured to detect at least one error occurrence on the aerosol generating device and update an error data log associated with the at least one error occurrence on the aerosol generating device stored in the volatile memory by storing an error data entry associated with the at least one error occurrence on the aerosol generating device in an error data log associated with the at least one error occurrence on the aerosol generating device. Example 25: The system according to any one of the preceding embodiments, wherein the aerosol generating device includes a near-field wireless communication module and a control unit. Example 26: A system described in Example 22 or Example 25, wherein the error occurrence is a coil replacement error or a battery replacement error. Example 27: The system of any one of Examples 1 to 26, wherein the control unit is further configured to encrypt the error data log. Example 28: A system as described in any of Examples 1 to 27, further comprising an external device for diagnosing the aerosol generating device or a charging device associated with the aerosol generating device, wherein the external device is configured to obtain an error data log from the non-volatile memory via near-field wireless communication in response to determining that the non-volatile memory corresponds to the non-volatile memory of the aerosol generating device or the charging device associated with the aerosol generating device. Example 29: 29. The system of example 28, wherein the external device is further configured to decode the error data log, sort the decoded error data log, and display the decoded error log on a user interface. Example 30: A method for maintaining error data on an aerosol generating device and / or a charging device associated with the aerosol generating device, the method including monitoring an error occurrence on the aerosol generating device and / or the charging device, and in response to the error occurrence, updating an error data log stored in a non-volatile memory of a near field communication module of the aerosol generating device and / or the charging device by storing an error data entry associated with the error occurrence in the error data log, and transmitting the error data log via near field communication to an external device for diagnosis. Example 31: The method of embodiment 30, wherein the short-range wireless communication module is a short-range wireless communication tag. Example 32: The method of example 30 or example 31, wherein updating the error data log includes sending the received error data entry to a near field communication controller for storing the received error data entry in the error data log. Example 33: The method of any of Examples 30 to 32, wherein monitoring the aerosol generating device and / or the charging device for occurrence of an error comprises monitoring the device for occurrence of an error for a plurality of error conditions. Example 34: 34. The method of any of Examples 30-33, wherein storing the error data entry in the error data log comprises storing the error data entry in the error data log as raw data. Example 35: The method according to any one of embodiments 30 to 34, wherein the error data log is stored in a non-volatile memory as a ring buffer. Example 36: The method of any of Examples 30 to 35, further comprising storing in non-volatile memory a near field communication data exchange format record configured to include identification information of the tobacco product. Example 37: The method of any of Examples 30 to 36, further comprising storing in a non-volatile memory a near field communication data exchange format record configured to include at least one or both of a uniform resource locator and a near field communication data exchange format record associated with Bluetooth Low Energy pairing configuration data. Example 38: 38. The method of any of Examples 30-37, wherein storing the error data entry in the error data log includes storing the error data entry in association with an error type and a timestamp. Example 39: The method of any of Examples 30 to 38, wherein storing the error data entry in the error data log includes storing the error data entry in association with identification information of the aerosol generating device. Example 40: The method of example 39, wherein the identification information of the aerosol generating device includes at least one of a product code, a device serial number, and a manufacturer code. Example 41: 41. The method of any of claims 30-40, further comprising filtering the erroneous data entries before storing the erroneous data entries in the error log. Example 42: 41. The method of any one of examples 30 to 40, further comprising receiving an indication that the external device is currently reading the error data log. Example 43: 43. The method according to any one of embodiments 30 to 42, wherein the error conditions of the plurality of charging devices include a battery replacement error. Example 44: A method as described in any of examples 30 to 42, further comprising, in response to the charging device receiving the associated aerosol generating device, obtaining an error data log associated with at least one error occurrence in the aerosol generating device, and updating the error data log with the error data log associated with at least one error occurrence in the aerosol generating device. Example 45: The method of example 44, wherein updating the error data log with an error data log associated with an error occurrence in the aerosol generating device includes storing an error data entry from an error data log associated with at least one error occurrence in the aerosol generating device in association with a serial number of the aerosol generating device. Example 46: The method of example 44 or example 45, wherein updating the error data log with an error data log associated with at least one error occurrence in the aerosol generating device includes updating the error data log with only error data entries from error data logs associated with error occurrences in the aerosol generating device that are not currently stored in the error data log. Example 47: The method of any of Examples 44 to 46, further comprising detecting at least one error occurrence on the aerosol generating device, and updating an error data log associated with the at least one error occurrence on the aerosol generating device stored in a volatile memory by storing an error data entry associated with the at least one error occurrence on the aerosol generating device in an error data log associated with the at least one error occurrence on the aerosol generating device. Example 48: The system described in Example 47, wherein the error occurrence 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 generating device and / or a charging device associated with the aerosol generating device, the method including: in response to detecting that an external device is near the device, displaying a prompt on a user interface of the external device to move the external device closer to the device; retrieving an error data log from a non-volatile memory of a near field communication module of the device via near field communication; and displaying an error data entry from the error data log on the user interface. Example 51: 51. The method of example 50, wherein obtaining the error data log includes decoding the error data entry from the error data log. Example 52: The method of example 50 or example 51, further comprising decoding the erroneous data input. Example 53: 53. The method of any of Examples 50 to 52, further comprising sorting the error data entries, and wherein displaying the error data entries comprises displaying a sorted list of the error data entries. [Brief description of the drawings]

[0021] The embodiments will now be further described with reference to the figures.

[0022] [Figure 1A] FIG. 1A shows a system including a device with a short-range wireless communication module for device diagnostics. [Figure 1B] FIG. 1B illustrates non-volatile storage maintained on the near field communication module for device diagnostics. [Figure 2A] FIG. 2A shows an aerosol generating device equipped with a short-range wireless communication module for device diagnostics. [Figure 2B] FIG. 2B shows an aerosol generating device equipped with a short-range wireless communication module for device diagnostics. [Diagram 3] FIG. 3 shows a charging device equipped with a short-range wireless communication module for device diagnostics. [Figure 4] FIG. 4 shows a graphical user interface for device diagnostics. [Diagram 5] FIG. 5 shows a flow chart of a method for diagnosing an apparatus. [Figure 6] FIG. 6 shows a flow chart of a method for obtaining diagnostic data from a device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0023] FIG. 1A illustrates a system including an apparatus 100 and an external device 140 configured to read an error log stored in a near-field communication module 110 of the apparatus 100. The apparatus 100 may be an aerosol generating device or a charging device associated with the aerosol generating device, as described in more detail below. The apparatus 100 is controlled by a control unit 120. The apparatus 100 includes a communication module 130, the control unit 120, and the near-field communication module 110. The control unit 120 may be configured to receive an indication of an error occurrence. The control unit 120 may be configured to monitor components of the apparatus 100 for a number of error conditions. In response to receiving an indication of the error occurrence, the control unit 120 may receive or generate data associated with the error occurrence. In FIG. 1A, arrows indicate data flow of data related to the error condition.

[0024] For example, an error occurrence may be the replacement of a battery in the device 100. An indication of an error occurrence may indicate the insertion of an improper battery having battery characteristics that carry a risk of malfunction of the device 100. For example, an improper battery may have an incorrect voltage, an incorrect capacity, or an incorrect discharge curve. Another error occurrence may be associated with the replacement of a coil used to generate an aerosol from an aerosol-generating article. Replacing a coil may also pose a risk to the safety of operation of the aerosol generating device. Thus, the control unit 120 may receive an indication that the coil has been replaced.

[0025] Upon detection of an error occurrence, the control unit 120 is configured to update the error data log 118 stored in the non-volatile memory 116 of the near field communication module 110 by storing data related to the occurred error in 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 entries are kept and older data entries are overwritten by new error data entries. The configuration of the data error log 118 is explained in more detail below. The non-volatile memory 116 may further store dynamic data related to improving the user experience by logging on to a product website or by 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 the error data entry associated with the indicated error occurrence in the error data log may further specifically include the control unit 120 communicating with the near field communication controller 112, for example employing a communication protocol I2C. The near field communication controller 112 may be configured to receive the error data entry from the control unit 120 and write the error data entry to the error data log 118. Specifically, the control unit 120 instructs the near field communication controller 112 to write the error data entry to a specific address in the non-volatile memory 116.

[0027] Thus, the control unit 120 dynamically updates the content of the data stored in the short-range wireless communication module 110. Thus, communication between the control unit 120 and the short-range wireless communication controller 112 allows read and write access to the non-volatile memory 116 of the control unit 120. The short-range wireless communication module 110 comprises an antenna 114 configured to be read by the external device 140, for example, according to a short-range wireless communication protocol or other radio frequency identification technology. The short-range wireless communication protocol or other radio frequency identification technology includes the short-range wireless communication module being powered by the external device 140. In particular, the power provided to the short-range wireless communication module 110 from the external device 140 allows communication between the short-range wireless communication module 110 and the external device 140 without the short-range wireless communication module being connected to a power source of the device 100. In particular, communication between the short-range wireless communication module 110 and the external device 140 does not involve the control unit 120 or a communication port, such as a USB port, which is easily damaged. Thus, 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, a smartphone, a computer laptop, a table computer or a personal digital assistant. The external device 140 includes a near field communication reader circuit 144, a memory 142 storing software instructions 143, a communication module 146, and a processor 148. The external device 140 executing the software instructions 143 with 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 a range that allows 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 uniform resource locators of websites and data related to Bluetooth Low Energy pairing.

[0029] The control unit 120 may send a request to the near field communication controller 112 as to whether an external device, such as the device 140, is currently reading the non-volatile memory 116. If the near field 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 communication controller 112 to update the error data log 118 with new error data entries to avoid causing data inconsistencies.

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

[0031] FIG. 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, 117c. The format of the error data log 118 may be different from the format of the structured data records 117a, 117b, 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 an external viewer cannot understand the meaning or purpose of the data. To further enhance information security, the error data log 118 may be encrypted. In particular, the raw data is provided to a dedicated application on an external device without prior processing, so that the dedicated application may be configured to decode the error data log according to a predefined custom structure. The format of the structured data records 117a, 117b, 117c may be a near field communication data exchange format record.

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

[0033] The error data log 118 may include an index of the error data entry that corresponds to the sequence number of the recorded error. The first error recorded receives an index of 1.

[0034] The error data log 118 may further be used to store the error type, the product code of the device 100, which is usually part of the device's serial code. The product code identifies what kind of device 100 is, such as a charger or a holder. The error data log 118 may also indicate a unique device identifier. Thus, two different holder devices will 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 the recorded error was detected, such as, for example, the date the battery was replaced in the device 100. The date the recorded error was detected may correspond to the recorded date and time when the control unit 120 received an indication that an error occurred.

[0036] Thus, the error data log 118 may contain comprehensive information regarding error occurrences to enable reliable device diagnosis.

[0037] In particular, in the example of Table 1, the size of the memory dedicated to area 2 for error data log 118 is 256 bytes, so that error data log 118 allows for the storage of 16 error data entries.

[0038] The list of records 117 is described in more detail below. When transferred to the external device 140, the list of records 117 may configure the external device to perform a particular action. The list of records 117 may include NDEF records containing website URLs that may be used by the external device 140 to navigate to a specified website to enhance the user experience. The list of records 117 may further include NDEF records containing configuration data for Bluetooth Low Energy pairing that may be used to establish Bluetooth communication between the device 100 and the external device 140. The list of records 117 may also include NDEF records configured to contain identifying information for the tobacco product, such as a coding string.

[0039] The list of records 117 includes at least two records arranged in the list.

[0040] The list of records 117 corresponds to a message that includes a list of three records: a first record 117a, a second record 117b, and a third record 117c. At least the first record 117a and the second record 117b are each different record types. Thus, at least the first record 117a and the second record 117b are each associated with a different action to be 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 a serial number of the device 100. The identification number may be used, for example, during the manufacture of the device or during other processes that require identifying the device.

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

[0043] Because the software instructions 143 automatically perform 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 performed by the software instructions 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 performed by the external device 140.

[0044] For example, FIG. 1B shows that the first record 117a is first in 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, it should be appreciated that the records 117a, 117b, and 117c may be arranged in any order. In particular, as described in more detail below, the order of the records in the list is based at least in part on the detection of a predetermined state of the device 100. Thus, the actions automatically performed by the external device 140 depend at least in part on the state of the device 100.

[0045] Thus, in response to receiving the message 117, the application and / or operating system software 143 installed on the external device 140 executes the record that is first in the list of records (i.e., at the top of the list). The external device 140 then executes the action associated with the executed record. Thus, as shown in FIG. 1B, when the first record 117a is first in 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 automatically executed. When the second record 117b is first in 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 automatically executed.

[0046] The short-range wireless communication module 110 is configured such that the content written 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. Thus, 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, a first action associated with the first record in the list is executed by the external device 140. A second time, the message 117 stored by the short-range wireless communication module may be overwritten such that the list of records is in a second order. When the list of records is in the second order, a second action associated with the first record in the list and different from the first action is executed by the external device 140.

[0047] More specifically, the control unit 120 is configured to configure the list of records in the message 117 to define an 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 predefined state of the device 100. The order of the records in the list is based on the particular predefined state detected. For example, in response to detecting a first predefined state of the device 100, the control unit 120 configures the list such that the first record 117a is first in the list, i.e., the first record 117a is at the top of the list. Then, when the control unit 120 detects a second predefined state of the device, the control unit 120 configures the list such that the second record 117b is first in 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, the message 117 including the configured list of records is stored in the short-range wireless communication module 110, thereby dynamically overwriting the message 117 previously stored in the short-range wireless communication module 110.

[0048] The first predefined state may be an advertising state. In the advertising state, the device 100 is in a mode in which an external device 140, or any other suitable device, can communicatively couple with the device 100. For example, when the device 100 is in the advertising state, the communication module 130 broadcasts, via the communication module 146 of the external device 140, an advertising packet that the external device 140 can communicatively couple with the device 100. The device 100 enters the advertising state when the communication module 130 is turned on or otherwise activated. The 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 state of the device 100, the control unit 120 configures the list such that the first record 117a is at the top of the list. The first record 117a may be a general-purpose Internet mail extended media type. If the first record 117a is a general-purpose Internet mail extended media type, the first record 117a includes data that enables the external device 140 to communicatively couple with the device 100 when the external device 140 executes the first record 117a. For example, the first record 117a may include a Bluetooth address or a Bluetooth Low Energy address.

[0050] Thus, 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 first in the list of records, so that the external device 140 executes the first record 117a and communicatively couples (pairs) with the device 100.

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

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

[0053] When the control unit 120 detects the communicatively coupled or off state of the device 100, the control unit 120 configures the list of records such that the second record 117b is at the top of the list. The second record 117b may be of a uniform resource identifier type. The second record 117b may include 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 include a uniform resource locator.

[0054] Thus, when the distance between the external device 140 and the short-range wireless communication module 110 falls below the threshold distance, the short-range wireless communication module 110 sends a message 117 to the external device 140. The message 117 is configured such that the second record 117b is first in the list of records, so that 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 a website associated with the uniform resource locator included in the second record 117b. Alternatively, or additionally, another application software may be launched as a result of executing the second record 117b.

[0055] A website or application launched in response to execution of the second record 117b may enable a user to register the device 100. For example, the uniform resource locator 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 initiate an unlocking of the device 100 such that the device 100 can be operated by the user. For example, when the device 100 is shipped after manufacturing, the device 100 may be in a locked state, meaning that it cannot be operated by the user. When the device 100 receives the registration confirmation message, the control unit 120 configures the device 100 to be operated by the 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 erroneous data entries before storing them in an erroneous data log on the near field communication module 110 .

[0057] In another embodiment, the control unit 120 may filter error occurrences on the device 100 and limit the number of error data entries stored in the error data log 118 taking into account the limited size of the non-volatile storage device 116.

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

[0059] 2, the aerosol-generating device 200A is configured to receive an aerosol-generating article 220. Specifically, the aerosol-generating device 200A comprises a cavity 210 for receiving the aerosol-generating article 220. The aerosol-generating article 220 may comprise an aerosol-forming substrate. The aerosol-forming substrate of the aerosol-generating article 220 may be a solid, such as a tobacco stick. The aerosol-generating device 200A further comprises a heating element 230. The heating element 230 is configured to heat the aerosol-forming substrate to form an aerosol.

[0060] The aerosol generation device 200B is configured to receive the cartridge 280. In particular, the aerosol generation device 200B comprises a cavity 270 for receiving the cartridge 280. The cartridge 280 may include an aerosol-forming substrate. The aerosol-forming substrate of the cartridge 280 may be a liquid. The aerosol generation device 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, the aerosol generating device 200A and the aerosol generating device 200B each include a power source configured to provide power to the respective heating elements 230 and 290. The power source preferably includes a power source such as the power source 240. The power source 240 is preferably a battery, such as a lithium ion battery. Alternatively, the power source 240 may be another form of charge storage device, such as a capacitor. The power source 240 may require recharging. For example, the power source 240 may have a capacity sufficient to allow continuous generation of aerosol for approximately six minutes, or a multiple of six minutes. In another example, the power source 240 may have a capacity sufficient to allow a predetermined number of puffs, or discontinuous activation of the heater assembly. The aerosol generating device 200A and the aerosol generating device 200B each may include a power contact 250 for recharging the power source 240. The power source 240 of the aerosol generating device 200A, 200B may be recharged using a charging device, such as the charging device 300 shown in FIG. 3.

[0062] The power supply 240 may comprise control electronics. The control electronics may comprise a microcontroller. The microcontroller is preferably a programmable microcontroller. The electrical circuitry may include further electronic components. The electrical circuitry may be configured to regulate the supply of power to the heater assembly. Power may be supplied to the heater assembly continuously after activation of the system, or may be supplied intermittently (e.g., between puffs). Power may be supplied to the heater assembly in the form of current pulses.

[0063] In some embodiments, the aerosol generating devices 200A, 200B include a near field communication module 110, as shown in dashed lines. In these embodiments, the aerosol generating devices 200A, 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 the occurrence of an error in the aerosol generating devices 200A, 200B, as described above with reference to Figure 1A, and to update an error data log maintained in non-volatile memory on the near field communication module 110.

[0064] In other embodiments, the aerosol generating devices 200A, 200B do not include a near field communication module, whereas the charging device 300 associated with the aerosol generating devices 200A, 200B includes a near field communication module 110 that stores error data inputs from both the aerosol generating devices 200A, 200B and the charging device 300. The charging device 300 is described in more detail below with reference to FIG. 3. In these embodiments, the aerosol generating devices 200A, 200B include a memory 280, which may be a 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 generating devices 200A, 200B and 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 generating devices 200A, 200B to the charging device 300 when the aerosol generating devices 200A, 200B are inserted into the charging device 300. When used regularly, the aerosol generating devices 200A, 200B are frequently recharged in the charging device 300. Therefore, obtaining error data input from the aerosol generating devices 200A, 200B to the charging device 300 allows reliable diagnostic information to be collected.

[0065] In yet another embodiment, both the aerosol generating device 200A, 200B and the associated charging device 300 include a short-range wireless communication module 110. In such an embodiment, the aerosol generating device 200A, 200B does not include a memory 280, but stores error data input in the short-range wireless communication module 110 as described above. When the aerosol generating device 200A, 200B is inserted into the charging device 300, the error data input stored in the short-range wireless communication module 110 on the aerosol generating device 200A, 200B may be retrieved by the charging device 300. Thus, both the aerosol generating device 200A, 200B and the associated charging device 300 provide a fail-safe error log.

[0066] 3 shows a charging device 300 including the near field communication module 110 described above with reference to FIG. 1A. The charging device 300 comprises a cavity 310 configured to receive an aerosol generating device, such as aerosol generating device 200A and aerosol generating device 200B. Within the cavity 310, there may be power contacts 320 configured to contact corresponding power contacts 250 of the aerosol generating device. Specifically, when the aerosol generating device 200A or the aerosol generating device 200B is received within the cavity 310, the power contacts 250 contact the power contacts 320 such that the charging device 300 can charge the rechargeable power source 240 of the aerosol generating device 200A or the aerosol generating device 200B.

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

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

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

[0070] After receiving the error data input from the aerosol generating device 200A, 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 the non-volatile memory 116, together with error data inputs previously received from other aerosol generating devices and error data inputs related to the occurrence of an error in the charging device 300 itself. In an embodiment, only error data inputs that are not currently stored on the near-field wireless communication module 110 are written to the error data log 116, saving storage space. The errors obtained from the received aerosol generating device 200 may be associated with the product code and serial number of the specific aerosol generating device 200A, 200B, so that when the charging device 300 receives a different aerosol generating device, an error can be traced back to the specific aerosol generating device 200A, 200B where the error occurred. Thus, the charging device 300 collects all errors from the charging device 300 itself and from the aerosol generating devices inserted into the charging device 300.

[0071] The present disclosure further describes a user interface for recovering an error from a near field communication module of an aerosol generating device or a charging device associated with the aerosol generating device. Figure 4 shows user interfaces 410 and 420 provided on an external device, such as external device 140 discussed with reference to Figure 1A. User interface 410 displays instructions 415 instructing a user to move the external device closer to the device, such as an aerosol generating device or a charging device, by tapping a near field communication reader to an area of ​​the device, as shown.

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

[0073] The user interface 420 further displays a list 426 of holder errors associated with errors of the aerosol generating devices 200A and 200B that have been obtained from the aerosol generating devices 200A and 200B by the charging device 300, as described above. The list 426 may be sorted by grouping the errors according to the serial numbers of the aerosol generating devices 200A and 200B in which a particular error occurred.

[0074] Figure 5 shows a flow chart of a method 500 for maintaining error data on an apparatus, such as apparatus 200A, 200B described above with reference to Figures 2A and 2B, or apparatus 300 described above with reference to Figure 3. The method 500 includes a step 510 of monitoring the apparatus for the occurrence of errors. For example, monitoring the apparatus may include monitoring for a number of predefined error conditions.

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

[0076] When the method 500 is implemented by the charging device 300 described above with reference to FIG. 3, the method 500 may optionally include step 530 of receiving an associated aerosol generating device for charging. In response to step 530, the charging device may retrieve, in step 540, an error data log associated with the occurrence of an error on the aerosol generating device. The error data log of the aerosol generating device may be stored in the volatile storage device 280 as described above with reference to FIGS. 2A and 2B, or may be retrieved 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 retrieved error data log may be combined with an error data log maintained in a non-volatile memory of the near-field wireless communication module on the charging device.

[0077] Method 500 may include a step 550 of transmitting the error data log via near field communication to an external device in the vicinity of the aerosol generating device or the charging device, allowing the external device to obtain the error data log even if the device stops functioning after the last update of the non-volatile memory.

[0078] FIG. 6 shows a flowchart of a method 600 for recovering error data from an aerosol generating device or a charging device associated with the aerosol generating device, such as by using an external device 140 that includes a near field communication reader.

[0079] The method 600 includes a step 610 of displaying a prompt on a user interface of the external device to move the external device closer to the device, such as by displaying instructions 415 on the user interface 410. The application may then detect the presence of a near field communication module of the device.

[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] The application decodes the error data input at step 630. Optionally, step 630 may include decoding the error data input, as described in more detail above.

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

[0083] Some or all of the method steps described above with respect to Figures 5 and 6 may be computer-implemented in that they are executed by (or used by) a processor, a microprocessor, an electronic circuit, or a processing circuit. For example, the implementation may be carried out using a non-transitory storage medium, such as a computer-readable storage medium. Such computer-readable media may be any available medium that can be accessed by a general-purpose or special-purpose computer system.

[0084] Generally, the embodiments described herein can be implemented as a computer program product having program code or computer-executable instructions that are 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) includes and stores a computer program or computer executable instructions for performing one of the methods described herein when executed by a processor. In a further embodiment, an apparatus comprises one or more processors and the above-mentioned storage medium.

[0086] In a further embodiment, the apparatus comprises processing circuitry means, e.g. a processor in communication with the memory, which means is configured or adapted to perform one of the methods described herein.

[0087] A further embodiment comprises a computer having installed thereon the computer program or instructions for performing one of the methods described herein.

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

[0089] For purposes of this specification and the appended claims, unless otherwise indicated, all numbers expressing amounts, quantities, percentages, and the like are to be understood in all instances as being modified by the term "about." Also, all ranges include the maximum and minimum points disclosed, as well as any intermediate ranges thereof, which may or may not be specifically recited 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, comprising displaying error data input from the error data log on the user interface.

Images