WO2025217537A1

WO2025217537A1 - Cartridge identification and protection

Info

Publication number: WO2025217537A1
Application number: PCT/US2025/024305
Authority: WO
Inventors: Jack HUNTER; Charles Eric Hunter; Gregory RAPP; Jeffrey Miller; Matthew CULPEPPER; Caley MODLIN
Original assignee: Pneuma Respiratory Inc
Current assignee: Pneuma Respiratory Inc
Priority date: 2024-04-12
Filing date: 2025-04-11
Publication date: 2025-10-16
Anticipated expiration: 2026-10-12

Abstract

A droplet delivery device for inhalation, such as including a nosepiece or mouthpiece, includes a fluid-delivery cartridge with an identifier that conveys information about the cartridge, liquid in the cartridge that is to be ejected for inhalation, use of the droplet delivery device, operating parameters operating restrictions, and the like. Following reading of the identifier by a scanner, contact data transfer, camera, electronic signal reader and the like, a computer processor in the droplet delivery device or connected to the droplet delivery device controls operation of the droplet delivery device based on the information determined from the identifier.

Description

CARTRIDGE IDENTIFICATION AND PROTECTION

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of priority of U.S. provisional application no. 63/633,136 filed April 12, 2024, and U.S. provisional application no. 63/701,565 filed September 30, 2024, which are incorporated herein by reference in their entireties.

FIELD OF THE INVENTION

[0002] This disclosure relates to droplet delivery devices and more specifically to a droplet delivery device for the delivery of fluids from a supply container, such as a fluid cartridge, which are inhaled into mouth, throat, nose, and/or lungs for therapeutic or non -therapeutic effects.

BACKGROUND OF THE INVENTION

[0003] The present application incorporates herein by reference in their entirety the contents of WO 2020/264501 (describing “Ring Mode” ejection) and WO 2022/271848 (describing “Push Mode” ejection). In embodiments, fluid-delivery cartridges described herein may be provided with push mode ejection technology as described in U.S. Patent No. 11,793,945, which is also incorporated herein by reference.

[0004] In embodiments, fluid-delivery cartridges described herein may be used with any cartridgebased droplet delivery device, including, but not limited to, electronic nicotine delivery devices, medical devices, and consumer devices. For the purposes of this disclosure, electronic nicotine delivery devices encompass heated technology (i.e., vapes, e-cigarettes, etc.) and non-heated technology (i.e., push mode and ring mode devices).

[0005] In cartridge-based droplet delivery devices like push mode or ring mode devices, there is a need to implement safety measures to ensure the liquid being ejected as droplets for inhalation is correct. This can be ensuring a user does not replace the liquid, making sure the liquid is not expired, making sure the cartridges are not refilled with unsafe liquids, and ensuring the cartridges that are used are genuine.

SUMMARY OF THE INVENTION

[0006] To answer this need, cartridges of the invention have an information-conveying identifier, such as a tag or contact point, that includes, for example, a memory chip, antenna, barcode, QR code, or other electrical hardware such as RFID, NFC tags, or an SPI-based EEPROM chip that indicates several parameters and/or information about the cartridge. A droplet device may include tag-reading capabilities or external devices such as a smartphone, camera, reader device and the like may read the tag or information conveying contact point.

[0007] In embodiments, a cartridge tag can be read to obtain information about fluid in the cartridge, use of the fluid, the cartridge, the droplet delivery device, and the like, including, for example liquid information, manufacturing lot ID, formulation ID, shot time, and/or manufacturer ID. Non-limiting examples of cartridge tags include a QR code, barcode, RFID tag, or NFC tag.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] FIG. 1 is a schematic diagram illustrating a cartridge (10) connected to a mouthpiece (20) for a droplet delivery device wherein the cartridge includes a readable identifier such as a tag (30) conveying information about the cartridge and/or associated droplet delivery device that that can be read by scanning, camera and reader capabilities of the droplet delivery device or associated reading devices in different examples of the invention.

[0009] FIG. 2 is a cross-sectional schematic view of a cartridge comprising a contact point or chip and a droplet delivery device comprising a compatible contact point and a printed circuit board (PCB) in one example of the invention.

[0010] FIG. 3 is a state flow diagram showing the process through which a device comprising a microcontroller (MCU) can control actuation when paired with a smartphone that scans a tag (i.e., barcode, QR code, NFC tag, or RFID tag) on a cartridge used in conjunction with the device in one example of the invention.

[0011] FIG. 4 is a state flow diagram showing the process through which a droplet device with an MCU can control actuation when paired with a cartridge that contains a chip in one example of the invention.

[0012] FIG. 5 is a diagram illustrating a cartridge (10) connected to a mouthpiece (20), where in the cartridge has two parallel plates (50) that can be used to measure the capacitance of the liquid in one example of the invention.

DESCRIPTION OF THE INVENTION

[0013] In cartridge-based droplet delivery devices like push mode or ring mode devices, it is important to implement safety measures to ensure the liquid is correct. This can be ensuring a user does not replace the liquid, making sure the liquid is not expired, making sure the cartridges (10) are not refilled with unsafe liquids, and ensuring the cartridges that are used are genuine. [0014] In embodiments, fluid-delivery cartridges described herein may be used with any cartridgebased droplet delivery device, including, but not limited to, electronic nicotine delivery devices, medical devices, and consumer devices. For the purposes of this disclosure, electronic nicotine delivery devices encompass heated technology (i.e., vapes, e-cigarettes, etc.) and non-heated technology (i.e., push mode and ring mode devices).

[0015] In some embodiments, a fluid-supplying cartridge (10) of a droplet delivery device is preferably removable and replaceable and comprises a readable tag or contact point that, in nonlimiting examples, includes a memory chip, antenna, barcode, QR code, or other electrical hardware such as RFID, NFC tags, or an SPI-based EEPROM chip that indicates several parameters about the cartridge or information about the fluid, device or cartridge. The droplet delivery device will read information from the tag, such as liquid information, manufacturing lot ID, formulation ID, shot time, and/or manufacturer ID. FIG. 1 shows a non-limiting example embodiment of a cartridge (10) with a mouthpiece (20). The cartridge has a tag (30) that can comprise a QR code, barcode, RFID tag, NFC tag, or readable information-conveying elements.

[0016] An RFID or NFC tag is read with a scanner that can be located on or in the handpiece of the device or via a smartphone that can be connected to a mobile app. A QR code or barcode will read with a scanner that can be located on or in the handpiece of the device or via a camera on a smartphone that can be connected to a mobile app. As a non-limiting example, FIG. 3 shows a state diagram outlining the process through which a device comprising a microcontroller (MCU) can control actuation when paired with a smartphone that scans a tag (i.e., barcode, QR code, NFC tag, or RFID tag) on a cartridge used in conjunction with the device.

[0017] A chip will be read through direct contact with the hardware on the device. FIG. 2 shows a non-limiting example embodiment of a cartridge (10) with a contact point or chip (40) located on the bottom of the cartridge. The handpiece (100) of the device contains a compatible contact point (110) that contacts the chip on the cartridge when the cartridge is inserted. The cartridge and MCU, located on PCB (120) in the handpiece, communicate via this contact point. An example embodiment of this can be an SPI-based EEPROM chip. As a non-limiting example, FIG. 4 shows a state diagram outlining the process through which a device comprising an MCU can control actuation when paired with a cartridge that contains a chip.

[0018] An RFID, NFC tag, barcode or QR code can all hold a unique identifier. This identifier is used to look up the necessary information about the cartridge (10). There would either be a chip on the device that holds the information for all necessary identifiers, or the device would communicate with a mobile app that would retrieve the necessary information from a database, such as via connection to a local or wide area online network, including the Internet.

[0019] A chip (40) on the cartridge (10) can house all necessary information on the chip itself. The droplet device communicates with the chip on the cartridge to determine the next course of action. [0020] The droplet device in examples of the invention can measure spray time of an individual cartridge (10). Each cartridge is preferably made to have a certain volume of liquid. The amount of volume shot per second is known. Therefore, each cartridge has a total number of seconds it can be ejected. Keeping track of the seconds of ejection allows the cartridge to be made dead once it reaches its limit. Therefore, the cartridge cannot be refilled or reused. This limits the use of potentially dangerous and unapproved liquids in the device.

[0021] The number of seconds of ejection will be saved with the cartridge ID. If the cartridge (10) has a chip (40) on it, the total number of ejected seconds will be saved on the cartridge chip. If there is no chip on the cartridge, the droplet delivery device will keep track of the number of ejected seconds and associated cartridge ID. The device can be connected to a mobile app and this information can be added to a database/cloud/server/or other storage application.

[0022] The device can record the spray interval down to 0.1 ms.

[0023] If the device has varying power (meaning the device will eject different volume rates), the device will be able to compensate. For lower power and less ejection of fluid volume per time, the device would have more ejection time per cartridge (10). These can all be weighted. In a nonlimiting example, for a medium power (e.g. 50%) device, each second of spray of droplets is equivalent to 1 second of recorded time. For a low power (e.g. 25%), each second of spray of droplets of droplets ss equivalent to 0.5 seconds of recorded time. For a high power device (e.g. 100%), each second of spray of droplets is equivalent to 2 seconds of recorded time.

[0024] This sort of cartridge ID can also be used to ensure the device does not dry fire. This means the device will never be ejected without verification of liquid being present or a cartridge (10) attached. When no liquid is attached in a cartridge to supply the droplet delivery device, an ejector can generate heat to an undesirable temperature in a dry firing situation. Limiting the amount of dry firing helps extend the life of the ejector and avoid safety issues with the droplet delivery device. [0025] A cartridge ID of the invention can also prevent any illicit or third-party cartridges (10) from being used. This makes it safer for the user because only approved liquids from authorized supply sources can be used in the device. The cartridge ID can also be referenced to a list. If the cartridge ID is present and unused, the device will work. If the cartridge ID is not present, or it is used, the device will not allow any ejection to occur. The lookup database can either be on the device, or the device can connect to a mobile app to reach the database on a connected network, including via wireless connectivity.

[0026] In another embodiment, the device can determine if the cartridge (10) and/or liquid is authentic by measuring the capacitance of the liquid using parallel plates (50) across the cartridge body. The plates will connect to the device when the cartridge is inserted. The internal MCU in the handpiece will ensure the capacitance matches the allowed capacitances (this data can be sent to an associated app to be handled). If the liquid has been changed, the capacitance will change. Additionally, this can keep track of how much liquid is left in the cartridge. As the liquid level decreases, the capacitance changes.

[0027] FIG. 5 shows a non-limiting example embodiment of a cartridge (10) comprising a mouthpiece (20) and parallel plates (50). In example embodiments, the device can determine if the cartridge (10) and/or liquid is authentic by measuring the conductivity of the liquid. Two points on the cartridge will be touching the liquid. These points will connect to the device when attached to the handpiece (100). The handpiece will run current through them and measure the resistance, current, and or conductivity. The MCU on the handpiece of a droplet delivery device can ensure the conductivity value is within specifications for an authorized liquid. This data can be sent to an associated app to be processed.

[0028] In another embodiment, the cartridge (10) will have a very specific resistor on it. When the cartridge is connected to the handpiece (100), the device will measure its resistance. If the resistance is within the proper range, the device will allow fluid from the cartridge to be ejected.

[0029] Element numbers are provided in Table 1 for convenient reference with respect to the descriptions and figures provided herein. Table 1

[0030] While described with reference to specific embodiments herein, the invention is intendedo extend in scope to the full extent of the disclosure.

Claims

WHAT IS CLAIMED:

1. A droplet delivery device comprising a fluid-delivery cartridge including an informationconveying identifier representing data about at least one of the cartridge and inhalable fluid in the cartridge, wherein the identifier is configured to be received by a computing processor, wherein the computing processor controls operating parameters or restrictions of the droplet delivery device based on the identifier.

2. The droplet delivery device of claim 1, wherein the droplet delivery device further comprises a mouthpiece or nasal piece.

3. The droplet delivery device of claim 2, wherein the computing processor is located in the handpiece of the device.

4. The droplet delivery of claim 2, wherein the computing processor is communicating with a mobile application.

5. The droplet delivery device of claim 3, wherein the fluid-delivery cartridge contains nicotine.

6. The droplet delivery device of claim 5, wherein the device is connected to a mobile application to allow for user interaction and access to lookup databases.

7. The droplet delivery device of claim 1, further comprising a push mode ejector in fluid communication with the cartridge.

8. The droplet delivery device of claim 1, further comprising a ring mode ejector in fluid communication with the cartridge.

9. The droplet delivery device of claim 1, wherein the computing processor is configured to change the identifier’s information or data.

10. The droplet delivery device of claim 2, further comprising a push mode ejector in fluid communication with the cartridge.

11. The droplet delivery device of claim 2, further comprising a ring mode ejector in fluid communication with the cartridge.

12. The droplet delivery device of claim 3, further comprising a push mode ejector in fluid communication with the cartridge.

13. The droplet delivery device of claim 3, further comprising a ring mode ejector in fluid communication with the cartridge.

14. The droplet delivery device of claim 5, further comprising a push mode ejector in fluid communication with the cartridge.

15. The droplet delivery device of claim 5, further comprising a ring mode ejector in fluid communication with the cartridge.

16. A droplet delivery device including: a fluid-delivery cartridge with liquid inside the cartridge; one or more sensors operatively coupled to the liquid inside the cartridge and configured to measure properties of the liquid; and a computer processor communicatively coupled to the one or more sensors is configured to control operating parameters or restrictions of the droplet delivery device based on data received from the one or more sensors.

17. The droplet delivery device of claim 16, wherein the droplet delivery device further comprises a mouthpiece or nasal piece.

18. The droplet delivery device of claim 16 or 17, wherein the fluid-delivery cartridge contains nicotine.

19. The droplet delivery device of claim 16 or 17, wherein the device is connected to a mobile application to allow for user interaction and access to lookup databases.

20. The droplet delivery device of claims 16 or 17, wherein the droplet delivery device includes a push mode ejector or ring mode ejector in fluid communication with the cartridge.