Device identification method

By enabling devices to operate as both master and slave simultaneously, Bluetooth Low Energy protocols facilitate efficient mesh networking and device identification, enhancing communication flexibility and power management in aerosol delivery systems.

JP2024161367AInactive Publication Date: 2024-11-19NICOVENTURES TRADING LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024113879
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2017-12-29
Filing Date
2024-07-17
Publication Date
2024-11-19
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Existing Bluetooth and Bluetooth Low Energy communication protocols limit devices to a single master or slave role, restricting flexibility and efficiency in wireless communication networks, particularly in mesh-like interactions among aerosol delivery devices.

Method used

Devices are configured to operate in both master and slave roles simultaneously through time-sharing, utilizing Bluetooth Low Energy protocols to establish a mesh network without a central node, enabling flexible and efficient data exchange among aerosol delivery devices.

Benefits of technology

This approach allows for high-speed data transmission and efficient power management in mesh networks, supporting seamless communication and identification of aerosol delivery devices using physical characteristics for user interface adjustments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024161367000001_ABST
    Figure 2024161367000001_ABST
Patent Text Reader

Abstract

To provide a method for exchanging information between an aerosol supply device and a portable electron device, and provide the portable electron device.SOLUTION: A method includes a step of receiving, via a radio communication interface for supporting a paired interaction, a data packet from an aerosol supply device via a radio communication network. The data packet contains information relating to at least one physical characteristic of the aerosol supply device. The method also includes the steps of: determining an identity of the aerosol supply device on the basis at least partially of one physical characteristic of the aerosol supply device; and changing an aspect of a user interface on the basis of the determined identity of the aerosol supply device.SELECTED DRAWING: Figure 15
Need to check novelty before this filing date? Find Prior Art

Description

Field and Background

[0001]

[0001] The present disclosure relates to methods and portable electronic devices.

[0002]

[0002] In conventional wireless communication schemes such as Bluetooth and Bluetooth Low Energy (also known as Bluetooth Smart Technology), individual devices can act as nodes that play the role of master or slave in a particular communication relationship. Thus, each node assumes either the role of master or the role of slave. Thus, in a communication pair, one node acts as a master and the other as a slave. In the context of Bluetooth Low Energy, the master is sometimes called a central and the slave is sometimes called a peripheral. One master (or central) node can be a master to several slaves (the exact number is often limited by the implementation of a particular chipset), and a node can register as a slave (or peripheral) to multiple masters, but can only act as a slave to one master at a time.

[0003]

[0003] Bluetooth and Bluetooth Low Energy operate fundamentally differently from other low-rate wireless personal area networks (LR-WPANs) such as Zigbee® and Thread®, both of which are based on the IEEE 802.15.4 wireless protocol.

[0004]

[0004] International Publication No. 2017 / 020188 and U.S. Patent Application Publication No. 2014 / 0107815 describe examples of exchanging information between an aerosol delivery device and another electronic device.

[0005]

[0005] Some particular aspects and embodiments are set out in the accompanying claims.

[0006]

[0006] According to a first aspect, a method is provided that includes the steps of receiving a data packet from an aerosol delivery device over a wireless communication network via a wireless communication interface capable of supporting paired interaction, the data packet including information regarding at least one physical characteristic of the aerosol delivery device; determining an identity of the aerosol delivery device based at least in part on the at least one physical characteristic of the aerosol delivery device; and modifying an aspect of a user interface based on the determined identity of the aerosol delivery device.

[0007]

[0007] According to another aspect, a portable electronic device can be provided that includes at least one processor, a display, a wireless communication interface capable of supporting paired interaction, and a memory containing instructions that, when executed by the at least one processor, cause the at least one processor to receive a data packet from an aerosol delivery device via the Bluetooth low energy communication interface, the data packet including information regarding at least one physical characteristic of the aerosol delivery device, determine an identity of the aerosol delivery device based at least in part on the at least one physical characteristic of the aerosol delivery device, and modify an aspect of a user interface displayed on the display so as to be changed based on the determined identity of the aerosol delivery device. [Brief description of the drawings]

[0008]

[0008] Embodiments of the present teachings will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0009] [Figure 1]

[0009] FIG. 1 is a schematic diagram of an advertising protocol.

[0010] [Diagram 2] FIG. 2 is a schematic diagram of an exemplary device environment.

[0011] [Diagram 3] FIG. 3 is a schematic diagram illustrating the functional components of an aerosol delivery device.

[0012] [Figure 4] FIG. 4 is a schematic diagram of a protocol stack.

[0013] [Diagram 5] FIG. 5 is a schematic diagram of scan response timing.

[0014] [Figure 6] FIG. 6 is a diagram illustrating mode scheduling.

[0015] [Figure 7] FIG. 7 is a schematic diagram of a mesh of nodes.

[0016] [Figure 8] FIG. 8 is a schematic diagram of a mesh of nodes.

[0017] [Figure 9] FIG. 9 is a schematic diagram of an exemplary BLE advertising packet.

[0018] [Figure 10]FIG. 10 is a schematic diagram of an exemplary BLE advertising packet PDU.

[0019] [Figure 11] FIG. 11 is a schematic diagram of functional components of a portable electronic device.

[0020] [Figure 12] FIG. 12 is a schematic diagram of a user interface of a display of a portable electronic device.

[0021] [Figure 13] FIG. 13 is a schematic diagram of a user interface of a display of a portable electronic device.

[0022] [Figure 14] FIG. 14 is a schematic diagram of a user interface of a display of a portable electronic device.

[0023] [Figure 15] FIG. 15 is an illustration of a method for a portable electronic device.

[0024] [Figure 16] FIG. 16 is an illustration of a further method for a portable electronic device. Detailed Description

[0025]

[0025] While the methods described herein are susceptible to various modifications and alternative forms, specific embodiments are shown by way of example in the drawings and will be described in detail herein. It should be understood, however, that the drawings and detailed description are not intended to limit the scope of the present invention to the particular forms disclosed, but on the contrary, the scope of the present invention is intended to cover all modifications, equivalents, and alternatives falling within the spirit and scope as defined by the appended claims.

[0026]

[0026] The present disclosure relates to modified forms of wireless communication behavior. According to the present teachings, a device can be configured to use a Bluetooth or Bluetooth-like communication protocol and can operate as both a master / central and a slave / peripheral in different communication relationships simultaneously on a time-division basis, in a manner that may be transparent to other devices using the communication protocol to communicate with the device.

[0027]

[0027] In some examples, these devices may be aerosol delivery devices such as so-called "E-cigarettes", sometimes also known as Electronic Nicotine Delivery devices (END) devices, equipped with electronics that allow them to communicate with other communication devices. As used herein, the term "aerosol delivery device" refers to both devices that contain aerosol source material (e.g., the device portion that contains the aerosol source material and the disposable cartomizer portion) and / or devices that do not contain aerosol source material (e.g., just the device portion of the previous example).

[0028] In this example, the devices use Bluetooth Low Energy ("BTLE"), but other Bluetooth or Bluetooth-like protocols can utilize the present teachings. Bluetooth is a wireless technology standard for short-range communication between appropriately enabled devices. BTLE is a modification of the original Bluetooth system designed to consume less power during use for extended battery life and / or small battery applications. Both Bluetooth and BTLE operate in the UHF wireless industrial, scientific and medical (ISM) band between 2.4 and 2.485 GHz and are designed to create so-called wireless personal area networks (PANs) for interconnecting devices over short distances. BTLE uses a modified version of the Bluetooth stack for communication, and as a result, BTLE devices are not directly compatible with traditional Bluetooth devices unless one of the devices implements both protocols. Both Bluetooth and BTLE standards are maintained by the Bluetooth Special Interest Group (SIG). This disclosure is provided in the context of an implementation of BTLE using the portions of the Bluetooth v4 specification that are relevant to BTLE. However, those skilled in the art will appreciate that the present teachings may be applied to other Bluetooth schemes, such as the so-called Classic Bluetooth definition, which is also described in the Bluetooth v4 specification, and will further appreciate that the present teachings may be applied to technologies that do not comply with the entire Bluetooth specification, but which nevertheless behave in a Bluetooth-like manner.

[0029]

[0029] For example, non-Bluetooth systems that also use an advertising configuration based on the Bluetooth Low Energy Generic Access Profile (GAP) and thus have substantially the advertising structure as shown in Figure 1 can utilize the technology of the present teachings. Figure 1 shows an advertising structure whereby a peripheral (or slave or remote or secondary) device advertises its availability as a peripheral (or slave or remote or secondary) device during advertising periods separated by an advertising interval. This advertisement may include data for transmission, or may indicate that there is data for transmission, or may have no data reference at all. To receive advertisements, a central (or primary or control) device scans for advertisements during a scan window. Multiple scan windows are separated by a scan interval. The relative duration of the scan interval and advertisement interval is changed by deciding to keep the interval constant for one device type and vary the other, or by deciding to vary both, which can be set by a standard or set of rules for implementing the advertising protocol. By varying the scan interval and advertisement interval relative to each other in this way, even if the first advertisement period does not overlap with the first scan window, after several advertisement intervals and scan intervals, there will be an advertisement period that overlaps with the scan window, so that a connection can be initiated between the central device and the peripheral device.

[0030]

[0030] A first example of a device environment 1 in which the present teachings can be utilized is shown in FIG. 2. In this example, there are several aerosol delivery devices 2a-2e in the device environment 1. The various aerosol delivery devices 2 are interconnected via wireless links indicated by dotted lines 4. However, not all aerosol delivery devices 2 are directly interconnected with each other aerosol delivery device. Rather, the aerosol delivery devices 2 are interconnected in a mesh-like pattern with a scatternet data flow. Thus, it will be seen that if a message is passed from aerosol delivery device 2a to aerosol delivery device 2d, the message is passed through aerosol delivery devices 2b and 2c (and optionally 2e) to reach aerosol delivery device 2d. From some perspectives, it may be considered appropriate to describe these interactions as piconets instead of using a description of meshing or mesh-like interactions. For ease of reading, the term mesh is used throughout this specification.

[0031]

[0031] To achieve such a mesh-type communication structure, a device consistent with the present teachings can assume two or more personas and therefore can belong to two or more BTLE communication relationships, and furthermore, a device can operate as a central or peripheral in one BTLE communication relationship and as a peripheral in another BTLE communication relationship. To manage the concurrency of these different personas, a device of the present teachings can operate to switch between two personas such that it adopts only one persona at a time. Switching between personas occurs frequently enough that each communication relationship is maintained without the devices forming the communication relationships concluding that the device has become unavailable and closing those relationships.

[0032]

[0032] Switching between personas in a given device occurs on a time scale that matches the requirements of a particular application for that device. As shown with respect to FIG. 1 above, there is a random element to this switching. However, the time range within which this random element can operate is set according to the requirements of the application. For example, to provide high speed data transmission through a mesh of devices, persona switching may be performed relatively frequently. For example, in an implementation based on interaction by devices associated with users in transient locations (such as in the case of END devices in social settings), each device may be configured to switch roles every few seconds. On the other hand, for greater power efficiency, and where data transmission speed through the mesh is less important, relatively infrequent persona switching may be used, perhaps making it appropriate to switch roles only once or twice an hour. Also, the relative duration of the peripheral and central roles may be altered according to factors that apply to the implementation environment. Thus, while the peripheral persona is active, the device sends data as part of advertising packets, and while the central persona is active, the device listens for other devices to advertise data packets.

[0033]

[0033] Furthermore, a device according to the present teachings can have multiple central personas that can be used to communicate in different meshes or to increase the total number of peripherals with which the device can maintain multiple associations at once beyond the limitations imposed by the particular Bluetooth chipset being used. These multiple central personas can be implemented using the persona switching scheme outlined above or by implementing multiple BTLE MCUs.

[0034]

[0034] By using such techniques, for example, the interconnections between the aerosol delivery devices 2 can be made in a first BTLE relationship in which the aerosol delivery device 2a acts as a central and the aerosol delivery device 2b acts as a peripheral. The aerosol delivery device 2b can also act as a central in a second BTLE relationship in which the aerosol delivery device 2c acts as a peripheral. The aerosol delivery device 2c can then be a central in a third BTLE relationship that includes the aerosol delivery devices 2d and 2e as peripherals. Furthermore, the aerosol delivery device 2d can also be a central in a fourth BTLE relationship that includes the aerosol delivery device 2e as a peripheral. As will be appreciated, other orderings in which the aerosol delivery devices act as centrals and peripherals in the various possible aerosol delivery device relationships can be implemented. 1 may alternatively be achieved by having aerosol delivery device 2b act as a central in a BTLE relationship in which aerosol delivery devices 2a and 2c are peripheral, aerosol delivery device 2d act as a central in a relationship in which aerosol delivery device 2c is peripheral, and aerosol delivery device 2e act as a central in a relationship in which aerosol delivery devices 2c and 2d are peripheral. As will be seen from the discussion below, the arrangement of relationships to form a mesh may be determined on an ad-hoc basis depending on which aerosol delivery device becomes the central as a result of the relationship establishment process.

[0035]

[0035] The mesh scheme described in this disclosure allows small data packets or tokens to be exchanged between aerosol delivery devices without the need to establish a full BTLE binding relationship between the aerosol delivery devices. Thus, such tokens may be flooded into a mesh of any two or more aerosol delivery devices based on a transient or non-permanent aerosol delivery device-to-aerosol delivery device relationship, where the peripheral-to-central relationship lasts only long enough to send and receive the token. This scheme does not prevent some or all of the aerosol delivery devices in the mesh from establishing a binding relationship (also known as pairing). Such a binding-based scheme may be used, for example, in situations where a larger amount of data needs to be transmitted between aerosol delivery devices in a mesh than can be accommodated using tokens.

[0036]

[0036] Also, as shown in Figure 2, an additional device 6 may be provided. The device 6 does not need to have knowledge or capability regarding the meshable interconnectivity of the aerosol delivery devices 2, but instead executes a communication protocol in a conventional manner. For example, the device 6 may implement a conventional BTLE interface and thus establish a connection 6 with one of the meshable aerosol delivery devices 2, such that the device 6 acts as a central and the aerosol delivery device 2 acts as a peripheral. Alternatively, the device may utilize the same meshable interconnectivity to communicate with one or more of the aerosol delivery devices 2.

[0037]

[0037] It can thus be seen that the scheme of the present teachings makes it possible to establish a Bluetooth or BTLE based mesh without a control device providing a core node for a star topology. The mesh can interact with non-mesh devices, but this interaction can be continuous or intermittent, and the non-mesh devices need not have any role in establishing, controlling, or configuring the mesh.

[0038]

[0038] Thus, by establishing such a mesh network, various aerosol delivery devices 2 can communicate with each other and pass information to other devices within range using existing communication protocols such as BTLE. However, as will be seen from the present discussion, the devices use a modified version of a Bluetooth hardware implementation with Generic Attribute Profile (GATT) Notification to achieve this ad-hoc meshable behavior. As will be seen from the present teachings, this modification can be achieved by performing a modified hardware, firmware, or software implementation of the protocol, for example by implementing a controller circuit that conforms in many respects to the standard communication protocol, but also includes additional functionality provided, for example, by using scripts to achieve device-to-device interaction as described herein. The additional functionality can be introduced using modified hardware, which requires the use of non-standard hardware, but which allows both modes to be provided in a full-time manner without the need to share personas in a time-shared manner. The controller circuit may be a hardware circuit having functionality provided by its configuration, such as an application specific integrated circuit (ASIC), or may be a programmable microprocessor (μP) or microcontroller (MCU) operating under firmware and / or software control.

[0039]

[0039] Figure 3 shows a schematic of the functional components of each aerosol delivery device 2. Each aerosol delivery device 2 has an antenna 10 for transmitting and receiving BTLE signals. The antenna 10 is connected to a wireless communication interface 12, e.g., a BTLE control circuit 12, such as a BTLE MCU. The wireless communication interface 12 receives data for transmission from and provides received data to a device core function processor 14, which operates, e.g., with a memory 16 and / or I / O elements 18 to perform the core computational functions of the aerosol delivery device 2. In Figure 3, the functional components of the aerosol delivery device 2 are shown interacting on a direct link basis, but it will be understood that since Figure 3 is schematic in nature, this description also includes alternative arrangements of the functional components on an interconnection basis, e.g., by a bus. It will also be understood that one or more of the illustrated functional components may be provided by a single physical component, and that one functional component may be provided by multiple physical components.

[0040]

[0040] With respect to the functional components related to the core computing function of the aerosol delivery device 2, it will be understood that the nature and use of these components may vary depending on the nature of the device itself. In the example of the aerosol delivery device 2, the core computing function may include the exchange of information tokens between aerosol delivery devices, monitoring and reporting of device charge levels and / or nicotine fluid levels, lost and found interactions, and usage records. It will also be understood that the core computing function may therefore be different from the core functionality of the device as perceived by the user. For example, in the case of an aerosol delivery device, the core functionality as perceived by the user may be an aerosol generation function for delivering nicotine, and the computing function may be additional, supplemental, or secondary to that core functionality as perceived by the user.

[0041]

[0041] Then, Fig. 4 shows a schematic representation of the protocol structure implemented by the wireless communication interface 12 of each aerosol delivery device 2. The protocol structure shown in Fig. 4 corresponds to a Bluetooth stack, which includes the generic attribute protocol (GATT), the generic access protocol (GAP), the service manager protocol (SM), the low energy attribute protocol (GATT / ATT), the logical link control and adaptation layer (L2CAP) and a link layer. In this example, the link layer operates on a low energy radio frequency (LERF) basis. As shown in Fig. 4, this protocol stack can be conceptually divided between a so-called host layer and a controller layer. The controller part constitutes the lower layers required for physical layer packets and the associated timing. The controller part of the stack can be implemented in the form of an integrated circuit, such as a system-on-a-chip (SoC) package with an integrated Bluetooth radio.

[0042]

[0042] Layer implementations that are relevant to understanding the present teachings include the link layer, L2CAP, GAP, and low energy attribute protocol.

[0043]

[0043] The link layer controller is responsible for low-level communication over the physical interface. It manages the sequence and timing of transmitted and received frames, and communicates with other devices regarding connection parameters and data flow control using the link layer protocol. The link layer controller also processes frames transmitted and received while the device is in advertising or scanner mode. The link layer controller also provides gatekeeping functionality to limit exposure and data exchange with other devices. When filtering is configured, the link layer controller maintains a "whitelist" of allowed devices and ignores all requests for data exchange or advertising information from other devices. In addition to providing security functionality, it can also help manage power consumption. The link layer controller communicates with the upper layers of the stack using a host controller interface (HCI) if the layer implementation is not co-located.

[0044]

[0044] The logical link control and adaptation layer protocol (L2CAP) component provides data services to higher layer protocols such as the security manager protocol and the attribute protocol. The L2CAP component is responsible for protocols that multiplex and split data into packets small enough for the link layer controller, and the reverse demultiplexing and reassembly operations. L2CAP has a back-end interface for GAP, which defines the generic procedures related to the discovery of BTLE devices and the link management aspects of connecting with other BTLE devices. GAP provides an interface for applications to configure and enable different operating modes, such as advertising or scanning, and to initiate, establish, and manage connections with other devices. Thus, GAP is used to control connections and advertising in Bluetooth. GAP controls device visibility and determines how two devices can (or cannot) interact with each other.

[0045]

[0045] The low energy attribute protocol (ATT) is optimized for the small packet sizes used by Bluetooth low energy and allows attribute servers to expose a collection of attributes and associated values ​​to attribute clients. These attributes can be discovered, read, and written by peer devices. GATT provides the framework for using ATT.

[0046]

[0046] As is apparent from the above discussion, the present teachings facilitate mesh-type interaction of multiple devices using an advertising process, enabling the dissemination of information among an unlimited number of devices, for example, for the purpose of disseminating data across distance and time.

[0047]

[0047] In the context of this example, an application running on a device communicating via the mesh structure described herein can request or wait for a specific scan response payload in response to a scan response sent by that device. This approach is used in conventional Bluetooth implementations to send the device name and other identifying details. However, in this approach, the scan response is defined as a 31-byte data packet, also called a token, that is used to share identity information associated with a variable that, when read by an application, triggers a specific response or action. The timing of such a request is shown in Figure 5. As can be seen, the scan response request is sent by the central device during the advertising interval and the scan response data is provided by the peripheral before the next advertising interval begins.

[0048]

[0048] By implementing the schemes of the present teachings, data exchanged over the physical layer is indistinguishable from normal BTLE traffic at that level, and although higher layers are modified to accommodate this mesh-enabled interaction of devices, non-mesh enabled applications can communicate over BTLE with devices consistent with the present teachings.

[0049]

[0049] Also, a device that utilizes only a conventional BTLE stack (such as device 6 shown in FIG. 2 above) can communicate with an aerosol delivery device 2 that uses the meshable scheme of the present teachings. The conventional BTLE device can then receive data from the meshable aerosol delivery device 2 without the BTLE stack in the conventional BTLE device having any knowledge of the mesh-type interactions of the aerosol delivery device 2. The data received by the conventional BTLE device may have been sent from a directly connected aerosol delivery device 2, or from an aerosol delivery device that was previously connected to the directly connected aerosol delivery device 2 via mesh, and the data was stored or cached in the meshable aerosol delivery device 2. The source of such mesh-transmitted data may be another mesh aerosol delivery device 2, or another conventional BTLE device that is connected or was connected to the mesh aerosol delivery device.

[0050]

[0050] Figure 6 shows a schematic of the behavior of each aerosol delivery device 2 in relation to managing its dual persona nature to establish connections as both a central and a peripheral. Because BTLE provides two modes of operation at the presentation layer, one corresponding to each of the roles of central and peripheral, the aerosol delivery device 2 in this example alternates between these two modes, implementing both an advertiser broadcasting to advertise its capabilities as a peripheral, and an observer activity to look for other potential peripheral aerosol delivery devices to which the device can connect as a central. While operating as an observer, the aerosol delivery device can act on the received broadcaster advertisements and establish connections as a central according to normal BTLE behavior, for example as described in the BTLE Generic Access Profile (GAP). While performing the advertiser broadcasting, the aerosol delivery device can establish connections as a peripheral with the observing aerosol delivery devices that respond to become central. As discussed above, this time division between the Central and Peripheral personas continues after the connection between the devices is established, allowing a single device to operate in both modes on a continuous, albeit time multiplexed, basis based on a single BTLE MCU within the device.

[0051]

[0051] Thus, the aerosol delivery device configured to provide meshable interaction in this example employs two modes of operation related to the dual persona nature of the aerosol delivery device, using the standard BTLE Generic Attribute profile (GATT) specification in combination with a modified GAP. As discussed below, the aerosol delivery device alternates between advertising as a peripheral and listening as a central so that it can easily connect with other aerosol delivery devices in both central and peripheral modes. Typically, a device already exhibits a mesh identity in that it may be pre-programmed to use a specific UUID that is tied to the particular device mesh (called a "service" in BTLE terminology) that the device intends to join. For example, all END devices from a particular brand, type, or manufacturer may be programmed to use the same UUID. In this context, to identify the active persona or mode, the aerosol delivery device uses an ID code that uniquely identifies the aerosol delivery device within the mesh. The ID and UUID (effectively a mesh ID or group ID) codes are held in the device's firmware and are inserted into advertising packets along with the data that constitutes the token, and may also be referenced in scan response request and scan response messages as part of the advertising under GAP interactions with and between devices.

[0052]

[0052] While operating as a central, the aerosol delivery device can adopt the states of scanner, initiator, and master, and while operating as a peripheral, the aerosol delivery device can adopt the states of advertiser and slave.

[0053]

[0053] Figure 6 also illustrates the relative advertising and observation times of multiple aerosol delivery devices. The illustrated scheme tends to avoid (but does not necessarily preclude) multiple aerosol delivery devices within range of each other from broadcasting at the same time. In this example, the observation duration is controlled to be in the range of 0.01 ms to 5 s, and the advertising period is a fixed duration that may be in the range of 0.5 s to 10 s. In other examples, the advertising duration may be variable, and the observation duration may fall within a different, overlapping range, or subset of the exemplary ranges given above. Such time offsets can be achieved in several ways, such as by coordination between the aerosol delivery devices, or by each aerosol delivery device making interval length adjustments, such as to provide irregular time intervals between each mode transition. Such interval length adjustments can be done by selecting one of several possible interval lengths for each interval, or by using some form of interval duration random number generator.

[0054]

[0054] When an aerosol delivery device is observing with the intent of establishing a role as a central in a mesh, the aerosol delivery device operates exactly like an aerosol delivery device without meshing capabilities when listening for advertisements from potential peripheral aerosol delivery devices. Thus, an aerosol delivery device operating in this mode can also become a central to conventional BTLE devices without the meshing capabilities of the present teachings.

[0055]

[0055] When an aerosol delivery device is advertising with the intent of establishing a role as a peripheral in a mesh, the aerosol delivery device advertises using a structure based on the BTLE GAP data. However, the BTLE GAP structure is modified to include mesh-specific information that can be recognized by mesh-enabled devices that receive the advertisement. The mesh-specific information can include fields such as: -ID of the advertising aerosol delivery device. The packet sequence number of the packet waiting to be transmitted from the aerosol delivery device. This is used to avoid duplication, depending on the application. This may simply be the packet sequence of packets transmitted from the aerosol delivery device (e.g., if the application only requires that the payload or token from the advertising aerosol delivery device be flooded to multiple other aerosol delivery devices), but may be unique for a given mesh (group ID), time window, and / or other uniqueness scope, according to the requirements of the application. The source aerosol delivery device identifier of the packet with that packet sequence number, to reflect that the token currently being passed may have been sent from a different aerosol delivery device than the aerosol delivery device currently passing it. The destination aerosol delivery device identifier for the packet with that packet sequence number. Depending on the implementation, this may be a single aerosol delivery device (corresponding to some form of routed operation) or "all" aerosol delivery devices (corresponding to a flood type operation). The group ID of the source aerosol delivery device for the packet with that sequence number. This is used to allow multiple mesh networks to coexist in the same physical space (as mentioned above, this group ID typically uses the BTLE UUID, but a different group ID field can be defined and used if desired). The lifetime or expiration time of the packet that contains that sequence number. Payload. Data specific to a particular application - for example, data related to an END device application.

[0056]

[0056] According to the BTLE data processing method, if a given application payload item is too large for a single packet, the payload item is split and distributed into multiple packets and then reassembled at the (each) destination aerosol delivery device. In such applications, binding may be established between the aerosol delivery devices to provide more transmission management for this large amount of data.

[0057]

[0057] Figure 7 shows a schematic of the connectivity pattern between several aerosol delivery devices N1, N2, N3, and N4. In this figure, the aerosol delivery device N1 is out of range of direct communication with the aerosol delivery device N4. The different operation modes of the aerosol delivery devices are represented by the control chip (CC) 22 and mesh chip (MC) 24 of each element of the aerosol delivery devices N1-N4. The control chip represents the aerosol delivery device MCU that operates to communicate with a conventional BTLE device, such as device 6 shown in Figure 2. The mesh chip represents the aerosol delivery device MCU that operates in both central and peripheral modes to communicate through the mesh.

[0058]

[0058] In the example of Figure 7, the aerosol delivery device N1 has a bit set in the advertisement data field indicating that the aerosol delivery device has data to send. Due to the advertising and observation schedules at each aerosol delivery device, the aerosol delivery device N2 becomes the first aerosol delivery device in direct communication range with N1 and listens as a central following the aerosol delivery device N1 with the advertisement data field set. Thus, when the aerosol delivery device N2 is in central mode, it receives the advertising data that N1 was advertising while in peripheral mode. This advertising data received by N2 may be used by N2 in connection with applications running on or otherwise associated with N2. Additionally or alternatively, the aerosol delivery device N2 may cache the advertising data and prepare to send it onward as advertising data at a future opportunity when the aerosol delivery device N2 adopts a peripheral persona. Thereby, advertising data transmitted from N1 can be passed on as advertising data from N2, which is then received by aerosol delivery device N3 when N2 is advertising as a peripheral and N3 is listening as a central. The advertising data transmitted from N1 can then be used and / or passed on by N3, and finally reach N4 in the same manner.

[0059]

[0059] It should be noted that in this embodiment, the advertising data is effectively flooded throughout the mesh. Thus, if N1 happens to be listening as a central at the same time that N2 is advertising as a peripheral, the advertising data will return to N1 and also be passed on through the mesh to N3. In this situation, either the aerosol delivery device N1 or any application running on or associated with N1 may simply discard the returned advertising data. In some embodiments, the aerosol delivery device or application may utilize the returned advertising data in some way, for example, using the time between transmission and reception as some form of random interval generator, or for mesh diagnostics.

[0060]

[0060] As explained above, transmission through the mesh can be in a more structured form, with connections established between the aerosol delivery devices. In such a situation, each pair of aerosol delivery devices interacts through an established connection, and persona switching at each aerosol delivery device allows data received on a connection in which one persona is a member to be transmitted onward using a connection in which the other persona is a member.

[0061]

[0061] Control of whether data is sent to all aerosol delivery devices (flooding) or data is sent only to selected aerosol delivery devices (routing) can be achieved in several ways. If data is to be automatically communicated to all aerosol delivery devices without restriction, this can be a default state set on the aerosol delivery device. If data is to be sent only to aerosol delivery devices that are currently active in the mesh, this can be achieved either as a default behavior setting on the aerosol delivery device, or as an application-specific setting, where the application is aware of the mesh and provides control information to the communication stack to indicate the transmission range of the data. If data is to be sent only to specific aerosol delivery devices, this can be achieved with an application-specific setting, where the application is aware of the mesh and provides control information to the communication stack to indicate the transmission range of the data. This example is configured to operate on a flooding basis, such that data is automatically forwarded to all currently meshed devices.

[0062]

[0062] Figure 8 provides further illustration of the meshing behavior between aerosol delivery devices. In this example, there are a number of aerosol delivery devices N11-N19. The diagram in Figure 8 represents a given snapshot in time, with different ones of these aerosol delivery devices shown as currently adopting different ones of their peripheral and central personas. At the time shown in Figure 8, three aerosol delivery devices are configured to be in central mode, these being aerosol delivery devices N12, N16, and N19, and the remaining aerosol delivery devices are configured to be in peripheral mode. As can be seen from the above discussion, when any given instance of the same aerosol delivery device is present at the same location, the exact number and identity of the aerosol delivery devices that are configured to be in central mode will depend on factors such as the scheduling of its advertising / observation period by each aerosol delivery device, and the relative location of each aerosol delivery device compared to any other aerosol delivery devices already configured as either central or peripheral mode. The exchange of the data token is indicated in the diagram by the presence of a flag that is passed to N12 listening in central mode to receive advertising data from N11, which sends the data token in its advertising data. The token will then be included in advertising data from N12 when N12 adopts a peripheral persona, allowing the token to be passed onwards through the mesh and ultimately reach each aerosol delivery device in the mesh at least once.

[0063]

[0063] As can be seen from the above discussion, a mesh can change dynamically based on changes in the number and location of aerosol delivery devices in the mesh. For example, some aerosol delivery devices may move away from the rest of the mesh, which may result in them losing communication with all aerosol delivery devices in the mesh and leaving the mesh. Similarly, an aerosol delivery device that is inactive or goes into a power-saving non-radio mode may lose communication with other aerosol delivery devices in the mesh and leave the mesh. Furthermore, a new aerosol delivery device that was not previously part of the mesh may join the mesh when it comes within range of an aerosol delivery device in the mesh or is powered on within range of an aerosol delivery device in the mesh. Also, as can be seen from the above discussion of persona switching, an aerosol delivery device that is already in the mesh and operates as a peripheral in the mesh may also operate as a central in the mesh at a different time. In embodiments where a mesh employs binding relationships such that a particular aerosol delivery device has a defined role as central in some bindings and a peripheral role in other bindings, if an aerosol delivery device changes location relative to aerosol delivery devices in the mesh, it may effectively leave the mesh as all established bindings may cease range operation for the new location, and such aerosol delivery device may then resume attempting both observation and advertising until it establishes one or more new binding relationships with other aerosol delivery devices in the mesh with which it is bound.

[0064]

[0064] As will be appreciated by those skilled in the art, Bluetooth and BTLE provide security of inter-node communication binding. This is not true for purely advertising-based transmission of tokens in the form of advertising data, unless such transmission of tokens leads to the establishment of binding relationships. In this example, even if binding relationships are used, the aerosol delivery device can be configured to establish such binding without requiring user input to confirm the trust between different aerosol delivery devices or other devices. Rather, in this example, an aerosol delivery device of a particular type can be configured to pre-trust all other aerosol delivery devices of that particular type. For example, each aerosol delivery device can be configured to trust all other devices that are identified as aerosol delivery devices from a given manufacturer, group of manufacturers, brand, group of brands, model, group of models, or that are identified as complying with a given aerosol delivery device standard or group of standards.

[0065]

[0065] Such patterns of trust can be supplemented with inherent control over the amount of personal data the device is allowed to store / transmit. For example, an aerosol delivery device can be configured by the owner to not retain any information identifying the owner or to prevent sharing of information. This does not prevent the END device from interacting with other END devices to exchange information that can be used for lost / found functions, nor does it prevent the END device from exchanging its own information to enable group interactions between END devices of the same brand or model, for example as discussed below.

[0066]

[0066] In other examples, trust may be a feature that is explicit to the user, and the user may be required to actively accept or request to establish a communication connection with another aerosol delivery device.

[0067]

[0067] For example, when a particular aerosol delivery device or other device is configured by a user to communicate with the user's conventional BTLE device, such as a smartphone, phablet, or tablet device, a trust relationship between the user's meshable device and the conventional BTLE device can be secured to establish a communication coupling in the same manner as other conventional BTLE pairings.

[0068]

[0068] Thus, it will be appreciated that using the techniques of the present teachings, a device can be provided that is capable of mesh-type interaction with other like devices by employing a dual persona structure in which the device can operate on a time-shared basis as both a master (central) and a slave (peripheral) for communicating with other like devices, while also operating as a slave / peripheral to conventional devices that do not have dual persona capability.

[0069]

[0069] This scheme can be used to facilitate device-to-device interaction between a range of devices for a range of purposes. As noted above, examples of devices that may be provided with such device-to-device interaction using the example mesh or piconet topology scheme above include electronic nicotine delivery devices (END devices).

[0070]

[0070] The meshable interconnectivity of the aerosol delivery device 2A with one or more other devices as described above can be considered as a connectionless interaction, with connectionless packets being generated, sent, and received by each device according to the examples described above with reference to Figures 1 to 8.

[0071]

[0071] In this example, the wireless communication interface 12 of the aerosol delivery device 2a is used to generate a connectionless advertising packet that includes information about at least one physical characteristic of the aerosol delivery device 2a. The at least one physical characteristic may include a color of the aerosol delivery device 2a. The at least one physical characteristic may also include other physical characteristics, such as a shape of the aerosol delivery device 2a, a size of the aerosol delivery device 2a, and a type of the aerosol delivery device 2a. For example, the at least one physical characteristic of the aerosol delivery device 2a may include a length, a width, and a thickness of the aerosol delivery device 2a, and / or an indication that the aerosol delivery device 2a is substantially cylindrical, pebbled, ovoid, or another geometric shape.

[0072]

[0072] The color of the aerosol delivery device 2a can be conveyed as a hexadecimal color code, which is either a hexadecimal code that approximates the actual color of the device, or a code that very generally indicates the color characteristics. For example, if the aerosol delivery device 2a is a red device, a general approximation of "red" can be represented by the hexadecimal color code FF0000, while a specific hexadecimal code for the actual color can correspond to the Pantone or other color identifier of the device (as an example, a Pantone 2347U colored device can be represented by the hexadecimal code E74536, or can be approximated to the so-called web-safe color FF3333 to easily represent the color on a display device). In the example of a yellow device, a general approximation of "yellow" can be represented by the hexadecimal color code FFFF00, while a specific hexadecimal code for the actual color corresponding to, for example, Pantone 114C can be represented by the hexadecimal code FBDD40 (or can be approximated to the so-called web-safe color FFCC33 to easily represent the color on a display device). By transporting the color of the aerosol-delivery device 2a as a hexadecimal color code, any color in the RGB color model can be transported in the advertising packet using three bytes. Alternatively, the color of the aerosol-delivery device 2a can be transported using a predefined code. For example, if a particular type of aerosol-delivery device 2a is manufactured in only a finite number of different colors, for example, eight colors, a code is used to transport the color of the device in the range of available colors, such as 001 for red, 010 for yellow, 011 for blue, etc. In this way, only three bits in a single byte of the advertising packet are required to transport the color of the aerosol-delivery device 2a, thereby saving space in the advertising packet.

[0073] In this example, the advertising packet generated by the wireless communication interface 12 of the aerosol delivery device 2a optionally includes additional information about the aerosol delivery device 2a, such as a batch number (batch ID) of the aerosol delivery device 2a, a serial number of the aerosol delivery device 2a, and / or a product identification number (product ID) of the aerosol delivery device 2a. For example, the advertising packet may include a UUID corresponding to the aerosol delivery device 2a.

[0074]

[0074] The wireless communication interface 12 of the aerosol delivery device 2a may be a Bluetooth low energy (BLE) communication interface. Fig. 9 shows a schematic diagram of an exemplary BLE advertising packet 100 with a size of up to 47 bytes. Such an advertising packet is generated by the BLE communication interface 12 of the aerosol delivery device 2a.

[0075]

[0075] The advertising packet 100 shown in Fig. 9 starts with a 1-byte preamble 110 and a 4-byte access address 120 that corresponds to the RF channel number used to transmit the advertising packet 100. Following the preamble 110 and access address 120 portions is a Packet Data Unit (PDU) 130 that can be 2 to 39 bytes in size depending on the advertising type used. The advertising packet 100 then ends with a 3-byte Cyclic Redundancy Check (CRC) 140. The content and format of the preamble 110, access address 120, and CRC 130 portions can be standardized across each advertising packet 100, but the length and content of the PDU 130 may vary for each advertising packet 100. The length of the PDU 130 is typically kept to the minimum necessary to transport the information required to reduce the transmission time of the advertising packet 100.

[0076]

[0076] Figure 10 illustrates a schematic of an exemplary BLE advertising packet 100, e.g., a PDU 130 of the BLE advertising packet 100 illustrated in Figure 9. In this example, the first 16 bytes of the PDU 130 include a 128-bit UUID 132 of the aerosol delivery device 2a. The next two bytes of the PDU 130 include a product ID 134 of the aerosol delivery device 2a. The next three bytes include a hexadecimal color code 136 corresponding to the color of the aerosol delivery device 2a. The remaining bytes 138 are unallocated, but can be used to convey additional information, such as the shape of the aerosol delivery device 2a, the size of the aerosol delivery device 2a, and / or the type of the aerosol delivery device 2a. A batch ID of the aerosol delivery device 2a may be included in place of the product ID 134, or the batch ID may be included in the unallocated portion 138 of the PDU 130. Alternatively, the space for color information may be allocated to a single byte, for example where the color of the aerosol delivery device 2a is conveyed using a predefined code.

[0077]

[0077] The generated advertising packet is then transmitted through the wireless communication network using the wireless communication interface 12 of the aerosol delivery device 2a. For example, if the wireless communication interface 12 is a BLE communication interface, the advertising packet 100 may be in the format shown in Figures 9 and 10. The advertising packet 100 is then received by the device 6 listening for advertising packets in the mesh network as described above.

[0078]

[0078] Figure 11 shows a schematic of the functional components of a portable electronic device 6. The portable electronic device 6 may be a mobile communication device such as a mobile phone or a smartphone, or a portable computing device such as a laptop, a smartwatch, a tablet or a phablet device. Each portable electronic device 6 has an antenna 60 for transmitting and receiving wireless communication signals, such as BLE signals. The antenna 60 is connected to a wireless communication interface 62, e.g. a BLE control circuit 62, such as a BLE MCU, capable of supporting paired interaction. In the context of BLE, paired interaction is understood to mean both pairing and bonding. The wireless communication interface 62 receives data for transmission from a device core function processor 64 and provides received data to the device core function processor 64. The device core function processor 64 operates, for example, together with a memory 66, an I / O element 68 and / or a display 65 to perform the core computational functions of the portable electronic device 6. The display 65 is configured to display a user interface, such as a graphical user interface (GUI), to a user of the portable electronic device 6. The display 65 may be a touch screen display that allows a user to interact with a user interface displayed on the display 65 by touching the display 65 with a finger, a stylus, or other suitable object. Alternatively, the display 65 may be a conventional display screen having a user interface including one or more buttons, switches, or other input elements 68 located on or attached to, or in communication with, the portable electronic device 6 for interaction with the user. For example, the user may interact with the user interface using buttons located on the portable electronic device, a wired pointing device such as a mouse, or a wireless device such as a wireless keyboard, wireless remote control, or smart watch, or by voice or gesture recognition.Although Figure 6 illustrates the functional components of the portable electronic device 6 interacting on a direct link basis, it will be appreciated that as Figure 6 is schematic in nature, the description also includes alternative arrangements of the functional components on an interconnection basis, for example by a bus. It will also be appreciated that one or more of the illustrated functional components may be embodied by a single physical component, and that a functional component may be embodied by multiple physical components.

[0079]

[0079] In this example, the portable electronic device 6 receives a data packet from the aerosol delivery device 2a over a wireless communication network via the wireless communication interface 62. The data packet may include information about at least one physical characteristic of the aerosol delivery device 2a, such as an advertising packet 100 as described above with respect to Figures 9 and 10.

[0080]

[0080] In response to receiving the data packet from the aerosol delivery device 2a, the processor 64 of the portable electronic device 6 is configured to determine the identity of the aerosol delivery device 2a based at least in part on at least one physical characteristic of the aerosol delivery device 2a. For example, the processor 64 of the portable electronic device 6 can read the data packet to retrieve the color of the aerosol delivery device 2a. In an example where the data packet is an advertising packet 100 as described above with respect to Figures 9 and 10, the processor 64 is configured to read the PDU 130 of the advertising packet 100 to retrieve information regarding at least one physical characteristic of the aerosol delivery device 2a, such as the color, the UUID 132, and the product ID 134 conveyed as a hexadecimal color code 136 of the aerosol delivery device 2a.

[0081]

[0081] The memory 66 of the portable electronic device 6 may contain a database of physical characteristics of known aerosol delivery devices. As part of determining the identity of the aerosol delivery device 2a, the processor 64 of the portable electronic device 6 may compare information regarding at least one physical characteristic of the electronic nicotine delivery device 2a and information contained in the received data packet with information contained in the database stored in the memory 66 of the portable electronic device 6. For example, if the at least one physical characteristic of the data packet includes the shape and / or size of the aerosol delivery device 2a, this information may be matched with information in the database to determine the type of aerosol delivery device from which the data packet was sent. Alternatively or additionally, if the color of the aerosol delivery device 2a is conveyed in the data packet using a predefined code, the processor 64 may use information in the database to translate the code conveyed in the data packet into the color of the aerosol delivery device 2a.

[0082]

[0082] In this example, the processor 64 of the portable electronic device 6 is configured to change aspects of the user interface based on the determined identity of the aerosol delivery device 2a. This allows the user to easily identify the aerosol delivery device when communicating with the portable electronic device for the first time. For example, the processor 64 can be configured to present a pictorial or graphical representation of the aerosol delivery device 2a in the user interface, where the graphical representation is based on the determined identity of the aerosol delivery device 2a. Figures 12 and 13 show schematic user interfaces of the display 65 of the portable electronic device 6 corresponding to the changes in aspects of the user interface made by the processor 64 of the portable electronic device 6. In the example shown in Figures 12 and 13, a graphical representation 67 of the aerosol delivery device 2a is provided on a portion 65a of the display 65.

[0083]

[0083] Alternatively or in addition, the processor 64 may modify another aspect of the user interface, such as playing a video or image, playing a sound, modifying display settings of the user interface, such as the brightness, contrast, or resolution of the user interface, or modifying one or more colors displayed in the user interface. By modifying the aspect of the user interface based on the determined identity of the aerosol delivery device, the user knows the identity of the aerosol delivery device 2a from which the data is sent. This allows the user to decide what action to take, for example, to request initiation of a pairing process between the portable electronic device 6 and the aerosol delivery device 2a, or to block further communication of the aerosol delivery device 2a with the portable electronic device 6.

[0084]

[0084] The identity of the aerosol delivery device 2a can be determined based on the color of the aerosol delivery device 2a, and the processor 64 is configured to change the color of at least a portion of the user interface to match the color of the aerosol delivery device 2a. For example, if the color of the aerosol delivery device 2a is conveyed as a hexadecimal color code, the processor 64 is configured to change the color of at least a portion of the user interface to an RGB color corresponding to the hexadecimal color code. Alternatively, the processor 64 may be configured to present the physical characteristics used to identify the aerosol delivery device 2a in the user interface, such as in text form. In the example shown in FIG. 12, the graphical representation 67 is shaded to represent the color of the aerosol delivery device 2a, while in the example shown in FIG. 13, the graphical representation 67 is not colored to match the color of the aerosol delivery device 2a.

[0085]

[0085] The identity of the aerosol delivery device 2a may also be determined based on one or more of the UUID, product ID, and batch ID of the aerosol delivery device 2a, and the processor 64 may be configured to display this information in the user interface, for example, as text or with one or more images. If the identity of the aerosol delivery device 2a is also determined based on the color of the aerosol delivery device 2a, the processor 64 may be configured to change the color of at least a portion of the user interface to match the color of the aerosol delivery device 2a and display additional information, such as the UUID, product ID, and / or batch ID, in text form at or near the portion of the user interface that has been changed in color. In the example shown in Figure 12, the portion 65a of the display 65 also includes text 69, beside the graphical representation 67, that includes the product ID and UUID of the aerosol delivery device 2a. In the example shown in FIG. 13, instead of a graphical representation 67 configured to represent the color of the aerosol delivery device 2a, portion 65a of display 65 also includes text 69 next to the graphical representation 67 including the color of the aerosol delivery device 2a and the size of the aerosol delivery device 2a.

[0086]

[0086] The identity of the aerosol delivery device 2a can also be determined based on one or more of the shape, size, and type of the aerosol delivery device 2a. In such an example, in addition to or instead of displaying this information in text form in the user interface, the processor 64 may be configured to display a pictorial representation of the aerosol delivery device 2a. In this case, the shape and size of the pictorial representation are based on the shape, size, and type of the aerosol delivery device 2a used to determine the identity of the aerosol delivery device. For example, if the data packet received from the aerosol delivery device 2a indicates that the shape of the aerosol delivery device 2a is substantially cylindrical, the processor 64 is configured to display a cylinder in a portion of the user interface, for example, as a 2D plan view, or an orthographic or isometric view. In the example shown in FIG. 12, the shape of the graphical representation 67 is cylindrical to match the shape of the aerosol delivery device 2a. If the data packet received from the aerosol delivery device 2a indicates the size of the aerosol delivery device 2a, the processor 64 is configured to display a graphical representation showing the aerosol delivery device 2a. In this case, the dimensions of the graphical representation are scaled to the size of the aerosol delivery device 2a contained in the data packet. In the example shown in Figure 13, the graphical representation 67 is pebble-shaped or ovoid to match the shape of the aerosol delivery device 2a, and the graphical representation 67 is also scaled to match the size of the aerosol delivery device 2a.

[0087]

[0087] The memory 66 of the portable electronic device 6 optionally includes a database of physical characteristics of known aerosol delivery devices. Each entry in the database may include a pictorial or graphical representation of the corresponding aerosol delivery device. Thus, when the identity of the aerosol delivery device from which the data packet originates is determined based on a comparison with entries in the database stored in the memory 66 of the portable electronic device 6, the processor 64 may be configured to modify the behavior of the user interface by displaying in a portion of the user interface a pictorial or graphical representation of the entry in the database corresponding to the identity of the aerosol delivery device 2a.

[0088]

[0088] Any combination of the above user interface aspect modifications may be used. For example, processor 64 may be configured to display a graphical representation of aerosol delivery device 2a in at least a portion of the user interface, where the shape and size of the graphical representation is based on the shape and size information in the received data packet, the color of the graphical representation is based on the color information in the received data packet, and any additional information in the received data packet, such as the UUID, product ID, and batch ID of the aerosol delivery device, is displayed in text form beside the graphical representation or as part of the graphical representation, e.g., as text on the body of the aerosol delivery device in the graphical representation.

[0089]

[0089] The portable electronic device 6 optionally receives a data packet from the second aerosol delivery device 2b via the wireless communication interface 62 through the wireless communication network. The data packet may include information on at least one physical characteristic of the second aerosol delivery device 2b, for example, the advertising packet 100 as described above with respect to Figs. 9 and 10. The at least one physical characteristic of the second aerosol delivery device 2b included in the data packet may be the same set of characteristics as the data packet received from the first aerosol delivery device 2a, or may be a different set of characteristics or a duplicated set of characteristics. For example, the data packet received from the first aerosol delivery device 2a may include information on the color of the first aerosol delivery device 2a, the UUID and product ID of the first aerosol delivery device 2a, while the data packet received from the second aerosol delivery device 2b may include information on the color of the second aerosol delivery device 2b, information on the size of the second aerosol delivery device 2b, and information on the shape of the second aerosol delivery device 2b.

[0090]

[0090] In response to receiving a data packet from the second aerosol delivery device 2b, the processor 64 of the portable electronic device 6 is configured to determine the identity of the second aerosol delivery device 2b based at least in part on at least one physical characteristic of the aerosol delivery device 2b, as described above with respect to determining the identity of the first aerosol delivery device 2a.

[0091]

[0091] The processor 64 is then configured to modify aspects of the user interface based on the determined identities of the first aerosol delivery device 2a and the second aerosol delivery device 2b, for example, to allow the user to select one of the first aerosol delivery device 2a or the second aerosol delivery device 2b. For example, the processor 64 may be configured to display information regarding the identity of the first aerosol delivery device 2a in a first portion of the user interface and display information regarding the identity of the second aerosol delivery device 2b in a second portion of the user interface. The user can then select either the first aerosol delivery device 2a or the second aerosol delivery device 2b, for example, by touching a portion of the touch screen display corresponding to either the first portion of the user interface or the second portion of the user interface, or by using a pointing device to place a pointer on either the first portion of the user interface or the second portion of the user interface to make a selection, or by pressing a button or other input element, or by speaking or making a gesture.

[0092]

[0092] Fig. 14 shows a schematic representation of a user interface on the display 65 of the portable electronic device 6 corresponding to changes in aspects of the user interface made by the processor 64 of the portable electronic device 6. In the illustrated example, a first graphic representation 67a showing a first aerosol delivery device 2a is provided on a first portion 65a of the display 65, and a second graphic representation 67b showing a second aerosol delivery device 2b is provided on a second portion 65b of the display 65. The first graphic representation 67a is cylindrical to match the shape of the first aerosol delivery device 2a, and the second graphic representation 67b is cylindrical to match the shape of the second aerosol delivery device 2b. The first graphic representation 67a shows the color of the first aerosol delivery device 2a with shading, while the second graphic representation 67b shows the second aerosol delivery device 2b as white without shading. The first portion 65a of the display 65 also includes a first text 69a beside the first graphical representation 67a, the first text 69a including a product ID and UUID of the first aerosol delivery device 2a. The second portion 65b of the display 65 also includes a second text 69b beside the second graphical representation 67b, the second text 69b including a product ID and UUID of the second aerosol delivery device 2b. The user can then select either the first aerosol delivery device 2a or the second aerosol delivery device 2b, for example, by touching either the first portion 65a of the display 65 or the second portion 65b of the display 65 with a finger, stylus, or other suitable device, or by pressing a button 68, or by another selection means as described above.

[0093]

[0093] Figure 15 shows a method for a portable electronic device 6. In step 15-1, a data packet is received from an aerosol delivery device over a wireless communications network, the data packet including information regarding at least one physical characteristic of the aerosol delivery device. In step 15-2, an identity of the aerosol delivery device is determined based at least in part on the at least one physical characteristic of the aerosol delivery device. In step 15-3, an aspect of a user interface is altered based on the determined identity of the aerosol delivery device.

[0094]

[0094] Figure 16 shows a further method for a portable electronic device 6. In step 16-1, a data packet is received from a first aerosol delivery device over a wireless communication network, the data packet including information about at least one physical characteristic of the first aerosol delivery device. In step 16-2, a data packet is received from a second aerosol delivery device over a wireless communication network, the data packet including information about at least one physical characteristic of the second aerosol delivery device. In step 16-3, an identity of the first aerosol delivery device is determined based at least in part on the at least one physical characteristic of the first aerosol delivery device. In step 16-4, an identity of the second aerosol delivery device is determined based at least in part on the at least one physical characteristic of the second aerosol delivery device. In step 16-5, based on the determined identities of the first and second aerosol delivery devices, aspects of a user interface are modified, for example, to allow a user to select either the first aerosol delivery device or the second aerosol delivery device. This provides a simple means of identifying the aerosol delivery device when initially communicating with the aerosol delivery device.

[0095]

[0095] The order of steps of the method shown in Figure 16 is for purposes of illustrating the method only, and these steps may be performed in a different order. For example, determining the identity of the first aerosol delivery device in step 16-3 may occur before receiving a data packet from the second aerosol delivery device in step 16-2. The method shown in Figure 16 may also be extended to include more than two aerosol delivery devices, for example 3, 5, 10 or more aerosol delivery devices.

[0096]

[0096] By displaying the depictions and / or associated text for the two devices, an intuitive manner is provided that allows the user to be given information that allows the user to distinguish one from the multiple aerosol delivery devices before pairing with one of the devices, as described above with respect to Figs. 15 and 16. Such a manner for identity disambiguation provides a system that can reduce the error rate of selecting a device to pair with and / or reduce the time spent to successfully pair. The user can customize how the processor 64 of the portable electronic device 6 changes aspects of the user interface or which aspects of the user interface the processor 64 changes based on the determined identity of the aerosol delivery device. For example, the user can specify that only the shape of the aerosol delivery device is transferred to the graphical depiction, and the remaining information, such as color, UUID, and product ID, is displayed as text near the graphical depiction. This may be particularly applicable if the user is color blind or cannot distinguish between the graphical depiction showing the aerosol delivery device and the physical aerosol delivery device by color alone.

[0097]

[0097] Thus, in one aspect, a method and a portable electronic device have been described. The method includes receiving a data packet from an aerosol delivery device over a wireless communication network via a wireless communication interface capable of supporting paired interaction. The data packet includes information regarding at least one physical characteristic of the aerosol delivery device. An identity of the aerosol delivery device is determined based at least in part on the at least one physical characteristic of the aerosol delivery device, and an aspect of a user interface is altered based on the determined identity of the aerosol delivery device.

[0098]

[0098] Although the above embodiments are mainly described with respect to a wireless communication interface using Bluetooth LE, it should be understood that the principles of the present disclosure are not limited to using a specific wireless communication interface. For example, other implementations may be based on a Wi-Fi direct communication interface, or any other wireless communication interface.

[0099]

[0099] The various embodiments described herein are presented only to aid in the understanding and teaching of the claimed features. These embodiments are merely provided as representative examples of embodiments, and are not intended to be all-inclusive or exclusive. The advantages, embodiments, examples, features, features, structures, and / or other aspects described herein should not be construed as limiting the scope of the disclosure as defined by the claims, or limiting the equivalents thereto, and it is understood that other embodiments may be utilized and modifications may be made without departing from the scope and / or spirit of the claims.

[0100]

[0100] Further examples consistent with the present teachings are described in the following numbered clauses. [Clause 1] A step of receiving a data packet from an aerosol delivery device over a wireless communication network via a wireless communication interface capable of supporting paired interaction, the data packet including information regarding at least one physical characteristic of the aerosol delivery device; determining an identity of the aerosol delivery device based at least in part on the at least one physical characteristic of the aerosol delivery device; modifying an aspect of a user interface based on the determined identity of the aerosol delivery device; The method includes: [Clause 2] The method according to clause 1, wherein the wireless communication interface is a Bluetooth low energy communication interface. [Clause 3] The method of clause 2, wherein the data packet is a Bluetooth low energy data packet, and the information regarding at least one physical characteristic of the first aerosol delivery device and the second aerosol delivery device is included within a packet data unit of the Bluetooth low energy data packet. [Clause 4] The method of any one of clauses 1 to 3, wherein the at least one physical characteristic includes a color of the aerosol delivery device. [Clause 5] The method of clause 4, wherein the color of the aerosol delivery device is transmitted as a hexadecimal color code. [Clause 6] The method of clause 4, wherein the colour of the aerosol delivery device is transferred as a predetermined code. [Clause 7] The method of clause 6, wherein the step of determining the identity of the aerosol delivery device includes translating the predetermined code contained in the data packet into a color of the aerosol delivery device using information stored in a database in a memory. [Clause 8] The method of any one of clauses 1 to 7, wherein the at least one physical characteristic includes one or more of the shape of the aerosol delivery device, the size of the aerosol delivery device, and the type of the aerosol delivery device. [Clause 9] The method of any one of clauses 1 to 8, wherein the data packet received from the aerosol delivery device includes at least one of a batch number, a serial number, and a product identification number of the aerosol delivery device. [Clause 10] A method according to any one of clauses 1 to 9, wherein the step of determining the identity of the aerosol delivery device includes comparing the at least one physical characteristic of the aerosol delivery device to a database of physical characteristics of aerosol delivery devices stored in a memory. [Clause 11] A method according to any one of clauses 1 to 10, wherein the step of changing an aspect of the user interface includes one or more of: displaying a graphical depiction of the aerosol delivery device in the user interface, playing a video, playing a sound, changing one or more display settings of the user interface, and changing one or more colors displayed in the user interface. [Clause 12] receiving a data packet from a second aerosol delivery device over the wireless communication network via the wireless communication interface, the data packet including information regarding at least one physical characteristic of the second aerosol delivery device; determining the identity of the second aerosol delivery device based at least in part on the at least one physical characteristic of the second aerosol delivery device; modifying an aspect of a user interface to allow a user to select either the first aerosol delivery device or the second aerosol delivery device based on the determined identities of the first aerosol delivery device and the second aerosol delivery device; 12. The method of any one of clauses 1 to 11, further comprising: [Clause 13] The method of clause 12, wherein the step of changing an aspect of the user interface includes displaying a first graphical representation indicative of the first aerosol delivery device in a first portion of the user interface and displaying a second graphical representation indicative of the second aerosol delivery device in a second portion of the user interface. [Article 14] At least one processor; a wireless communication interface capable of supporting paired interaction; a memory containing instructions which, when executed by said at least one processor, cause said at least one processor to perform a method according to any one of clauses 1 to 13; A portable electronic device comprising:

[0101]

[0101] Various embodiments within the scope of the claims may suitably comprise, consist of, or consist essentially of any suitable combination of the disclosed elements, components, features, parts, steps, means, etc., other than those specifically described herein. Moreover, the disclosure may include other concepts not currently claimed, but which may be claimed in the future in combination with the currently claimed features or separately from the currently claimed features.

Claims

[Claim 1] The method described in the specification.