Mobile defibrillator with improved pads, charging, and switching.

The mobile AED system with subcutaneous needles and intelligent power management addresses the limitations of conventional defibrillators by ensuring continuous power and efficient shock delivery, enhancing survival chances in cardiac arrest situations.

JP2026516744APending Publication Date: 2026-05-26デフィブリオ·アーエス

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
デフィブリオ·アーエス
Filing Date
2024-04-17
Publication Date
2026-05-26

AI Technical Summary

Technical Problem

Existing defibrillators are not widely available and may run out of power during critical stages of resuscitation, and conventional pads do not efficiently deliver shocks due to high skin resistance and poor fixation, leading to increased mortality rates in cardiac arrest situations.

Method used

A mobile AED system that includes a defibrillator unit connected to a device capable of running applications, utilizing needles for subcutaneous current delivery, redundant charging ports, and intelligent power management to ensure continuous operation, along with pads that pierce the skin for reduced resistance and better fixation.

Benefits of technology

The system enhances availability, reduces energy requirements, and ensures continuous power supply, allowing for earlier shock delivery and improved survival chances by minimizing skin resistance and maintaining pad fixation during resuscitation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026516744000001_ABST
    Figure 2026516744000001_ABST
Patent Text Reader

Abstract

The disclosed system and method provides a mobile defibrillator system which may include a mobile defibrillator (AED) unit configured to be operablely connected to a device capable of running an application. The mobile AED unit may include a circuit for delivering an electric shock to a person and one or more pads. Each pad may include one or more needles electrically connected to the circuit and may be configured to puncture the person's skin, be present in the person's body, and deliver an electric current from the electric shock to the person.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims priority to U.S. Patent Application No. 18 / 302,113, filed on April 18, 2023, the entire disclosure of which is incorporated herein by reference.

Background Art

[0002] Sudden cardiac arrest (e.g., heart failure) may be accompanied by a sudden loss of heart function, breathing, and consciousness. In many cases, this condition can result from an electrical disorder of the heart that prevents the heart's pumping action, which can cause the blood flow in the body to stop. It is estimated that in the United States alone, approximately 300,000 people die from out - of - hospital cardiac arrest each year.

Summary of the Invention

Means for Solving the Problems

[0003] According to one aspect of the present disclosure, a mobile defibrillator system can include a mobile automated external defibrillator (AED) unit configured to be operably connected to a device capable of running an application. The mobile AED unit can include a circuit for delivering an electrical shock to a subject and one or more pads. Each pad can include one or more needles electrically connected to the circuit and configured to pierce the subject's skin and deliver the current from the electrical shock to the subject who is present inside the subject's body.

[0004] In some embodiments, one or more needles may include a metallic material. In some embodiments, one or more needles may be curved. In some embodiments, one or more needles may be curved away from the subject. In some embodiments, one or more needles may be configured to reside in the subcutaneous tissue of the subject. In some embodiments, one or more pads may be foldable. In some embodiments, one or more needles may be configured to act in response to instructions received from a device. In some embodiments, instructions may be generated based on detecting an impedance exceeding a predetermined threshold between one or more pads and the subject.

[0005] According to another aspect of the present disclosure, a mobile defibrillator system may include a mobile defibrillator (AED) unit configured to be operably connected to a device that can run an application and act as a first power source for a mobile AED. The mobile AED unit may include a circuit for delivering an electric shock to a person, one or more pads configured to adhere to the person for delivering the electric shock, a first charging port, and a second charging port. The device may be configured, via one or more processors, to switch from a first power source at the first charging port to a second power source at the second charging port during a defibrillation procedure.

[0006] In some embodiments, the device may be configured to determine, via one or more processors, that the battery level of a first power supply is below a predetermined threshold, display a query to the device, receive an instruction from the user that a second power supply is nearby in response to the display of the query, detect that the second power supply is within a predetermined vicinity, and, in response to the detection that the second power supply is within a predetermined vicinity, initiate a power switching process. In some embodiments, the power switching process may include initiating data transfer between the device and the second power supply, performing a handshake between the device and the second power supply, receiving an instruction that the second power supply is connected to a second charging port, and continuing the defibrillation procedure.

[0007] In some embodiments, the power switching process may include returning to the device to power the mobile AED in response to an error. In some embodiments, detecting that a second power source is within a predetermined vicinity may be performed via Bluetooth®, NFC, or WiFi. In some embodiments, detecting that a second power source is within a predetermined vicinity may include receiving the location, version, and capacity of the second power source, analyzing the location, version, and capacity of the second power source, determining that the second power source is acceptable, and sending a warning to the second power source.

[0008] According to another aspect of the present disclosure, a mobile defibrillator system may include a mobile defibrillator (AED) unit configured to be operably connected to a device that can run an application and act as a power source for a mobile AED. The mobile AED unit may comprise a circuit for delivering an electric shock to a person, which may include a charge controller, a sensing line bias circuit, a current sensing resistor, a switch, a transformer, and a capacitor, and one or more pads configured to adhere to a person for delivering an electric shock.

[0009] In some embodiments, the charge controller may be configured to control the sensing line bias circuit using a pulse-width modulated waveform. In some embodiments, the current sensing resistor may be configured to monitor the current flowing through the switch and transformer. In some embodiments, the charge controller may be configured to interrupt the switch in response to the current sensing resistor detecting a voltage exceeding a predetermined threshold. In some embodiments, the predetermined threshold may be 78 mV. In some embodiments, the current limit of the transformer may be greater than 2 amperes.

[0010] According to another aspect of the present disclosure, a mobile defibrillator (AED) device may include a mobile AED unit configured to be operablely connected to a device capable of running an application. The mobile AED unit may include one or more electrodes and may be configured to measure respiratory data of a person. The device may be configured to detect the connection of the mobile AED unit to the device via one or more processors running on the device, detect that one or more electrodes have been connected to a person, receive EKG measurements of the person recorded by the electrodes, receive measured respiratory data from the AED unit relating to the respiratory movement of the person's chest, receive wearable data from a wearable device associated with the person, analyze the respiratory data to determine the person's breathing pattern, determine that the person requires an electric shock based on the received EKG measurements, the wearable data and the determined breathing pattern, determine shock pattern factors based on the received EKG measurements, the wearable data and the determined breathing pattern, the shock pattern factors including duration, time interval and energy level, and, based on the determination, deliver an electric shock to the person via the mobile AED using the determined shock pattern factors.

[0011] The various purposes, features, and advantages of the disclosed subject matter can be more fully understood by referring to the following detailed description of the disclosed subject matter, where similar reference numbers identify similar elements in relation to the following drawings.

[0012] The drawings are not necessarily to scale, nor do they include all elements of the system; instead, the emphasis is generally on illustrating the concepts, structures, and technologies that are required to be protected herein. [Brief explanation of the drawing]

[0013] [Figure 1] The present disclosure provides an exemplary mobile automated external defibrillator (AED) system according to several embodiments. [Figure 2] This is an exemplary schematic circuit diagram of a mobile AED according to some embodiments of the present disclosure. [Figure 3A] This disclosure shows various charging configurations for a mobile AED according to several embodiments. [Figure 3B] This disclosure shows various charging configurations for a mobile AED according to several embodiments. [Figure 3C] This disclosure shows various charging configurations for a mobile AED according to several embodiments. [Figure 3D] This disclosure shows various charging configurations for a mobile AED according to several embodiments. [Figure 4] This is a block diagram of a mobile AED device system according to some embodiments of the present disclosure. [Figure 5] The following are exemplary pads for use with a mobile AED according to some embodiments of this disclosure. [Figure 6] This is a mobile AED power supply selection decision flow according to some embodiments of the present disclosure. [Figure 7] This is a switching mobile controller determination flow according to some embodiments of the present disclosure. [Figure 8]A process for charging a mobile AED according to some embodiments of the present disclosure. [Figure 9] A process for charging a mobile AED according to some embodiments of the present disclosure. [Figure 10] Shows voltage (y-axis) as a function of time (x-axis) in an electrode / pad according to some embodiments of the present disclosure. [Figure 11] Shows an exemplary circuit architecture according to some embodiments of the present disclosure. [Figure 12] An exemplary process for using a mobile AED according to some embodiments of the present disclosure. [Figure 13] An exemplary server device that can be used within the system of FIG. 4 according to some embodiments of the present disclosure. [Figure 14] An exemplary computing device that can be used within the system of FIG. 1 and / or FIG. 3 according to some embodiments of the present disclosure.

Mode for Carrying Out the Invention

[0014] Those skilled in the art will understand that the elements in the figures are shown for simplicity and clarity and are not necessarily drawn to scale. For example, some dimensions of the elements in the figures may be exaggerated relative to other elements to help improve the understanding of the embodiments of the present disclosure.

[0015] The structural components of the security system are represented by conventional symbols in the figures as necessary, showing only the specific details relevant to the understanding of the embodiments of the present disclosure so as not to obscure the present disclosure with details that will be readily apparent to those skilled in the art who benefit from the description herein.

[0016] The following detailed description is merely exemplary in nature and is not intended to limit the invention or its use in any way.

[0017] The availability of public defibrillators or automated external defibrillators (AEDs) can have a significant impact on the survival of individuals experiencing cardiac arrest. Patients receiving an electric shock from a publicly available AED have a much higher survival rate. Without cardiopulmonary resuscitation (CPR), the mortality rate can increase by 10% per minute.

[0018] Embodiments of this disclosure relate to a mobile AED that can be controlled by the processing power of an external device such as a smartphone, tablet, laptop, watch, or in-car entertainment system. The mobile AED of this disclosure may be smaller and more widely available than any previous attempt. It can be used by any person with access to a device having a microphone, speaker, data storage, and power supply. The pads / electrodes used with the mobile AED may include an accelerometer, and the defibrillator unit may include an electric shock circuit. This makes it possible to create a mobile AED that is easily portable and more versatile.

[0019] In some embodiments, the mobile AEDs of this disclosure can be utilized according to various advantageous charging and communication technologies. For example, the disclosed mobile AEDs may be operable to receive wireless charging and reverse wireless charging (e.g., wireless charging from a mobile device). Furthermore, the disclosed mobile AEDs may include redundant (i.e., additional) charging ports that can enable improved power redundancy. In addition, the primary power supply of the mobile AED can be changed during operation by utilizing various power selection processing technologies, which can provide advantageous benefits such as preventing the mobile AED from running out of power at critical stages of the resuscitation process.

[0020] Furthermore, mobile AEDs of some embodiments of the present disclosure may include one or more pads / electrodes, each containing a needle configured to puncture the subject's skin during defibrillation, which can offer various advantages such as reduced skin resistance and better fixation between the subject and the pad. This can also reduce the energy required in the pulse, thereby reducing the need for / size of the capacitor for the AED.

[0021] In some embodiments, the mobile AEDs of this disclosure can be utilized according to advantageous processing techniques that allow the AED to detect and read the patient's heartbeat while it is charging. This allows for earlier delivery of the shock to the patient, thereby increasing the chances of survival.

[0022] In some embodiments, the mobile AEDs of the present disclosure can be utilized according to an advantageous charging technique that enables faster charging of the AED. This may be called a residual charging technique that utilizes residual charge in the AED's capacitor from a previous shock to help reach an energy level for a subsequent shock.

[0023] Figure 1 shows an exemplary mobile AED system 100 according to some embodiments of the present disclosure. The mobile AED system 100 may include a defibrillator unit 102 detachably connected to a device 101 via a connection 103. The defibrillator unit 102 may include a circuit configured to generate a specific pulse or shock to be administered to a patient in order to treat a patient in cardiac arrest (see Figure 2). Note that the device 101 is a smartphone in this figure of the mobile AED system 100, but this is not limited to it. The device 101 may be a tablet, laptop, computer, watch, or other device having an operating system capable of running applications such as an in-car entertainment system. In some embodiments, the connection 103 may include a USB-C connection or other similar connection. When the device 101 and the defibrillator unit 102 are connected, the connection 103 may allow the defibrillator unit 102 to be controlled via a user interface and applications on the device 101. In some embodiments, the defibrillator unit 102 may optionally include an additional connection port to the power bank 104 (e.g., a portable charger, a wall outlet, etc.), which may be a USB-C port but may be different from the port for connection 103.

[0024] The defibrillator unit 102 may include an additional port for connection to wiring 105, which can function as a medium to transfer the shock determined and / or generated by the circuitry within the defibrillator 102 to pads 106a-b. Pads 106a-b can be any standard defibrillator pads known in the art and can be configured to adhere to the patient's body and act as electrodes for supplying electric current from the defibrillator unit 102 into the person's body. In some embodiments, pad 106 may be the pad described in relation to Figure 5. In some embodiments, pads 106a-b may also include accelerometers. In some embodiments, pads 106a-b may also include more intelligent sensing devices, such as a circuitry for ultrasonic detection of blood flow and / or an optical sensor for oxygen saturation, which may be particularly useful for self-rescue. In some embodiments, when the defibrillator unit 102 is connected to or plugged into device 101, the user can connect to a video assistant specialist 107. In some embodiments, a team of specialists can work on call and communicate with the device user. For example, if a person suddenly experiences cardiac arrest, a person nearby can connect the defibrillator unit 102 to the device 101, navigate to an application (or the application can open automatically upon connection), and choose the option to immediately participate in a video session with a specialist who can assist this person in delivering a shock and / or CPR to the patient. In some embodiments, the person can also connect to emergency services (e.g., call 911) via the application on the device 101. In some embodiments, the application on the device 101 can be configured to be remotely controlled by paramedics or mobile AED specialists. This allows paramedics to actually control and deliver an electric shock to a person connected to the defibrillator unit 102, as the defibrillator unit 102 is controlled by the application on the device 101.In some embodiments, the defibrillator unit 102 can be configured to receive power from a 220V power supply or socket, or from a 12V socket in the vehicle.

[0025] In some embodiments, the defibrillator unit 102 can be integrated into the vehicle. For example, the defibrillator unit 102 can be completely integrated with only a long wiring pad (4m or more) as the only visible part, or it can be a modular defibrillator unit 102 similar to the original device that can connect to a mobile phone or car app. This makes the defibrillator unit 102 more accessible for use in a variety of situations.

[0026] In some embodiments, the mobile AED system 100 shown in Figure 1 may be the same as or similar to the devices described in U.S. Patents 11,173,315 and 11,439,837, both of which are incorporated herein by reference in their entirety.

[0027] In some embodiments, the defibrillator unit 102 may include a circuit design that allows for the safe storage of charge in the capacitor, enabling the charging process shown in Figure 8. In some embodiments, the defibrillator unit 102 may include redundant charging ports, such as those consistent with the charging configuration described in relation to Figures 3A to 3D.

[0028] In some embodiments, the application on device 101 may also be configured to receive data from an external device connected to the user device 101, such as a smartwatch or other similar device that monitors the subject. For example, a person's smartwatch can consistently monitor the person's heart rate and transmit this information to the user device 101. In these embodiments, the signals from the smartwatch, in addition to the pads 106a-b, can be used to improve the effectiveness of defibrillation. Application 304 may be configured to monitor and analyze the subject's heart rate and potentially identify and / or detect dangerous rhythms (e.g., rapid ventricular tachycardia, ventricular fibrillation, or other rhythm indicators trained to detect by a neural network). In response to the detection of a dangerous rhythm, the application may be configured to notify the subject via device 101 and instruct the subject to connect the subject's mobile AED and pads and potentially initiate a self-rescue protocol.

[0029] Furthermore, the application on device 101 can be configured to perform processing techniques described in relation to Figures 6 and 7 in order to select a power supply and switch the mobile controller via one or more processors on the mobile device 101.

[0030] Figure 2 is an exemplary schematic circuit diagram 200 of a mobile AED according to several embodiments of the present disclosure. The circuit 200 can be included within the defibrillator unit 102 of Figure 1. In some embodiments, the circuit 200 may include a charger 201, switches 202 and 203, an inductor 204, a resistor 205, a pass-through resistor 206, and a capacitor 207. In some embodiments, the pass-through resistor 206 may represent the resistance in the person's body present between pads 106a and 106b while pads 106a and 106b are connected. The charger 201 can charge the capacitor 207 when switches 202 and 203 are in the left position (as shown in Figure 2). In some embodiments, the charger 201 may represent the battery of the connected device (e.g., device 101 in Figure 1), an external power bank (e.g., power bank 104 in Figure 1), or a combination of both. Switches 202 and 203 can be controlled via logic within device 101 and via applications that the user can navigate on device 101. For example, the application can determine the duration for which a shock (e.g., a pulse of current / energy) should be delivered to the patient. To deliver the shock, switches 202 and 203 move to the rightward position (not shown in Figure 2), thereby allowing current to flow from capacitor 207 through the patient, inductor 204, and resistor 205. As the current flows through the patient's heart, it can serve to resuscitate the subject until paramedics or other emergency response teams can stabilize the subject. In some embodiments, the circuit 200 can be configured to deliver pulses of up to 200-360 J or more, and to deliver them repeatedly for up to 1 hour or even 90 minutes or more.

[0031] Figures 3A to 3D show various charging configurations for a mobile AED according to several embodiments of the present disclosure. The defibrillator unit 102 may include redundant (i.e., second) charging ports. In some embodiments, the redundant charging port may be a secondary USB-C port and / or wireless charging functionality. Furthermore, the defibrillator unit 102 may be configured to be fully power redundant.

[0032] Figure 3A shows the charging of the defibrillator unit 102, which receives charge from the mobile device 101 via a USB-C connection cable plugged into one of the charging ports. Figure 3B shows the functionality of the defibrillator unit 102, which receives charge from the mobile device 101 via one charging port, or via an external battery charger via a secondary charging port. Figure 3C shows the defibrillator unit 102, which receives charge from the mobile device 101 via one charging port, or from a second mobile device 101 via a second charging port.

[0033] Figure 3D shows a defibrillator unit 102 that wirelessly receives charge from a mobile device 101. In some embodiments, the defibrillator unit 102 is configured to be wirelessly powered via wireless charging utilizing the Qi wireless standard. In some embodiments, such wireless charging may come from either a Qi charging device (not shown) or a mobile phone with reverse wireless charging. Qi is generally known as an open interface standard that performs wireless power transmission via inductive charging over distances up to about 4 cm and is supported by many manufacturers. For example, there are currently about 80 available phone models that support reverse wireless charging, which allows a phone to charge other devices (e.g., smartphones, smartwatches, smart bands, this defibrillator unit 102).

[0034] In some embodiments, the defibrillator unit 102 may include USB-C cable charging, wireless charging, or both. Today's wireless charging can support up to approximately 10W for reverse wireless charging and up to 80W or more for Qi-enabled devices, and this is likely to increase in the near future. In some embodiments, the defibrillator unit 102 may include redundant charging posts (e.g., secondary USB-C or wireless charging functionality). If the defibrillator unit 102 is at risk of power shortage (i.e., the device charging it, or the device supplying it), a secondary power source can be connected to continue charging and the defibrillation process can continue. Power switching selection processes are described with reference to Figures 6 and 7. In some embodiments, the charging capability may be USB 3.2 or USB 4.0.

[0035] Figure 4 is a block diagram of a system 400 of a mobile AED device according to some embodiments of the present disclosure. In some embodiments, the system 400 may include a plurality of user devices 402a-n (collectively, user device 402) that are communicably coupled to a server device 410 via a network 408. The system 400 includes two user devices 402a-n for illustrative purposes, but it should be noted that any number of user devices may be included in the system of the present disclosure.

[0036] In some embodiments, network 408 may include one or more wide area networks (WANs), metropolitan area networks (MANs), local area networks (LANs), personal area networks (PANs), or any combination thereof. Network 408 may include a combination of one or more types of networks, such as the Internet, intranet, Ethernet, twisted pair, coaxial cable, optical fiber, cellular, satellite, IEEE 801.11, terrestrial, and / or other types of wired or wireless networks. Network 408 may also use standard communication technologies and / or protocols.

[0037] In some embodiments, the user device 402 may be similar to or identical to device 101 in Figure 1. For example, the user device 402 may include a smartphone, tablet, laptop, watch, in-car entertainment system, or a combination of similar types of devices capable of running software applications and utilizing an operating system. The user device 402 may include one or more computing devices capable of receiving user input, transmitting and / or receiving data over the network 408, or communicating with the server device 410. In some embodiments, the user device 402 may include a conventional computer system such as a desktop or laptop computer. Alternatively, the user device 402 may include a device with computer functionality such as a personal digital assistant (PDA) or other suitable device. Furthermore, each user device 402 may include a specially installed application 404 for use with a connected mobile AED 406. The application 404 may include software instructions that can be stored on a non-temporary computer-readable medium that, when executed by a processor (e.g., a processor within the user device 402), can perform various processes related to delivering a shock as an AED and reading the EKG in cooperation with the mobile AED 406.

[0038] In some embodiments, application 404 may include further instructions to read the patient's heart rate while the defibrillator unit 406 is charging. Instead of reading and analyzing the heart rate and then waiting for the device to fully charge, as conventional AED devices do, the disclosed embodiments can simultaneously implement the ability to charge the defibrillator unit 406 while reading and analyzing the heart rate. In this way, a shock can be delivered earlier if necessary. The user device 402 would have the processing power to accomplish both tasks, and this would also be possible because it can communicate in full duplex (i.e., bidirectional simultaneous communication) via USB-C while charging via the same cable. For example, in full duplex, a fully functional USB-C cable implementing USB 3.1 Gen. 2 can handle data transfer speeds of up to 10 Gbit / s. At the same time, because there is a separate line for charging (Vbus) within USB-C, one device can send charging power on one line in the cable while communicating bidirectionally at full speed on the other line in the same cable. In practice, the user device 402 can receive and interpret electrical signal information from the pads (e.g., pad 106) while charging. This allows for online-assisted, deeper signal analysis over a longer period than conventional AEDs, resulting in improved treatment.

[0039] In some embodiments, the application 404 can be kept focused without any interruption while performing rescue procedures, which can be achieved through close integration with the operating system of the user device 402. For example, the user can access the app without a lock code. Since the owner of the app may be a person in cardiac arrest, the app can be launched immediately, and if an AED device is connected, it can be launched without entering a lock code. For example, application 404 can: 1) automatically and immediately start up when a cable is connected or during app sync switching; 2) control power output via the USB port; 3) take over the screen completely without interference from the mobile phone's OS; 4) send and receive commands to and from the AED device without any timing interruptions or delays; 5) access full-duplex video and microphone / speaker; 6) access to read the battery level; 7) access GPS / NFC / BT etc; 8) access emergency call function and related functions (i.e., notify emergency contacts); and 9) stop the execution of energy-intensive apps or other apps, including apps that use the USB port, BT, NFC, video and speaker.

[0040] The server device 410 may include any combination of one or more of the following: a web server, a mainframe computer, a general-purpose computer, a personal computer, or other types of computing devices. The server device 410 may represent a distributed server that is remotely located and communicates over a communication network or over a dedicated network such as a local area network (LAN). The server device 410 may also include one or more backend servers for performing one or more aspects of the present disclosure. In some embodiments, the server device 108 may be the same as or similar to the server device 700 described later in relation to Figure 10.

[0041] As shown in Figure 4, the server device 410 may include an AED improvement module 412, an update module 414, and an AED tracking module 416. Furthermore, the server device 410 may be communicatively coupled to a database 418. In some embodiments, the AED improvement module 412 may include one or more models / algorithms trained via machine learning that can be used to continuously improve the performance of the AED and / or CPR over time. In some embodiments, the AED improvement module 412 may be configured to continuously receive performance data from the user device 402 and to retrain or update the model to reflect the newly received performance data. In some embodiments, the AED improvement module 412 may also have access to emergency health records and other external databases to acquire additional training data. In some embodiments, the AED improvement module 412 may be configured to analyze, retrain, and / or update various machine learning models related to AED performance, such as models that determine the length and level of the initial pulse, pad placement, body part detection, frequency of providing additional pulses, the amount of energy in each pulse, and various other decisions related to electrocardiogram (EKG) readings. In some embodiments, decisions may also be made based on other data related to the use of the mobile device interface, such as the time spent on different screens, the number of times the back function was used, and typical usage timings, in order to improve and optimize the user experience.

[0042] In some embodiments, the update module 414 may be configured to package or incorporate updated / retrained models from the AED improvement module 412, make them into a software update, and deliver this update to the user device 402. In some embodiments, the update may be received by the user device 402 via download from an application store. Furthermore, the AED tracking module 416 may be configured to track the location of each mobile AED 406. In some embodiments, the AED tracking module 416 may utilize GPS coordinates (or any positioning signal) obtained from the user device 402. In some embodiments, the AED tracking module 416 may allow the user to search for nearby mobile AEDs 406 via an application 404 on the user device 402.

[0043] Various system components such as modules 412-316 and 404a-n can be implemented using hardware and / or software configured to perform and execute processes, steps, or other functions in cooperation with them.

[0044] Figure 5 shows an exemplary pad for use with a mobile AED according to several embodiments of the present disclosure. The left side of Figure 5 (500a) shows the pad 505 before it is activated. The pad 505 comprises electrodes 508a-b, cloth 507a-b, and needles 506a-b. The cloth 507 may include neoprene or another suitable high-density flexible material. The needles 506a-b may include a metallic material and may be sharp enough to puncture the subject's skin 504 and curved to avoid puncturing the lungs 501. The pad 505 has two needles, but is not limited to any number of needles. The pad 505 is placed on the subject's skin 504 (dermis). Additional layers of the subject include the subcutaneous tissue 503, ribs 502, and lungs 501, as well as the heart 510. In some embodiments, the needle 506 can be attached at its blunt end to the underside of a plastic plate, and the plastic plate can be fixed to the pad 505 via a flexible joint, thus forming a flap ready for use in a tiled position. The tip of the needle is positioned inside the pad 505, near the adhesive surface, but not through it. In some embodiments, such a pad 505 may require a slightly thicker surface tissue to prevent spontaneous puncture. Furthermore, the plastic plates can be mounted together to ensure resistance and inertia so that the needle 506 is only actuated by a pressure exceeding a specific predetermined threshold, such as 10 kg. The needle 506 and the plastic plate may be covered with a cloth 507 to keep their area sterile. In this way, the needle 506 and the plate may be invisible to the user and appear as a ridge on the back of the pad when the needle 506 is not actuated. In some embodiments, markings on the ridge may indicate that the pad 505 contains a needle and that the pad 505 can be actuated and fixed by applying separate pressure thereto.

[0045] The right side of Figure 5 (500b) shows the pad 505 when the pad 505 is activated (for example, by pressing the button on the top of the pad 505 in the direction of arrow 509), with the needles 506a-b penetrating the skin and in the subcutaneous tissue (skin 503). A significant portion of the energy used when delivering an electric shock can be dissipated as it passes through the skin. To reduce energy needs and the amount of skin burns, the pad 505 with hook-shaped needles 506s-b can more efficiently direct the shock current subcutaneously and to the heart 510. This can reduce the energy requirements and thus reduce the potential size of the defibrillator unit 102. The needles 506a-b can also prevent the pad from loosening while attempting resuscitation. Conventional pads often loosen when the subject is damp with sweat, etc., or when lying in water, which prevents the adhesive on the pad from sticking to the chest. Because some rescuers may be reluctant to push needles into a patient's body, penetration may occur without the rescuer seeing when the needles 506a-b are incorporated into the pad 505. For example, the needles 506a-b can initially rest at a semi-vertical angle. In some embodiments, the pad 505 may be foldable. Furthermore, in some embodiments, the pad 505 may be foldable without the needles 506a-b.

[0046] The back of the pad 505 has an instruction to press firmly, which guides the needles 506a-b into the correct position. The needles 506a-b can have a curved shape, which means that the needles 506a-b will curve away from the chest, not penetrate it, and not cause pneumothorax. Instead, the needles 506a-b are located in the subcutaneous tissue 503, which helps to deliver the current to the heart 510 more easily and keep the pad 505 fixed. The needles 506a-b can be activated when greater resistance in the tissue is expected, for example, when a high BMI is recorded, or when high impedance (i.e., impedance exceeding a given threshold) is measured between the electrodes / pads, indicating a well-isolated patient. After several failed shocks, or when the energy in the phone is low, the program may also suggest activating the needles 506a-b.

[0047] Figure 6 shows a mobile AED power selection decision flow 600 according to some embodiments of the present disclosure. In some embodiments, the flow 600 can be executed via one or more processors on a mobile device (for example, via application 404 in Figure 4). Block 614 applies a proposed hierarchy of input priorities for selecting a power source for the defibrillator unit 102. In block 601, if the internal battery power is available, this is the highest priority power source. Another potential power source is, in block 602, a USB-C input or similar. In block 606, it is determined whether USB Power Delivery is available. If yes, processing proceeds to block 607, where it is determined whether the power source can supply more than 8W (however, this value is essentially illustrative and any value can be used). If yes, this is determined to be the second highest priority power source in block 614. In block 607, if it is determined that power source 602 cannot supply more than 4W of power, processing proceeds to block 608. Similarly, if there is no available USB Power Delivery power supply in block 606, processing proceeds to block 608. In block 608, it is determined whether the power supply supports USB-3.0 or similar. If yes, it is determined in block 614 to be the fifth highest priority power supply. If no, it is determined in block 615 to be an unacceptable power supply.

[0048] Another potential power source in block 603 is a secondary USB-C or similar power source. In block 609, it is determined whether USB Power Delivery is available. If yes, processing proceeds to block 610, where it is determined whether the power source can supply more than 8W (however, this value is essentially illustrative and any value can be used). If yes, it is determined in block 614 to be the third highest priority power source. In block 610, if it is determined that power source 602 cannot supply more than 4.5W, processing proceeds to block 611. Similarly, if there is no available USB Power Delivery power source in block 609, processing proceeds to block 611. In block 611, it is determined whether the power source supports USB-3.0 or similar. If yes, it is determined in block 614 to be the fourth highest priority power source. If no, it is determined in block 615 that it is not an acceptable power source.

[0049] Another potential power source in block 604 is a Qi charger. In block 612, it is determined whether the Qi charger power source in block 604 can supply more than, for example, 3W of power. If yes, it is determined to be the sixth highest priority power source in block 614. If no, it is determined to be an unacceptable power source in block 615. Another potential power source in block 605 is a reverse mobile phone that performs wireless charging. In block 613, it is determined whether the reverse wireless charging source can supply more than, for example, 4W of power. If yes, it is determined to be the lowest priority power source in block 614. If no, it is determined to be an unacceptable power source in block 615. If multiple power sources are available, in block 614, the highest priority power source is selected to power the defibrillator unit 102. In some embodiments, such a priority list is essentially illustrative and can be modified based on specific design choices.

[0050] Figure 7 shows a switching mobile controller decision flow 700 according to some embodiments of the present disclosure. Flow 700 can be performed to enable switching power to a new mobile device while defibrillation is in progress for a cardiac arrest patient, for example. In some embodiments, flow 700 can be performed via the Internet, WiFi, Bluetooth, or NFC to exchange status and history and transfer control to an application on a second mobile device. During flow 700, both mobile devices (e.g., mobile device 101 in Figure 1) can be plugged into the defibrillator unit 102 (via two charging ports). In some embodiments, flow 700 can also be performed using a defibrillator unit 102 having only a single charging port, which includes unplugging the first mobile device and plugging in the second mobile device after synchronization.

[0051] Process 700 can be executed while the mobile device 101 is plugged into and powered by the defibrillator unit 102. Furthermore, the defibrillator unit 102 may be in the process of performing defibrillation on the patient. In block 701, a determination is made as to whether the battery level of the mobile device 101 is low. In some embodiments, "low" can be defined as falling below a certain predetermined threshold, such as a standard mobile phone (e.g., less than 20% battery level). If the battery level is not low, the flow is reset. If the battery level is low, the process proceeds to block 702. Furthermore, before block 702 begins, the user may be prompted to switch mobile devices via application input in block 705.

[0052] In block 702, the mobile device 101 connected to the defibrillator unit 102 (e.g., via application 404) determines whether there is another mobile device 101 nearby with the same application installed by providing the user with a query that will be displayed on the user interface of the mobile device 101. If there is no such mobile device nearby, the process resets to block 702. If there is such a mobile device nearby, the process proceeds to block 703. In block 703, the first mobile device 101 detects whether another mobile device is nearby via NFC, Bluetooth, WiFi, etc. In some embodiments, all mobile devices with an application can search for nearby users with an application for cardiac arrest (or other emergency) situations and alert the user. For example, the application receiving the alert can read via USB, Bluetooth, or WiFi whether a supported AED device is nearby and send a signal back to the original application near the cardiac arrest. The message may include location (via GPS, WiFi), AED and mobile phone versions, and capacity (battery, etc.). Next, the alert-sending app can select the best nearby option and confirm the need for assistance from that specific mobile device. The owner of the alert-receiving app can then rush to provide help. The alert-sending app can track the rescuer's location on a map as they approach. This works whether the app is on a mobile phone, in a car, on a webpage, or on a personal computer. If assistance is needed depending on the circumstances (such as due to physical limitations), alerts via the app network can also help in receiving assistance.

[0053] If the first mobile device 101 cannot detect another nearby mobile device, the process resets to block 703. If the first mobile device 101 can detect another nearby mobile device, the process proceeds to block 704, initiating a procedure to switch the power to the defibrillator unit 102. Further details of such a procedure for switching the power are described in relation to Figure 8.

[0054] In some embodiments, when a connection is established between the original mobile device and the new mobile device, the app automatically starts on the second mobile phone. The app on the first phone connects to the second phone and requests a switch of control. The app on the first phone synchronizes its data with the second phone. The synchronization is verified. The app on the second phone asks the user to confirm the switch. If yes, the app on the second phone sends a message to the app on the first phone and initiates the switch. The app on the second phone asks the user to plug the USB cable into the phone (move it from the first phone). Once the cable is plugged into the app on the second phone, it checks that the connected device is the same as and in the same state as reported by the first phone. At this point, the app on the second phone takes control of the procedure and device and sends a message to the first phone about the successful handover.

[0055] Figure 8 shows a process 800 for switching the power supply of a defibrillator unit according to some embodiments of the present disclosure. In block 801, the transfer of data from the old mobile device to the new mobile device is initiated. The data to be transferred may include personal data known before the procedure was initiated (e.g., age, gender, weight, language, etc.), data points collected from the start of the current emergency (e.g., cardiac signals, number of shocks, timing, etc.), current status information (e.g., capacitor charge level, cardiac status, EMS connection, etc.), and software / firmware / hardware revisions and associated digital signatures. In block 802, once the data has been fully transferred, a handshake is performed between the mobile devices to verify the data. In block 803, once the data has been verified by the handshake, the new mobile phone is connected to the defibrillator unit 102. In block 804, the defibrillation procedure is continued on the new mobile device to assist the subject. In optional block 805, the system may fall back to the old mobile device if any error occurs during the defibrillation procedure. This can be done via inter-app communication.

[0056] Figure 9 shows a process 900 for charging a mobile AED according to some embodiments of the present disclosure. In some embodiments, the process 900 is performed by hardware in a user device 402. In some embodiments, the process 900 can be controlled by a command from the user device 402 ("Discharge / Do not discharge capacitor") or by the defibrillator unit itself based on a safety rule (e.g., "Discharge capacitor after 3 minutes for safety"). Existing AEDs have the design to discharge the capacitor after a shock as a precautionary measure. For mobile AEDs, where charging time is considerably long, the advantage of not discharging the capacitor is important for preparing for the next shock. The process 900 provides the advantage of faster charging by conserving the remaining energy of a capacitor (e.g., capacitor 207) in the defibrillator unit 102 and charging its top in preparation for the next charge. In block 901, the defibrillator unit 102 delivers a shock to a subject, such as a cardiac arrest patient. In block 902, the current is stopped after the completion of the first shock. In block 903, the energy remaining in the capacitor within the defibrillator unit is conserved. For example, after the current is stopped in block 902, the capacitor does not discharge rapidly as it normally would. In block 904, each time a subsequent shock is delivered to the subject, subsequent charging begins, starting from the already charged capacitor level.

[0057] Figure 10 shows the voltage (y-axis) as a function of time (x-axis) at an electrode / pad such as pad 505. This voltage is similar to the output voltage of capacitor 207, but after passing through the phase-switching capacitor. At the point indicated by the arrow, the safety discharge circuit typically kicks in, releasing the remaining energy into the environment. However, the disclosed embodiment is configured to retain the remaining charge in the defibrillator unit stored in the capacitor, reducing charging time and device size.

[0058] Figure 11 shows exemplary circuit architectures 1100 according to several embodiments of the present disclosure. In some embodiments, the circuit architecture 1100 can be a flyback converter charging circuit having a current-sensing bias circuit that can reduce the charging time. A typical flyback converter circuit can consist of a flyback transformer, which is supplied by a DC voltage source and is switched on and off to produce a high DC voltage output. The principle disclosed herein uses the circuit architecture 1100 to charge a high-voltage capacitor 1109 to 1900V, etc. Charging can be achieved using a charging controller 1103 that switches a MOSFET switch 1106 on and off, the switch 1106 is connected between the transformer 1107 and a ground reference. When the switch 1106 is on, current flows through the primary winding of the transformer 1107, and the current increases linearly with time as a function of the primary winding inductance of the transformer 1107. The current flowing through the transformer 1107 and the switch 1103 is monitored by a current-sensing resistor 1105. When the voltage across the current-sensing resistor 1105 increases beyond a threshold (e.g., 78mV), the charge controller 1103 shuts off switch 1106, and the energy stored in transformer 1107 is forced into the secondary circuit, diode 1108, and capacitor 1109. Switch 1106 is then turned back on, and charging continues.

[0059] In the embodiment described herein, the current-sensing resistor 1105 is configured such that the switch 1106 turns off when a predetermined amount of current (e.g., 2A) flows through the transformer 1107. This corresponds to an average current draw of 0.9A from the USB-C power supply 1101. However, due to the non-ideal parasitic capacitance of the flyback transformer 1107, as the voltage of the high-voltage capacitor 1109 increases, some of the energy from the USB-C power supply 1101 is stored in the transformer 1107 and then fed back to the USB-C power supply 1101. This stored energy may be proportional to the voltage of the high-voltage capacitor 1109. Potential problems that may occur include: 1) as the capacitor 1109 is charged, the average current draw from the USB-C power supply 1101 decreases to 0.6A-0.7A; and 2) as the capacitor voltage increases, the charging efficiency decreases, resulting in longer charging times.

[0060] The disclosed embodiment addresses these issues of reduced current draw by raising the current limit of transformer 1107 above 2A and making it adjustable as the voltage across capacitor 1109 increases. This is achieved by biasing the voltage across current sensing resistor 1105 using sensing line bias circuit 1104. Effectively, the bias circuit 1104 allows higher currents to flow above 2A before the voltage across current sensing resistor 1105 reaches 78mV. Furthermore, the bias circuit 1104 is controlled by a pulse-width modulated waveform from microcontroller 1102, the pulse width of which is adjusted in software. This makes it possible to adjust the bias circuit 1104 on the fly while capacitor 1109 is charging. Ultimately, this makes it possible to maximize the current draw from USB-C power supply 1101 throughout the entire charging period, and more importantly, reduce the charging time.

[0061] Figure 12 shows an exemplary process 1200 for using a mobile AED according to some embodiments of the present disclosure. In some embodiments, process 1200 can be performed by a user device (e.g., user device 402 and / or user device 101). In some embodiments, the execution of process 1200 can be assisted by a user interacting with the user device. For example, in response to a person experiencing sudden cardiac arrest, a bystander, friend, or other individual can perform process 1200 using the mobile AED of the present disclosure and an application on the user device (e.g., application 404). In block 1201, user device 402 can detect the AED connection (e.g., via application 404). For example, the user can connect the defibrillator unit 102 to the user device by locating the mobile AED (e.g., defibrillator unit 102) and plugging in the connection cable. The user device can detect that the defibrillator unit 102 has been connected, for example, via application 404. In block 1202, the user device 402 can open application 404. In some embodiments, application 404 can be opened automatically in response to detection of a defibrillator connection, and in some embodiments, the application can be opened manually by the user.

[0062] In block 1203, application 404 can analyze data associated with a subject (e.g., a person who has recently experienced cardiac arrest). For example, application 404 can store demographic and health information associated with a subject by pre-enabling access for the subject to input self-descriptive information. Application 404 can store various types of information such as height, weight, age, blood pressure, previous EKG assessments, and medical history. In some embodiments, application 404 can be configured to utilize machine learning algorithms to analyze subject information and make various decisions related to the remaining steps for administering an AED. In some embodiments, the analysis can be performed outside of the user device 402; for example, subject data can be transmitted and processed by a server (e.g., server 410), and the results of the processing can be transmitted to the user device 402 to influence the treatment.

[0063] In block 1204, application 404 can analyze various wearable data, such as biometric authentication data, obtained from wearable devices worn by the subject. This may include smartwatches or other wearable devices. Wearable data may include, but is not limited to, various data such as heart rate and blood oxygen saturation.

[0064] In block 1205, application 404 can detect pad placement. In some embodiments, application 404 can be configured to detect whether a human body is connected between two pads based on electrical measurements (e.g., current) from pads 106a-b. In some embodiments, detecting pad placement may include application 404 being able to detect the amount of current flowing through the subject between the pads when the pads (e.g., pads 106a-b) are placed on the subject's body (e.g., under the subject's right clavicle and under the subject's left armpit). Based on the intensity of the detected current, application 404 can determine whether the pads are too far apart or too close together. For example, application 404 can utilize a threshold current range and compare the detected current to a threshold. If the detected current is above or below the threshold, application 404 can display a warning on the device to the user recommending that the pads be moved closer together or further apart.

[0065] In block 1206, application 404 can be configured to determine a shock pattern to be administered to a subject. In some embodiments, determining a shock pattern may include application 404 using a machine learning model to analyze data associated with the subject (e.g., height, weight, pad placement, EKG measurements, etc.) and wearable data to output a shock pattern to resuscitate the subject. In some embodiments, application 404 may acquire and analyze data via connected pads (e.g., acting as an EKG machine) before determining a shock pattern, and then use the acquired data to determine a shock pattern. For example, a machine learning model can be trained to determine a shock pattern based on data such as pulse rate (both frequency and variability), all types of cardiac rhythms, EKG composite wave composition, ST elevation (e.g., vertical distance within EKG trace and baseline), deficiency, and signs of myocardial ischemia, ventricular tachycardia, and ventricular fibrillation. Application 404 may also be configured to detect that certain respiratory patterns occurring in association with ventricular premature contractions may be trigger events. In some embodiments, the machine learning model may include a neural network having multiple nodes trained to map the aforementioned types of health data to various factors in the shock pattern (e.g., duration, timing, and energy level). In some embodiments, application 404 may be configured to estimate the subject's body fat percentage based on electrical measurements received from pads 106a-b, which can then be used in determining the electrical shock pattern. In some embodiments, the machine learning model may also be configured to predict whether the subject will achieve “return of spontaneous circulation” (ROCS), which may include the resumption of sustained perfusionable cardiac activity. This can be predicted by analyzing respiration, movement, pulse, and blood pressure.

[0066] In some embodiments, the shock pattern may include the duration and level of multiple energy pulses (e.g., energy levels in joules). In some embodiments, the initial pulse to a person in cardiac arrest may be important for resuscitation. In block 1206, application 404 can cause the defibrillator unit 102 to deliver a determined shock pattern to the person. Delivering the shock pattern may involve using the power supply of the user device 402 to power a circuit (e.g., circuit 200) within the defibrillator unit 102. A possible advantage of using the power circuit in a mobile device is that it can provide a less expensive device, which will ultimately make it more accessible to more people and increase its adoption rate. In some embodiments, application 404 may be configured to warn nearby people before the electric shock pattern is delivered. For example, while the electric shock is being delivered, application 404 may use the speaker and user interface of device 101 to sound and display a warning to move away from the person. This can prevent the current from shocking or harming other people. In some embodiments, after the electric shock pattern is completed, application 404 may sound an alarm displaying another message indicating that the alarm has been cleared.

[0067] In some embodiments, the mobile AED can be configured to operate as an EKG for a period of time before determining the shock pattern in block 1207. The application can be configured to receive data and EKG measurements and make various decisions related to the shock pattern based on these measurements. In some embodiments, once any delivered shock pattern is completed, all data / information associated with the process can be transmitted from the user device 402 to the server 410, specifically to the AED improvement module 312. The AED improvement module 412 can use the received information to update and / or retrain any machine learning models related to determining shock patterns and pad placement based on both demographic and health data and EKG measurements. In some embodiments, a large number of mobile AEDs can be utilized, thus providing a large and rich dataset, and algorithms and models related to AED performance can be continuously updated on this dataset. Due to the nature of operation of this disclosure (utilizing an application interface in a standard operating system to administer the AED), this makes it possible to continuously update and improve AED performance.

[0068] In some embodiments, process 1200 can be performed in accordance with a video assistant and / or a voice assistant. For example, application 404 can be configured to utilize any voice assistant function on the device (e.g., Alexa®, Google Assistant®, Siri®, in-vehicle voice system, etc.). For example, if a person opens the app but does not know how to administer an AED to a patient, the person can communicate with application 404 via the voice assistant and ask for help. In some embodiments, the application can connect to a professional via video and activate the camera on the mobile device 402. In some embodiments, a team of professionals capable of handling the inflow of video connections can be assembled. Each professional can have knowledge of how to operate the mobile AED 406, thereby providing quick and effective assistance and reliable information in an emergency. This may be more beneficial than being able to connect to a doctor or similar person because there are no availability issues. In some embodiments, application 404 can also enable the user to immediately connect to law enforcement and / or paramedics. In some embodiments, GPS and medical data associated with a person can be immediately transferred to law enforcement or paramedics via application 404, in response to notification to the law enforcement or paramedics through application 404. This provides paramedics with valuable information in advance, thereby potentially saving them valuable time when they arrive at the scene.

[0069] In some embodiments, application 404 can also assist in performing CPR in conjunction with applying a shock pattern. In some embodiments, application 404 can be configured to detect the strength of the pressure an individual is applying to the patient's chest cavity by analyzing the force applied to pads 106a-b. Application 404 can provide the user with instructions such as "press harder" or "press lighter."

[0070] Figure 13 shows an exemplary server device 1300 that can be used in the system of Figure 4 according to some embodiments of the present disclosure. The server device 1300 can perform a variety of functions and processes as described herein. The server device 1300 can be implemented on any electronic device that runs a software application derived from compiled instructions, including, but not limited to, personal computers, servers, smartphones, media players, electronic tablets, game consoles, email devices, etc. In some embodiments, the server device 1300 may include one or more processors 1302, volatile memory 1304, non-volatile memory 1306, and one or more peripheral devices 1308. These components can be interconnected by one or more computer buses 1310.

[0071] Processor 1302 may use any known processor technology, including, but is not limited to, graphics processors and multicore processors. Processors suitable for executing instruction programs may include, for example, both general-purpose microprocessors and dedicated microprocessors, as well as a single processor or one of several processors or cores of any type of computer. Bus 1310 may be any known internal or external bus technology, including, but is not limited to, ISA, EISA, PCI, PCI Express, NuBus, USB, Serial ATA, or FireWire. Volatile memory 1304 may include, for example, SDRAM. Processor 1302 may receive instructions and data from read-only memory or random access memory or both. Essential elements of a computer may include a processor for executing instructions and one or more memories for storing instructions and data.

[0072] The non-volatile memory 1306 may include, for example, semiconductor memory devices such as EPROMs, EEPROMs, and flash memory devices, magnetic disks such as internal hard disks and removable disks, magneto-optical disks, and CD-ROMs and DVD-ROM disks. The non-volatile memory 1306 can store various computer instructions, including operating system instructions 1312, communication instructions 1315, application instructions 1316, and application data 1317. The operating system instructions 1312 may include instructions for implementing an operating system (e.g., MacOS®, Windows®, or Linux®). The operating system may be multi-user, multi-processing, multi-tasking, multi-threaded, real-time, etc. The communication instructions 1315 may include software for implementing network communication instructions, such as TCP / IP, HTTP, Ethernet, telephony, and other communication protocols. Application instruction 1316 may include instructions for delivering a shock pattern using a mobile AED, instructions for connecting to law enforcement, instructions for displaying instructions for delivering a shock pattern using a mobile AED, and instructions for performing self-rescue actions in accordance with the systems and methods disclosed herein. For example, application instruction 1316 may include instructions for the components 110-112 described above in conjunction with Figure 1.

[0073] Peripheral device 1308 can be included within server device 1300 or can be operablely coupled to communicate with server device 1300. Peripheral device 1308 may include, for example, a network subsystem 1318, an input controller 1320, and a disk controller 1322. The network subsystem 1318 may include, for example, an Ethernet port for a WiFi adapter. The input controller 1320 may be any known input device technology, including, but not limited to, a keyboard (including a virtual keyboard), a mouse, a trackball, and a touch-sensitive pad or display. The disk controller 1322 may include one or more mass storage devices for storing data files, such devices including magnetic disks, magneto-optical disks, and optical disks, such as internal hard disks and removable disks.

[0074] Figure 14 shows an exemplary computing device 1400 that can be used in the systems of Figure 1 and / or Figure 3 according to some embodiments of the present disclosure. In some embodiments, device 1400 may be a user device 101. The exemplary user device 1400 may include a memory interface 1402, one or more data processors, an image processor, a central processing unit 1404, and / or a secure processing unit 1405, and a peripheral subsystem 1406. The memory interface 1402, one or more processors 1404, and / or secure processors 1405, and / or peripheral subsystem 1406 may be separate components or may be integrated into one or more integrated circuits. The various components within the user device 1400 may be connected by one or more communication buses or signal lines.

[0075] Sensors, devices, and subsystems can be coupled to the peripheral subsystem 1406 to facilitate multiple functions. For example, a motion sensor 1410, a light sensor 1412, and a proximity sensor 1414 can be coupled to the peripheral subsystem 1406 to facilitate orientation, illumination, and proximity functions. Other sensors 1416 can also be connected to the peripheral subsystem 1406 to facilitate related functions, such as a Global Navigation Satellite System (GNSS) (e.g., a GPS receiver), a temperature sensor, a biometric sensor, a magnetometer, or other sensing devices.

[0076] The camera subsystem 1420 and optical sensor 1422, for example, a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) optical sensor, can be used to enhance camera functions such as recording photographs and video clips. The camera subsystem 1420 and optical sensor 1422 can also be used to collect images of a user for use during user authentication, for example, by performing facial recognition analysis.

[0077] Communication functions can be facilitated through one or more wired and / or wireless communication subsystems 1424, which may include radio frequency receivers and transmitters and / or optical (e.g., infrared) receivers and transmitters. For example, Bluetooth (e.g., Bluetooth Low Energy (BTLE)) and / or WiFi communication as described herein can be handled by the wireless communication subsystem 1424. Specific designs and embodiments of the communication subsystem 1424 may depend on a communication network, and the user device 1400 is intended to operate over this communication network. For example, the user device 1400 may include a communication subsystem 1424 designed to operate over a GSM network, a GPRS network, an EDGE network, a WiFi or WiMAX network, and a Bluetooth® network. For example, the wireless communication subsystem 1424 may include a hosting protocol so that the device 1400 can be configured to act as a base station for other wireless devices and / or provide WiFi services.

[0078] The audio subsystem 1426 can be coupled to the speaker 1428 and microphone 1430 to facilitate voice-enabled functions such as speaker recognition, voice duplication, digital recording, and telephone functions. The audio subsystem 1426 can be configured, for example, to facilitate the processing of voice commands, voiceprint recognition, and voice authentication.

[0079] The I / O subsystem 1440 may include a touch-surface controller 1442 and / or other input controllers 1444. The touch-surface controller 1442 may be coupled to a touch-surface 1446. The touch-surface 1446 and the touch-surface controller 1442 may detect their contact and movement or interruption using, for example, any of several touch sensitivity technologies, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements to determine one or more points of contact with the touch-surface 1446.

[0080] Other input controllers 1444 can be coupled to other input / control devices 1448, such as one or more buttons, rocker switches, thumbwheels, infrared ports, USB ports, and / or pointer devices such as styluses. One or more buttons (not shown) may include up / down buttons for adjusting the volume of speaker 1428 and / or microphone 1430.

[0081] In some embodiments, the touchscreen 1446 can be unlocked by pressing a button for a first duration, and the user device 1400 can be powered on or off by pressing a button for a second duration longer than the first duration. By pressing a button for a third duration, voice control or voice commands, or modules can be activated, allowing the user to speak commands into the microphone 1430 and have the device execute the spoken commands. The user can customize the functionality of one or more buttons. The touchscreen 1446 can also be used to implement, for example, virtual buttons or soft buttons and / or a keyboard.

[0082] In some embodiments, the user device 1400 can present recorded audio files and / or video files such as MP3 files, AAC files, and MPEG files. In some embodiments, the user device 1400 can include the functionality of an MP3 player such as an iPod®. Therefore, the user device 1400 can include an iPod-compatible 36-pin connector and / or 8-pin connector. Other input / output devices and control devices can also be used.

[0083] The memory interface 1402 can be coupled to the memory 1450. The memory 1450 may include one or more magnetic disk storage devices, one or more optical storage devices, and / or high-speed random access memory such as flash memory (e.g., NAND, NOR) and / or non-volatile memory. The memory 1450 can store operating systems 1452 such as Darwin, RTXC, LINUX, UNIX®, OS X®, Windows, or embedded operating systems such as VxWorks.

[0084] The operating system 1452 may include instructions for handling basic system services and instructions for performing hardware-dependent tasks. In some embodiments, the operating system 1452 may be a kernel (e.g., a UNIX kernel). In some embodiments, the operating system 1452 may include instructions for performing voice authentication.

[0085] Memory 1450 can also store communication instructions 1454 to facilitate communication with one or more additional devices, one or more computers and / or one or more servers. Memory 1450 may include graphic user interface instructions 1456 to facilitate graphic user interface processing, sensor processing instructions 1458 to facilitate sensor-related processes and functions, telephone instructions 1460 to facilitate telephone-related processes and functions, electronic messaging instructions 1462 to facilitate electronic messaging-related processes and functions, web browsing instructions 1464 to facilitate web browsing-related processes and functions, media processing instructions 1466 to facilitate media processing-related functions and processes, GNSS / navigation instructions 1468 to facilitate GNSS and navigation-related processes and instructions, and / or camera instructions 1470 to facilitate camera-related processes and functions.

[0086] Memory 1450 can store application (or "app") instructions and data 1472, such as instructions for the app described above in relation to Figures 1 to 12. Memory 1450 can also store other software instructions 1474 for various other software applications in appropriate locations on device 1400.

[0087] The above specification has described specific embodiments. However, those skilled in the art will understand that various modifications and changes can be made without departing from the scope of the invention, as described in the following claims. For example, although the invention is described and illustrated in relation to a school, it is not intended to be limited in that way. Accordingly, this specification and drawings should be considered illustrative rather than restrictive, and all such modifications are intended to be within the scope of this teaching.

[0088] No benefit, advantage, solution to a problem, or any element that may produce or make more prominent any benefit, advantage, or solution should be construed as an essential, necessary, or required feature or element of any or all claims. The present invention is defined solely by the appended claims and all equivalents of the issued claims, including any amendments made during the pendency of this application.

[0089] This abstract of the disclosure is provided to enable readers to quickly confirm the nature of the technical disclosure. This abstract of the disclosure is submitted with the understanding that it is not to be used to interpret or limit the claims or their meaning. Furthermore, it is found that in the detailed description above, various features are grouped together in various embodiments for the purpose of simplifying the disclosure. This method of disclosure should not be interpreted as reflecting an intention that the claimed embodiments require more features than those expressly described in each claim. Rather, the subject matter of the invention lies in fewer features than all the features of a single disclosed embodiment, as reflected in the following claims. Accordingly, the following claims are incorporated into the detailed description, and each claim stands alone as separately claimed subject matter.

[0090] It should be understood that the subject matter disclosed is not limited in its application to the structural details and component arrangements described in the following description or shown in the drawings. Other embodiments of the subject matter disclosed are possible and can be carried out and implemented in various ways. It should also be understood that the expressions and terms used herein are for illustrative purposes only and should not be considered limiting. Accordingly, those skilled in the art will understand that the concepts underlying this disclosure can be readily used as the basis for designing other structures, methods and systems to accomplish some of the purposes of the subject matter disclosed. Accordingly, it is important that the claims be considered to include such equivalent configurations, as long as they do not deviate from the spirit and scope of the subject matter disclosed.

[0091] While various embodiments have been described above, it should be understood that they are presented as examples only and not as limitations. Those skilled in the art will see that various modifications of form and detail can be made without departing from the spirit and scope. Indeed, after reading the above description, the methods for carrying out alternative embodiments will be obvious to those skilled in the art. For example, other steps may be provided or eliminated from the described flow, other components may be added to the described system, or other components may be removed from the described system. Therefore, other embodiments are within the scope of the following claims.

[0092] Furthermore, please understand that any diagrams emphasizing functionality and benefits are presented for illustrative purposes only. Each disclosed method and system is sufficiently flexible and configurable to be used in ways other than those shown.

[0093] The term “at least one” is used most often in this specification, claims and drawings, but terms such as “a,” “an,” “the,” and “said” also mean “at least one” or “the said at least one” in this specification, claims and drawings.

[0094] Finally, the applicant intends that only claims containing the explicit phrase “means for” or “steps for” should be interpreted under 112(f) of the U.S. Patent Act. Claims that do not explicitly contain the phrases “means for” or “steps for” should not be interpreted under 112(f) of the U.S. Patent Act. [Explanation of Symbols]

[0095] 100 Mobile AED system, 101 Device, 102 Defibrillator unit, 103 Connection, 104 Power bank, 105 Wiring, 106a Pad, 106b Pad, 107 Video assistant expert, 108 Server device, 200 Circuit, 201 Charger, 202 Switch, 203 Switch, 204 Inductor, 205 Resistor, 206 Pass-through resistor, 207 Capacitor, 400 System, 402 User device, 402a User device, 402n User device, 404 Application, 404a Application, 404n Application, 406 Mobile AED, 408 Network, 410 Server device, 412 AED improvement module, 414 Update module, 416 AED tracking module, 418 Database, 500a Left side of Figure 5, 500b Right side of Figure 5, 501 Lung, 502 Ribs, 503 Subcutaneous tissue, skin, 504 skin, 505 pad, 506a needle, 506b needle, 507a cloth, 507b cloth, 508a electrode, 508b electrode, 509 arrow, 510 heart, 600 mobile AED power selection decision flow, 700 switching mobile controller decision flow, 1100 circuit architecture, 1101 USB-C power supply, 1102 microcontroller, 1103 charge controller, 1104 sensing line bias circuit, 1105 current sensing resistor, 1106 MOSFET switch, 1107 transformer, 1108 diode, 1109 high voltage capacitor, 1200 process, 1300 server device, 1302 processor, 1304 volatile memory, 1306 non-volatile memory, 1308 peripherals, 1310 computer bus, 1312 Operating System Instructions, 1315 Communication Instructions, 1316 Application Instructions, 1317 Application Data, 1318 Network Subsystem, 1320 Input Controller, 1322 Disk Controller, 1400 Computing Devices, 1402 Memory Interface, 1404 Processor, 1405 Secure Processor, 1406 Peripheral Subsystem, 1410 Motion Sensor, 1412 Light Sensor, 1414 Proximity Sensor, 1416 Other Sensors, 1420Camera subsystem, 1422 Optical sensor, 1424 Wireless communication subsystem, 1426 Audio subsystem, 1428 Speaker, 1430 Microphone, 1440 I / O subsystem, 1442 Touchscreen controller, 1444 Input controller, 1446 Touchscreen, 1448 Other input / control devices, 1450 Memory, 1452 Operating system, 1454 Communication commands, 1456 Graphic user interface commands, 1458 Sensor processing commands, 1460 Telephone commands, 1462 Electronic messaging commands, 1464 Web browsing commands, 1466 Media processing commands, 1468 GNSS / navigation commands, 1470 Camera commands, 1472 Application commands and data, 1474 Other software commands

Claims

1. A mobile defibrillator (AED) device, A mobile AED unit is provided, configured to be operablely connected to a device capable of running an application. The application is configured to access at least one of the subject's heart rate or blood oxygen saturation, as measured by a wearable device worn by the subject during defibrillation. The AED unit is configured to include one or more electrodes and to measure the respiratory data of the subject. The device, via one or more processors running on the device, The steps include detecting the connection of the mobile AED unit to the device, A step of detecting that one or more of the electrodes are connected to the subject, The steps include receiving the electrocardiogram (EKG) measurement values ​​of the subject recorded by the electrodes, The steps include receiving measured respiratory data related to the respiratory movement of the subject's chest from the AED unit, The steps include receiving wearable data from the wearable device worn by the subject after the mobile AED unit has been connected to the device, including at least one of the subject's heart rate or blood oxygen saturation measured by the wearable device and associated with the subject; The steps include: analyzing the respiratory data in order to determine the respiratory pattern of the subject; The steps include determining whether the subject requires an electric shock based on the received EKG measurement, the wearable data including at least one of the heart rate or blood oxygen saturation, and the determined breathing pattern. Based on the received EKG measurement, the wearable data including at least one of the heart rate or the blood oxygen saturation, and the determined breathing pattern, shock pattern factors are determined, and the shock pattern factors include duration, time interval, and energy level. Based on the above determination, the steps include administering the electric shock to the subject via the mobile AED using the determined shock pattern factor, A mobile defibrillator (AED) device configured to perform the following actions.

2. The AED device according to claim 1, wherein the step of determining that the subject requires an electric shock includes the step of analyzing the EKG measurement value and the step of detecting a dangerous rhythm.

3. The AED device according to claim 2, wherein the step of detecting a dangerous rhythm includes the step of detecting at least one of rapid ventricular tachycardia or ventricular fibrillation.

4. The aforementioned device The current flowing between one or more electrodes is measured. Based on the measured current, a recommendation is displayed to change the distance between one or more electrodes. The AED device according to claim 1, further configured as follows.

5. The step of determining whether the subject requires an electric shock based on the received EKG measurement values, the wearable data, and the determined breathing pattern is: A step of using a neural network having multiple nodes to map at least one of the EKG measurements, the wearable data, and the determined breathing pattern to a shock pattern factor, wherein the shock pattern factor includes duration, time interval, and energy level. The AED device according to claim 1, including the following:

6. The AED device according to claim 5, wherein the neural network is configured to estimate the likelihood of the subject achieving spontaneous return of circulation (ROCS) based on the respiratory data and the wearable data.

7. The AED device according to claim 1, wherein the step of receiving the EKG measurement includes a step of determining at least one of pulse rate, EKG composite wave configuration, ST elevation, and deficiency.

8. The AED device according to claim 1, wherein the step of administering the electric shock to the subject includes the step of using the power supply of the device to supply power to the circuits in one or more electrodes.