Automatic external defibrillator management method and system and storage medium

Abstract

The invention discloses an automatic external defibrillator management method and system and a storage medium, and the method comprises the steps: a cloud management system which operates at a cloud platform end receives an equipment binding request, and the equipment binding request is sent by a user terminal; the equipment binding request comprises equipment state information generated by performing self-inspection on the to-be-bound automatic external defibrillation; the cloud platform end analyzes the equipment state information, and binds the user terminal as a management terminal of the automatic external defibrillator under the condition that the equipment state information is normal; and at least opening the management authority of the equipment application data and the equipment state data of the automatic external defibrillator to the management terminal. According to the invention, the management efficiency of the automatic external defibrillator can be improved.

Description

Technical Field

[0001] This application relates to the field of medical technology, specifically to an automated external defibrillator (AED) management method, system, and storage medium. Background Technology

[0002] An automated external defibrillator (AED) is a portable medical device that can be used by professionals or non-professionals to resuscitate patients suffering from sudden cardiac arrest. AEDs are currently widely used in public places such as companies, schools, and train stations, and an increasing number of households are also choosing to install them.

[0003] Automated external defibrillators (AEDs) are emergency medical devices, therefore, installation, use, and maintenance all require specialized personnel. To ensure continued proper functioning, AEDs need regular inspections, including checking the functionality of the AED itself and the condition of vital accessories such as batteries and electrode pads. In current technology, in scenarios with concentrated AED use (such as hospitals), professional personnel conduct batch inspections to check the functionality and condition of accessories. However, in home or office settings, where AEDs are randomly distributed and at relatively low density, the aforementioned professional inspection method is extremely inefficient and unsuitable for these scenarios. Existing remote management systems primarily employ a centralized approach, where system administrators manage all AEDs centrally. This allows for batch management (e.g., unified software upgrades) but fails to provide differentiated management for different AEDs in home or office settings, nor does it enable comprehensive inspections or full lifecycle management. Summary of the Invention

[0004] In view of the above problems, this application provides an efficient method for managing automated external defibrillators (AEDs) to be applicable to AED management in discrete distribution scenarios such as homes or companies.

[0005] To achieve the above objectives, this application provides a method for managing an automated external defibrillator (AED), the method comprising:

[0006] The cloud management system running on the cloud platform receives a device binding request. The device binding request is sent by the user terminal and includes the device status information generated by the automated external defibrillator to be bound during self-testing.

[0007] The cloud platform analyzes the device status information. If the device status information is normal, it binds the user terminal to the management terminal of the automated external defibrillator (AED). It also grants the management terminal at least management permissions for the AED's device application data and device status data, including defibrillation emergency data and / or vital signs data. The device status data includes battery status data and / or electrode pad status data.

[0008] Furthermore, the user terminal obtains the device status information by identifying or receiving a carrier medium, which is generated during the self-test; the carrier medium includes any one of the following: QR code, barcode, NFC tag, Bluetooth tag, and RFID tag.

[0009] Furthermore, the user terminal logs into the cloud management system through a locally installed APP or mini-program platform.

[0010] Furthermore, the device binding request also includes the network type information of the automated external defibrillator; the process of binding the user terminal as the management terminal of the automated external defibrillator also includes the following steps:

[0011] The cloud platform identifies the network type information and presents corresponding network configuration guidance on the user terminal according to the obtained network type. The network type includes any one of Bluetooth, 4G, 5G, 6G, and WIFI.

[0012] Furthermore, after the automated external defibrillator (AED) network is configured, the cloud platform tests the network transmission connection between the AED and the cloud platform.

[0013] Furthermore, the device status information includes the device sequence information of the automated external defibrillator;

[0014] The process of binding the user terminal as the management terminal of the automated external defibrillator further includes the following steps:

[0015] The cloud platform acquires the user's personal information from the management terminal, as well as the operation training confirmation information of the automated external defibrillator; and generates an electronic warranty card by combining the user's personal information, the device serial information, and the operation training confirmation information.

[0016] Furthermore, it also includes the step of: the cloud platform controlling the management terminal to present the operation training information of the automated external defibrillator, the operation training information including any one or more combinations of text, pictures, and videos;

[0017] The operation training confirmation information is generated after the operation training information is presented and after confirmation of training is received on the management terminal.

[0018] Furthermore, when the cloud management system receives a device binding request, it also includes:

[0019] The cloud management system presents a first-time power-on or non-first-time power-on button on the user terminal; in response to the operation event of the first-time power-on or non-first-time power-on button, it presents a binding operation guide for the first-time power-on or a binding operation guide for non-first-time power-on on the user terminal.

[0020] Furthermore, the management authority over the device application data includes presenting the device application data on the management terminal, including presenting the numerical values ​​and / or data trend change graphs of the device application data, wherein the data trend change graphs include any one of bar charts, scatter plots, line charts, and pie charts.

[0021] Furthermore, the data trend chart includes:

[0022] Analyze the changes in the time span of the recorded time points of multiple device application data, as well as the changes in the numerical range of the device application data;

[0023] Based on the changes in the time span and the changes in the numerical range, the coordinate values ​​of the time axis and the numerical axis of the data trend change graph are dynamically adjusted so that the data trend change graph is displayed in an appropriate size within the area enclosed by the time axis and the numerical axis.

[0024] Furthermore, it also includes the following steps:

[0025] Generate and share a shared medium with other user terminals to collaboratively manage the bound automated external defibrillator.

[0026] Furthermore, generating and sharing a shared medium for collaborative management of the bound automated external defibrillator with other user terminals includes:

[0027] The management terminal initiates the sharing process and requests the cloud platform to generate a sharing medium for collaborative management of the bound automated external defibrillator;

[0028] The management terminal sends the shared medium to other selected user terminals and receives sharing acceptance information from the other user terminals;

[0029] In response to the sharing acceptance information, the cloud platform synchronously transmits some management permissions of the bound automated external defibrillator to the other user terminals until the management terminal ends the sharing process.

[0030] Furthermore, after the management terminal sends the shared medium to the selected other user terminals, the process also includes:

[0031] Determine whether the other user terminal is a registered user; if not, push a user registration link to the other user terminal.

[0032] Furthermore, the sharing medium includes any one of the following: QR code, barcode, web link, NFC tag, Bluetooth tag, and RFID tag.

[0033] Furthermore, it also includes the following steps:

[0034] The management terminal generates and sends a transfer medium to other user terminals to transfer the bound automated external defibrillator.

[0035] Furthermore, the management terminal generates and sends a transfer medium for transferring the bound automated external defibrillator to other user terminals, including:

[0036] The management terminal selects other user terminals of the automated external defibrillator (AED) that are bound to it for takeover, and generates the handover medium for the other user terminals.

[0037] In response to the other user terminal accepting the acceptance event for the handover medium, the cloud platform binds the other user terminal as a new management terminal and deletes all management permissions of the original management terminal.

[0038] Furthermore, the management terminal shall be granted at least one or more of the following management permissions: user registration, device map positioning, device operation training, service rights, fault diagnosis, and device unbinding.

[0039] Furthermore, the self-test includes a self-test performed upon first power-on after installation or a self-test performed periodically by the automated external defibrillator.

[0040] To address the aforementioned technical problems, this application also provides another technical solution:

[0041] A cloud-based management system for an automated external defibrillator (AED), running on a cloud platform, includes:

[0042] The device binding module is used to respond to a device binding request sent by a user terminal. The device binding request includes device status information generated by the automated external defibrillator (AED) during self-testing. If the device status information is normal, the module binds the user terminal as the management terminal of the AED and grants the management terminal at least management permissions for the device application data and device status data of the AED. The device application data includes defibrillation emergency data and / or vital signs data; the device status data includes battery status data and / or electrode pad status data.

[0043] Furthermore, the user terminal obtains the device status information by identifying or receiving a carrier medium, which is generated during the self-test; the carrier medium includes any one of the following: QR code, barcode, NFC tag, Bluetooth tag, and RFID tag.

[0044] Furthermore, the user terminal logs into the cloud management system through a locally installed APP or mini-program platform.

[0045] Furthermore, the device binding request also includes the network type information of the automated external defibrillator;

[0046] The binding module is also used to identify the network type information and present the corresponding network configuration guidance on the user terminal according to the obtained network type. The network type includes any one of Bluetooth, 4G, 5G, 6G, and WIFI.

[0047] Furthermore, the binding module is also used to obtain the user's personal information from the user terminal and the operation training confirmation information of the automated external defibrillator; and to generate an electronic warranty card by combining the user's personal information, the device sequence information and the operation training confirmation information.

[0048] Furthermore, during the user terminal device binding request process, the cloud management system presents a first-time power-on or non-first-time power-on button on the user terminal; in response to the operation event of the first-time power-on or non-first-time power-on button, it presents a binding operation guide for first-time power-on or a binding operation guide for non-first-time power-on on the user terminal.

[0049] Furthermore, the management authority for the device application data includes presenting the device application data on the management terminal, including presenting the numerical values ​​and / or data trend graphs of the device application data, wherein the data trend graphs include any one of bar charts, scatter plots, line graphs, and pie charts.

[0050] Furthermore, it also includes:

[0051] The device sharing module is used to respond to the device sharing request of the management terminal and generate a sharing medium for collaborative management of the automated external defibrillator that has been bound to the management terminal.

[0052] Furthermore, the device sharing module is also used to respond to the sharing acceptance information and synchronously transmit some management permissions of the bound automated external defibrillator to the other user terminals until the management terminal ends the sharing process.

[0053] Furthermore, the device sharing module is also used to determine whether the other user terminal is a registered user; if not, it pushes a user registration link to the other user terminal.

[0054] Furthermore, it also includes:

[0055] The device handover module is used to respond to the device handover request from the management terminal and generate a handover medium for handing over the bound automated external defibrillator to a designated user terminal.

[0056] Furthermore, the device handover module is also used to respond to the other user terminal accepting the acceptance event for the handover medium, bind the other user terminal as a new management terminal, and delete all management permissions of the original management terminal.

[0057] To address the aforementioned technical problems, this application also provides another technical solution:

[0058] A computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, the automated external defibrillator management method described in any one of the above technical solutions is performed.

[0059] Unlike existing technologies, this invention offers at least the following technical advantages: It employs a three-in-one online management model integrating a cloud platform, a management terminal (i.e., the AED management system), and the AED device itself. AED administrators can log in to the cloud platform via the management terminal to manage their bound AEDs. Administrators can manage their bound devices anytime, anywhere. Therefore, administrators can manage their bound AEDs flexibly and efficiently, making it particularly suitable for application scenarios where AEDs are geographically dispersed, such as in homes or offices. It also enables differentiated management, improving AED management efficiency. Furthermore, this invention uses a carrier medium generated based on AED self-testing for AED device binding on the AED management system, improving the targeting and efficiency of AED binding. It also ensures that binding only occurs when the AED is in normal working order, making it particularly suitable for application scenarios where non-professionals manage the devices, such as in homes or offices.

[0060] Furthermore, the cloud management system of this invention also provides the functions of device sharing and device transfer, which can share AEDs with others for collaborative management or completely transfer them to others for management. Therefore, it is particularly suitable for application scenarios such as homes or companies where non-professional personnel manage the devices, and can effectively cope with situations where non-professional managers are busy or there are personnel changes.

[0061] The above description of the invention is merely an overview of the technical solution of this application. In order to enable those skilled in the art to better understand the technical solution of this application and to implement it based on the description and drawings, and to make the above-mentioned objectives and other objectives, features and advantages of this application easier to understand, the following description is provided in conjunction with the specific embodiments and drawings of this application. Attached Figure Description

[0062] The accompanying drawings are only used to illustrate the principles, implementation methods, applications, features, and effects of specific embodiments of the present invention and other related contents, and should not be considered as limitations on this application.

[0063] In the accompanying drawings of the instruction manual:

[0064] Figure 1a A schematic diagram of the framework of the automated external defibrillator management system described in a specific implementation;

[0065] Figure 1b A block diagram of the automated external defibrillator described in a specific embodiment;

[0066] Figure 2 A flowchart illustrating the automated external defibrillator management method described in the specific implementation embodiment;

[0067] Figure 3 This is a schematic diagram of the self-test results of the automated external defibrillator described in a specific implementation.

[0068] Figure 4a This is a schematic diagram illustrating the device binding guide described in a specific implementation method;

[0069] Figure 4b This is a schematic diagram illustrating the user terminal's identification of the carrier medium during device binding as described in a specific implementation method.

[0070] Figure 4c A schematic diagram illustrating the network testing of the automated external defibrillator as described in a specific implementation;

[0071] Figure 4d A schematic diagram illustrating the network status confirmation of the automated external defibrillator as described in a specific implementation;

[0072] Figure 4e This is a schematic diagram illustrating the user operation training of the management terminal described in a specific implementation.

[0073] Figure 4f A schematic diagram of the electronic warranty card described in the specific implementation method;

[0074] Figure 5a This is a schematic diagram of the blood oxygen and pulse monitoring data described in the specific implementation method;

[0075] Figure 5b This is a data trend chart of the blood oxygen and pulse monitoring data described in the specific implementation method;

[0076] Figure 5c This is a schematic diagram of the defibrillation emergency data described in the specific implementation method;

[0077] Figure 6 A schematic diagram of the framework of the automated external defibrillator management system according to another specific embodiment;

[0078] Figure 7 A flowchart illustrating device sharing as a specific implementation method;

[0079] Figure 8a This is a schematic diagram illustrating the transfer medium handed over by the management terminal sending device in a specific implementation embodiment;

[0080] Figure 8b This is a schematic diagram illustrating the equipment handover process during a specific implementation method.

[0081] Figure 8c This is a schematic diagram showing the equipment after the handover is completed in a specific implementation method.

[0082] Figure 9 This is a schematic diagram illustrating the device displayed on the electronic map in a specific implementation embodiment;

[0083] Figure 10 A block diagram of the cloud management system for the automated external defibrillator described in a specific implementation;

[0084] Figure 11 This is a schematic diagram of a computer-readable storage medium described in a specific embodiment. Detailed Implementation

[0085] To illustrate the possible application scenarios, technical principles, implementable specific solutions, and achievable objectives and effects of this application in detail, the following description, in conjunction with the listed specific embodiments and accompanying drawings, provides a detailed explanation. The embodiments described herein are merely illustrative of the technical solutions of this application and are therefore intended to limit the scope of protection of this application.

[0086] In this document, the term "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The term "embodiment" appearing in various places throughout the specification does not necessarily refer to the same embodiment, nor does it specifically limit its independence or connection with other embodiments. In principle, in this application, as long as there are no technical contradictions or conflicts, the technical features mentioned in each embodiment can be combined in any way to form corresponding implementable technical solutions.

[0087] Unless otherwise defined, the technical terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the use of related terms herein is merely for the purpose of describing particular embodiments and is not intended to limit this application.

[0088] In the description of this application, the term "and / or" is used to describe the logical relationship between objects, indicating that three relationships can exist. For example, A and / or B means: A exists, B exists, and A and B exist simultaneously. Additionally, the character " / " in this document generally indicates that the preceding and following objects have an "or" logical relationship.

[0089] In this application, terms such as “first” and “second” are used only to distinguish one entity or operation from another, and do not necessarily require or imply any actual quantity, hierarchy or order relationship between these entities or operations.

[0090] Without further limitations, the use of terms such as “comprising,” “including,” “having,” or other similar open-ended expressions in this application is intended to cover non-exclusive inclusion, which does not exclude the presence of additional elements in a process, method, or product that includes the stated elements, such that a process, method, or product that includes a list of elements may include not only those defined elements but also other elements not expressly listed, or elements inherent to such a process, method, or product.

[0091] Similar to the understanding in the Examination Guidelines, in this application, expressions such as "greater than," "less than," and "exceeding" are understood to exclude the stated number; expressions such as "above," "below," and "within" are understood to include the stated number. Furthermore, in the description of the embodiments in this application, "multiple" means two or more (including two), and similar expressions related to "multiple" are also understood in this way, such as "multiple groups" and "multiple times," unless otherwise explicitly specified.

[0092] In the description of the embodiments of this application, the space-related expressions used, such as "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "vertical," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," and "circumferential," indicate the orientation or positional relationship based on the orientation or positional relationship shown in the specific embodiments or drawings. They are only for the purpose of describing the specific embodiments of this application or for the reader's understanding, and do not indicate or imply that the device or component referred to must have a specific position, a specific orientation, or be constructed or operated in a specific orientation. Therefore, they should not be construed as limitations on the embodiments of this application.

[0093] Unless otherwise expressly specified or limited, the terms "installation," "connection," "linking," "fixing," and "setting," as used in the description of the embodiments of this application, should be interpreted broadly. For example, "connection" can be a fixed connection, a detachable connection, or an integral setting; it can be a mechanical connection, an electrical connection, or a communication connection; it can be a direct connection or an indirect connection through an intermediate medium; it can be the internal connection of two components or the interaction between two components. For those skilled in the art to which this application pertains, the specific meaning of the above terms in the embodiments of this application can be understood according to the specific circumstances.

[0094] This application provides a method, system, and storage medium for managing automated external defibrillators (AEDs), applicable to online management of AEDs, to provide more comprehensive and efficient AED management. This application's AED management method, system, and storage medium are particularly suitable for AED applications in out-of-hospital (outside-hospital) locations such as homes or offices. While professional inspections are highly efficient for managing large numbers of AEDs within hospitals, in out-of-hospital scenarios like homes or offices, AEDs are dispersed across different locations with low density, resulting in extremely low efficiency for professional inspections. Existing AED remote management systems are primarily developed for in-hospital applications, mainly involving backend specialists managing all AEDs on a backend server. These systems are primarily suitable for centralized management methods such as batch software upgrades and data statistics, but are not applicable to out-of-hospital scenarios like homes or offices where differentiated management based on user needs is required. Therefore, this application proposes the following automated external defibrillator management methods, systems, and storage media to achieve more efficient differentiated management of AEDs in out-of-hospital application scenarios such as homes or companies, and to realize functions such as collaborative device management and handover.

[0095] Please see Figure 1a , Figure 1aThis is a schematic diagram of the framework of the Automated External Defibrillator (AED) management system. The AED management method in this embodiment is based on the management system shown in Figure 1, which is a three-in-one management system consisting of the AED device, the cloud platform, and the management terminal. The AED device refers to the AED itself (including accessories such as batteries and electrode pads). The cloud platform refers to a service platform that provides services and resources through cloud computing technology, and a server with the AED management system (i.e., the cloud management system) is set up on the cloud platform. The management terminal refers to a terminal that has been registered on the cloud management system and can manage the bound AED by logging into the cloud management system on the cloud platform. The management terminal is connected to the cloud platform via the Internet, and the management terminal can be a personal computer, smartphone, tablet, IoT device, etc.

[0096] Please see Figure 2 , Figure 2 This is a flowchart of an automated external defibrillator (AED) management method. The AED management method in this embodiment includes the following steps:

[0097] S201. The cloud management system running on the cloud platform receives a device binding request. The device binding request is sent by the user terminal and includes the device status information generated by the automated external defibrillator to be bound during self-testing.

[0098] S202. The cloud platform analyzes the device status information. If the device status information is normal, it binds the user terminal to the management terminal of the automated external defibrillator. The management terminal is granted management permissions for at least the device application data and device status data of the automated external defibrillator, including defibrillation emergency data and / or vital signs data. The device status data includes battery status data and / or electrode status data.

[0099] In step S201, the device status information is generated by the automated external defibrillator (AED) through self-testing. Therefore, the AED needs to perform a self-test before step S201. Since the AED is an emergency medical device used to defibrillate patients in sudden situations, in actual use, if the electrode pads expire or the device has insufficient power, some AEDs may be difficult to activate in an emergency, wasting valuable rescue time and increasing the risk of complications. Therefore, in related technologies, the installation, use, and maintenance of the AED require specialized personnel. For example, when the AED itself and its accessories (such as electrode pads and batteries) reach the end of their service life or malfunction, timely repairs by specialists are necessary to ensure its normal operation.

[0100] In this embodiment, the self-test of the automated external defibrillator (AED) can promptly detect whether the device itself and its accessories are functioning properly. This proper functioning includes checking the functionality of the device's hardware and software, as well as the functionality and expiration dates of each accessory. The AED self-test includes: checking the power supply and battery status; ensuring the AED's power supply is normal and the battery is sufficient to ensure normal operation and provide adequate power; checking the normal operation of the hardware and software, including checking the circuitry, sensors, processor, and other components for proper functioning; checking the electrode pad status, as the electrodes are crucial for transmitting defibrillation current and monitoring heart rhythm; and checking whether the defibrillation energy output meets standards to ensure sufficient energy is provided for defibrillation when needed. During the power supply and battery status checks, corresponding battery status data is obtained; during the electrode pad status check, corresponding electrode pad status data is obtained. After the self-test, the AED generates corresponding self-test information, including the aforementioned battery status data and electrode pad status data.

[0101] like Figure 3 The image shows the self-test result display interface retrieved from the cloud management system after the automated external defibrillator (AED) performs a self-test in one embodiment. The self-test result includes the AED's test items and their current test result (i.e., whether the self-test passed or failed), including the device's main control module, ECG module, treatment module, charging / discharging module, battery, and electrode pads. This application does not specifically limit the content of the self-test; the specific content can be added to or removed as needed. In some embodiments, the self-test content includes any two or more combinations of the device's main control module, ECG module, treatment module, charging / discharging module, battery, and electrode pads. In some embodiments, battery status data includes the battery serial number, battery expiration date, and remaining charge; electrode pad status data includes the electrode pad expiration date and electrode pad connection status.

[0102] like Figure 1b As shown, the automated external defibrillator (AED) includes: a device application data recording module, a self-test data recording module, a device status data display module, and a network transmission module. The device application data recording module records the aforementioned device application data; the self-test data recording module records data generated during the self-test process, including the aforementioned device status data; the device status data display module records and displays the device status data; and the network transmission module connects to a cloud platform to upload the recorded device application data and device status data to the cloud platform.

[0103] In this embodiment, the automated external defibrillator (AED) generates not only device status information during its self-test but also a medium carrying that information. Other devices can obtain the device status information by identifying this medium. Specifically, the medium can include any one of the following: a QR code, barcode (i.e., a one-dimensional barcode), NFC tag, Bluetooth tag, or RFID tag. In some embodiments, the medium can also be a randomly generated array, etc. Figure 4a and Figure 4b As shown, taking a QR code as an example, the automated external defibrillator generates a QR code after self-testing. The QR code is displayed on the display screen of the automated external defibrillator, and other devices can obtain the device status information of the automated external defibrillator by scanning the QR code.

[0104] In step S201, the user terminal can first register as a user in the cloud management system. After successful registration, the user can apply for device binding in the cloud management system. The cloud management system provides a user registration module and a device binding module. After logging into the cloud management system, the user terminal can enter the user registration module to register as a user, and then enter the device binding module to bind the automated external defibrillator (AED) device according to the prompts.

[0105] When binding a device, the user terminal identifies the carrier medium generated after the automated external defibrillator (AED) self-tests and then uploads the device status information identified based on the carrier medium to the cloud platform.

[0106] It should be noted that in step S201, the cloud management system running on the cloud platform does not mean that the user terminal does not run the cloud management system. The cloud management system includes a main control program running on the server of the cloud platform to implement various functions and data calculations, and an interactive program running on the user terminal or management terminal to implement data interaction. The cloud management system running on the cloud platform refers to the main control program in the cloud management system that implements various functional modules, data, and calculations, which is supported by the server on the cloud platform and runs on the cloud platform; while the interactive program of the cloud management system runs on the user terminal or management terminal.

[0107] In step S201, the user terminal can log in to the cloud management system in different ways. One way is to install the cloud management system APP (application) on the user terminal and log in to the cloud management system through the locally installed APP. Another way is to log in to the cloud management system through a mini-program on a mini-program platform. The mini-program platform includes any one of the comprehensive mini-program platforms such as WeChat Mini-program Platform, Alipay Mini-program Platform, Baidu Smart Mini-program Platform, and Toutiao Mini-program Platform. For example, a user can search for the cloud management system mini-program in WeChat Mini-programs and then enter the mini-program to access the cloud management system. The mini-program is implemented based on the open capabilities and underlying technology of the mini-program platform. The mini-program runs within the mini-program platform and does not require downloading and installing a corresponding application. Taking WeChat mini-programs as an example, they are implemented based on WeChat's open capabilities and underlying technology. When a user opens the cloud management system mini-program, WeChat loads the mini-program's code and resources through a virtual runtime environment and displays it within WeChat. Login via mini-program platforms eliminates the need to download and install applications. Users can directly open them using the QR code scanning or search functions of the aforementioned comprehensive mini-program platforms. Furthermore, mini-program updates are more convenient, requiring no manual updates from the user, ensuring that the latest version is available every time the app is opened.

[0108] In step S202, after receiving the device binding request and the device status information uploaded by the user terminal (the device status information can be obtained by identifying the carrier medium), the cloud platform analyzes and confirms the received device binding request and device status information. The analysis and confirmation of the received device status information includes obtaining the device sequence information of the automated external defibrillator (AED) and confirming whether the device status information is normal (i.e., all functions, battery, and electrode pads of the AED are normal). Each management terminal is bound to at least one AED; in some embodiments, one management terminal can bind to multiple AEDs, and the management terminal can find the bound devices in its device list. When the device status information of the AED is normal, the user terminal is bound as the management terminal of the AED. If the device status information of the AED is faulty, the device binding process ends. When the user terminal is bound as the management terminal of the AED, the user terminal has at least management permissions for the device application data and device status data of the AED.

[0109] In step S202, when a user terminal applies for device binding, the device binding module of the cloud management system provides two sets of binding operation instructions: one for the first power-on and one for subsequent power-ons.

[0110] The cloud management system presents a first-time power-on or non-first-time power-on button on the user terminal; in response to the operation event of the first-time power-on or non-first-time power-on button, it presents a binding operation guide for the first-time power-on or a binding operation guide for non-first-time power-on on the user terminal.

[0111] The initial power-on includes the first power-on after a new automated external defibrillator (AED) is installed, and the first power-on after repair or system upgrade. During the initial power-on, the AED will automatically perform a self-test and generate the aforementioned carrier medium, for example, displaying a self-test QR code on the screen after power-on. Therefore, in this case, the user terminal can apply to bind the AED by uploading the device status information obtained from identifying the carrier medium after entering the device binding process. Figure 4a As shown, this is a binding operation guide interface for the first power-on in one embodiment, which includes instructions for the operator to install the battery and perform the device self-test.

[0112] When the automated external defibrillator (AED) is not being used for the first time, the setup instructions display a path to the self-test results, guiding the user to the AED's periodic self-test results. Upon accessing the self-test results, the AED generates the aforementioned carrier medium, allowing the user terminal to apply for setup by identifying this medium.

[0113] In one embodiment, the device binding request mentioned above also includes the network type information of the automated external defibrillator. The cloud platform can also identify the network type information based on the information obtained by the user terminal when it applies for device binding by uploading the identification carrier medium. Based on the obtained network type, the cloud platform can present the corresponding network configuration guidance on the user terminal. The network type includes, but is not limited to, any one of Bluetooth, 4G, 5G, 6G, and WIFI.

[0114] Users can configure the network of an automated external defibrillator (AED) based on the network configuration guide. The network configuration guide can include the following two types: Network Configuration Guide 1, which guides the AED to directly perform network configuration, and the AED can directly connect to the Internet after network configuration; Network Configuration Guide 2, which guides the AED to perform network configuration within its local area network (LAN), enabling the AED to connect to the Internet through the LAN's gateway device.

[0115] In this embodiment, the specific timing of the network configuration of the automated external defibrillator (AED) relative to the device binding described above is not limited. In some embodiments, the network configuration of the AED can be performed during the device binding process; that is, the user terminal is bound to the AED only when the AED's device status information is normal and the network configuration allows it to connect to the network (the cloud management system can connect to the AED). In other embodiments, network configuration can be performed after the device binding process; that is, regardless of whether the AED applying for binding has already completed network configuration, the device binding described above can be performed, and then the network configuration of the AED can be performed after the device binding.

[0116] In some embodiments, the cloud management system also provides a network testing function (i.e., a network connectivity testing function) to test the network connection status and performance between the automated external defibrillator and the cloud platform. For example... Figure 4c As shown, after the automated external defibrillator (AED) is network-configured, the network test function can be used to test whether the cloud platform can connect to the AED. It should be noted that in some embodiments, the AED can automatically perform network configuration, thus eliminating the need for manual configuration. Therefore, in the activation step, only manual execution is required. Figure 4c The network testing steps shown are sufficient.

[0117] In some embodiments, the above-described automated external defibrillator (AED) management method further includes online operation training, that is, the above-described AED management method may further include: the cloud platform controlling the management terminal to present the operation training information of the AED, the operation training information including any one or more combinations of text, pictures, and videos.

[0118] like Figure 4e As shown, in this embodiment, the cloud management system receives... Figure 4d When the "Next" button is pressed, the management terminal is controlled to play operation training information for the automated external defibrillator (AED). In this embodiment, the operation training information is a video demonstrating the use of the AED. Playing this video trains the AED operator, ensuring they at least master the basic operation of the AED. In other embodiments, the operation training information may include text descriptions in addition to the video, or in some embodiments, a combination of images and text may be used to explain the operation of the AED. This operation training information may be sent to the management terminal by the cloud management system upon receiving the "Next" button input; in some embodiments, the operation training information may also be pre-stored in the local storage space of the management terminal when the cloud management system APP is installed.

[0119] like Figure 4eAs shown, the management terminal also displays options such as "I have confirmed that I have watched the AED operation video" to indicate that I have received training. After receiving the above operation training (for example, after watching the above operation video), the trainee can select this option. Therefore, the management terminal can confirm that the operation training has been carried out and upload the operation training information to the cloud platform.

[0120] In one embodiment, the above-described automated external defibrillator (AED) management method further includes generating an electronic warranty card (hereinafter referred to as an electronic warranty card) for the AED. The aforementioned carrier medium also carries the device serial information of the AED, such as... Figure 3 As shown, the device sequence information is directly included in the self-test information. In some embodiments, the device sequence information may also exist independently of the self-test information. The cloud platform obtains the user's personal information (e.g., company name and contact information) from the management terminal, as well as the operation training confirmation information of the automated external defibrillator (AED), and generates an electronic warranty card by combining the user's personal information, the device sequence information, and the operation training confirmation information. The operation training confirmation information is generated after the operation training information is presented and after confirmation of training is received on the management terminal. The above-mentioned generation of an electronic warranty card based on the operation training confirmation information means that the electronic warranty card can only be generated after the operation training confirmation information has been received (i.e., the above-mentioned operation training has been conducted), not that the electronic warranty card contains the operation training confirmation information. If operation training has not been conducted, an electronic warranty card will not be generated.

[0121] like Figure 4f As shown, the electronic warranty card includes information such as the user's name, address, installation time, device serial number (i.e., device serial information), and warranty period. In some embodiments, the electronic warranty card also includes the name and contact information (e.g., mobile phone number and address) of the organization to which the automated external defibrillator (AED) belongs. Once generated, the information within the electronic warranty card remains unchanged.

[0122] Please see Figures 4a to 4f In one embodiment, an automated external defibrillator (AED) activation step is provided, which includes the device binding described in the above embodiments (e.g., Figure 4a and Figure 4b As shown), network testing (such as...) Figure 4c and Figure 4d (as shown), online operation training (such as) Figure 4e (as shown), generate an electronic warranty card (such as...) Figure 4f (As shown) Each step. The activation process enables the automated external defibrillator (AED) to connect to the cloud platform and be managed by a control terminal, allows the AED operator to acquire basic operating skills, and generates an electronic warranty card.

[0123] It should be noted that in the above embodiments, device binding can be one of the steps in the automated external defibrillator (AED) activation process, or it can be performed independently of the activation process. The success of the device binding is not limited by the successful completion of other steps in the activation process. That is, if activation fails after reaching a step following device binding, the completed device binding steps are still valid.

[0124] In the above embodiments, the management authority over the device application data includes presenting the device application data on the management terminal, including presenting the numerical values ​​and / or data trend change graphs of the device application data, wherein the data trend change graphs include any one of bar charts, scatter plots, line charts, and pie charts.

[0125] like Figure 5a and Figure 5b As shown, the management terminal allows users to view vital signs data such as blood oxygen saturation and pulse rate of the automated external defibrillator (AED) it is linked to. For example... Figure 5a As shown, vital sign data such as blood oxygen saturation and pulse rate can be presented in the form of numerical tables; for example... Figure 5c As shown, the defibrillation and emergency medical data of the linked automated external defibrillator (AED) can be viewed through the management terminal. Figure 5b As shown, vital sign data such as blood oxygen data and pulse data can also be presented in the form of numerical values ​​combined with a vital sign data trend change graph, with the vital sign data trend change graph displayed above the numerical display area. In this embodiment, the vital sign data trend change graph is presented in the form of a dot plot. In other embodiments, the above-mentioned vital sign data trend change graph can also be presented in other ways such as a bar chart or a line graph; and the vital sign data trend change graph and the numerical display area can also be arranged in other ways, such as presenting the vital sign data trend change graph below the numerical display area. In some embodiments, vital sign data such as blood oxygen data and pulse data can also be presented only in the form of a trend change graph, and the numerical values ​​of the vital sign data can be obtained from the trend change graph, instead of displaying the vital sign values ​​in a separate area, that is, only displaying Figure 5b The upper middle part of the text.

[0126] In the previous embodiment, presenting the data trend change graph includes:

[0127] Analyze the changes in the time span of the recorded time points of multiple device application data, as well as the changes in the numerical range of the device application data;

[0128] Based on the changes in the time span and the changes in the numerical range, the coordinate values ​​of the time axis and the numerical axis of the data trend change graph are dynamically adjusted so that the data trend change graph is displayed in an appropriate size within the area enclosed by the time axis and the numerical axis.

[0129] Because different users use automated external defibrillators (AEDs) for vital sign monitoring at different frequencies, and the vital sign data of the same user also fluctuates at different time periods, this embodiment provides a dynamically adjusted data trend chart to facilitate user viewing of the vital sign data trend changes. That is, within different time periods, the coordinate values ​​of the time axis and the numerical axis of the data trend chart are dynamically adjusted as the time span of the recorded time point changes and the numerical range of the data applied by the device changes. The result of this dynamic adjustment is that the graph in the data trend chart can be displayed as completely as possible within the area enclosed by the time axis and the numerical axis, and is easy to view.

[0130] For example, when the blood oxygen recording time changes from three times a day to once a day (i.e., the time span becomes longer), in order to easily view the trend of blood oxygen changes, such as... Figure 5b As shown, the time axis coordinates in the blood oxygen trend graph can be adjusted from 4 hours per grid to 12 hours per grid. Conversely, the time axis coordinates can be decreased. The dynamic adjustment of the numerical coordinate axis in the data trend graph is the same as the adjustment of the time axis coordinates described above, and will not be repeated here.

[0131] In one embodiment, the above-described automated external defibrillator (AED) management method further includes generating and sharing a shared medium with other user terminals to collaboratively manage the bound AED.

[0132] The term "shared medium" refers to the medium's purpose, specifically its use in sharing partial management access to the automated external defibrillator (AED) with other user terminals (i.e., non-bound management terminals), rather than referring to the medium's own structure or other characteristics. The specific type of shared medium can be any of the following: a QR code, a barcode, or a web link. The web link includes, but is not limited to, links sent through social media platforms such as WeChat, QQ, and Alipay.

[0133] In this embodiment, the management terminal of an automated external defibrillator (AED) can invite other user terminals to collaboratively manage the AED it is bound to via a shared medium. The management terminal can select one or more AEDs it is bound to generate a shared medium, which can then be shared with one or more other user terminals. For example, the management terminal can share the shared medium (e.g., a QR code) with its WeChat or QQ friends, inviting them to collaboratively manage the AED. When other user terminals accept the shared medium (i.e., accept the collaborative management request), they gain partial management privileges over the AED, such as viewing the device status data and application data. Figure 6 As shown, at this time, the management terminal of the automated external defibrillator is the primary management device, and the other user terminals that are managed in collaboration are the secondary management devices of the automated external defibrillator. In addition to sending the device status data and device application data of the automated external defibrillator to the management terminal, the cloud platform also sends them to the other user terminals that are managed in collaboration.

[0134] In some embodiments, the cloud management system also provides a device co-management function, meaning that an automated external defibrillator (AED) can be managed collaboratively by two or more devices simultaneously. The AED's management terminal can invite other user terminals to collaboratively manage the bound AED through a shared process. Therefore, in one embodiment, the aforementioned shared medium for generating and sharing collaborative management of the bound AED with other user terminals includes:

[0135] The management terminal initiates the sharing process and requests the cloud platform to generate a sharing medium for collaborative management of the bound automated external defibrillator; the management terminal sends the sharing medium to selected other user terminals and receives sharing acceptance information from the other user terminals;

[0136] In response to the sharing acceptance information, the cloud platform synchronously transmits some management permissions of the bound automated external defibrillator to the other user terminals until the management terminal ends the sharing process.

[0137] Specifically, such as Figure 7As shown, in step S701, the management terminal displays a list of devices that can be shared and selects the device to be shared (i.e., the automated external defibrillator to be collaboratively managed; this can be one device or multiple devices selected simultaneously). In step S702, the management terminal generates a sharing medium for the selected sharing device, where the sharing medium can be any one of a QR code, barcode, NFC tag, Bluetooth tag, or RFID tag. In step S703, the management terminal sends the sharing medium to other user terminals. For example, the management terminal can send the sharing medium to its friends via WeChat, QQ, or Alipay. This sharing medium is a network link such as a WeChat link for receiving and collaboratively managing my device. After receiving the sharing medium, other user terminals can choose to accept or reject the device sharing request. Furthermore, after sending the sharing medium, the management terminal will further determine whether the other user terminals are registered users of the cloud management system. If not, it will push a link to the cloud management system's user registration mechanism (i.e., a user registration link) to them. In step S704, the management terminal, based on the received device sharing confirmation information, can confirm whether the other user terminals have accepted the device sharing request and report back to the cloud management system. The other user terminals that receive the device sharing request are designated as secondary management terminals, and the management terminal is designated as the primary management device. Therefore, in step S705, the cloud management system will delegate some management functions for the shared devices to the secondary management devices. The secondary management devices, like the primary management devices, receive and synchronously display the relevant device information.

[0138] In one embodiment, the above-described automated external defibrillator management method further includes the step of:

[0139] The management terminal generates and sends a transfer medium to other user terminals to transfer the bound automated external defibrillator.

[0140] In response to the other user terminal accepting the acceptance event for the handover medium, the cloud platform binds the other user terminal as a new management terminal and deletes all management permissions of the original management terminal.

[0141] In this context, "transfer medium" refers to a medium whose information is intended for the transfer of management authority over an automated external defibrillator (AED), rather than the medium itself possessing transfer characteristics. Similar to the aforementioned carrier or sharing medium, the transfer medium can also be any of the following: a QR code, barcode, or web link. Web links include, but are not limited to, links sent through social media platforms such as WeChat, QQ, and Alipay. Figure 8a , Figure 8b and Figure 8cAs shown, the management terminal can send and receive network links to friends on WeChat, QQ, and Alipay to manage and control my AED. Of course, the device sharing and transfer described above are not limited to WeChat, QQ, and Alipay; they can also be other social or office platforms that can transmit, share, and transfer devices, such as Xiaohongshu, Douyin, and Lark.

[0142] In the above embodiments, the cloud management system also includes multiple functional modules such as user registration, device map positioning, device operation training, service rights, fault diagnosis, and device unbinding. In addition to delegating management permissions for the device application data and device status data to the management terminal of the automated external defibrillator, the cloud management system can also delegate all or part of the above permissions according to the permissions of the management terminal.

[0143] As an illustration, the service rights function module includes an equipment maintenance information display module, an equipment fault diagnosis module, and an equipment value-added service purchase module. The equipment fault diagnosis module can obtain the most recent self-test data of the automated external defibrillator and display the current equipment status; the equipment value-added service purchase module provides online store functionality and service continuation functionality.

[0144] Indicative, such as Figure 9 As shown, the device map positioning is used for device positioning. In the device map positioning module, the management terminal can display an electronic map and show the location of the bound automated external defibrillator on the electronic map, as well as the device status and other information.

[0145] In a demonstrative manner, the equipment operation training module includes a first aid knowledge module, an operation and usage module, and an interactive experience module. The interactive experience module includes a video demonstration module and a user operation feedback module. The user operation feedback module provides a real-time demonstration of the entire automated external defibrillator (AED) first aid process and user interaction feedback shortcut keys. These shortcut keys allow users to simulate the entire AED first aid process in real-time.

[0146] In summary, the above-described implementation allows for online management of automated external defibrillators (AEDs) via platforms such as apps and WeChat mini-programs. The management terminal connects to each AED through a cloud platform, enabling online device binding, operation training, electronic warranty card generation, multi-device collaborative management, and device management transfer. This allows non-professionals, such as family or company members, to efficiently and reliably manage AEDs—tasks that previously required professional personnel—significantly improving management efficiency. Furthermore, administrators can perform differentiated management of bound devices by logging into the cloud platform, and achieve full lifecycle management of the devices through device installation, binding, and management transfer.

[0147] like Figure 10 As shown, in another embodiment, a cloud management system for an automated external defibrillator (AED) is provided. The cloud management system for the AED runs on a cloud platform and includes a device binding module, a device sharing module, and a device transfer module.

[0148] The device binding module is used to respond to a device binding request sent by a user terminal. The device binding request includes device status information generated by the automated external defibrillator (AED) during self-testing. If the device status information is normal, the module binds the user terminal as the management terminal of the AED and grants the management terminal at least management permissions for the AED's device application data and device status data. The device application data includes defibrillation emergency data and / or vital signs data; the device status data includes battery status data and / or electrode pad status data.

[0149] The device sharing module is used to respond to the device sharing request from the management terminal and generate a sharing medium for collaborative management of the automated external defibrillator (AED) bound to the management terminal. It is also used to respond to the sharing acceptance information and synchronously transmit partial management permissions of the bound AED to other user terminals until the management terminal completes the sharing process.

[0150] The device handover module is used to respond to the device handover request from the management terminal, generate a handover medium for handing over the bound automated external defibrillator to a designated user terminal, and respond to the acceptance event of another user terminal for the handover medium, bind the other user terminal as a new management terminal, and delete all management permissions of the original management terminal.

[0151] In this embodiment, the cloud management system of the automated external defibrillator has the same function and role as the cloud management system in the cloud management method of the automated external defibrillator in the above embodiments. This embodiment follows the descriptions of the cloud management system in the cloud management method of the automated external defibrillator, and will not repeat them here.

[0152] like Figure 11 As shown, in another embodiment, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program, which, when executed by a processor, performs the automated external defibrillator management method described in any of the above embodiments.

[0153] The computer-readable storage medium may be volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); the magnetic surface memory may be disk storage or magnetic tape storage.

[0154] The volatile memory may be random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synclink dynamic random access memory (SLDRAM), and direct memory bus random access memory (DRRAM). The computer-readable storage media described in the embodiments of the present invention are intended to include these and any other suitable types of memory.

[0155] In some embodiments, the processor may be implemented by software, hardware, firmware, or a combination thereof, and may use at least one of the following: circuit, single or multiple application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), central processing units (CPUs), controllers, microcontrollers, and microprocessors, thereby enabling the processor to perform some or all of the steps or any combination of the steps in the automated external defibrillator management method in the various embodiments of this application.

[0156] Finally, it should be noted that although the above embodiments have been described in the text and drawings of this application, this should not limit the scope of patent protection of this application. Any technical solutions that are based on the essential concept of this application and utilize the content described in the text and drawings of this application, resulting in equivalent structural or procedural substitutions or modifications, as well as the direct or indirect application of the technical solutions of the above embodiments to other related technical fields, are all included within the scope of patent protection of this application.

Claims

1. A method for managing an automated external defibrillator, characterized in that, The method includes: The cloud management system running on the cloud platform receives a device binding request. The device binding request is sent by the user terminal and includes the device status information generated by the automated external defibrillator to be bound during self-testing. The cloud platform analyzes the device status information. If the device status information is normal, it binds the user terminal to the management terminal of the automated external defibrillator (AED). It also grants the management terminal at least management permissions for the AED's device application data and device status data, including defibrillation emergency data and / or vital signs data. The device status data includes battery status data and / or electrode pad status data.

2. The automated external defibrillator management method according to claim 1, characterized in that, The user terminal obtains the device status information by identifying or receiving the carrier medium, which is generated during the self-test. The carrier medium includes any one of the following: QR code, barcode, NFC tag, Bluetooth tag, and RFID tag.

3. The automated external defibrillator management method according to claim 1, characterized in that, The user terminal logs into the cloud management system through a locally installed APP or mini-program platform.

4. The automated external defibrillator management method according to claim 1, characterized in that, The device binding request also includes the network type information of the automated external defibrillator; the process of binding the user terminal as the management terminal of the automated external defibrillator also includes the following steps: The cloud platform identifies the network type information and presents corresponding network configuration guidance on the user terminal according to the obtained network type. The network type includes any one of Bluetooth, 4G, 5G, 6G, and WIFI.

5. The automated external defibrillator management method according to claim 4, characterized in that, After the automated external defibrillator (AED) network is configured, the cloud platform tests the network transmission connection between the AED and the cloud platform.

6. The method for managing an automated external defibrillator according to claim 1, characterized in that, The device status information includes the device sequence information of the automated external defibrillator; The process of binding the user terminal as the management terminal of the automated external defibrillator further includes the following steps: The cloud platform acquires the user's personal information from the management terminal, as well as the operation training confirmation information of the automated external defibrillator; and generates an electronic warranty card by combining the user's personal information, the device serial information, and the operation training confirmation information.

7. The method for managing an automated external defibrillator according to claim 6, characterized in that, The process also includes the step of: the cloud platform controlling the management terminal to present the operation training information of the automated external defibrillator, wherein the operation training information includes any one or a combination of two or more of text, images, and videos; The operation training confirmation information is generated after the operation training information is presented and after confirmation of training is received on the management terminal.

8. The method for managing an automated external defibrillator according to claim 1, characterized in that, When the cloud management system receives a device binding request, it also includes: The cloud management system presents a first-time power-on or non-first-time power-on button on the user terminal; in response to the operation event of the first-time power-on or non-first-time power-on button, it presents a binding operation guide for the first-time power-on or a binding operation guide for non-first-time power-on on the user terminal.

9. The method for managing an automated external defibrillator according to claim 1, characterized in that, The management authority over the device application data includes presenting the device application data on the management terminal, including presenting the numerical values ​​and / or data trend graphs of the device application data, wherein the data trend graphs include any one of bar charts, scatter plots, line charts, and pie charts.

10. The method for managing an automated external defibrillator according to claim 9, characterized in that, The data trend charts include: Analyze the changes in the time span of the recorded time points of multiple device application data, as well as the changes in the numerical range of the device application data; Based on the changes in the time span and the changes in the numerical range, the coordinate values ​​of the time axis and the numerical axis of the data trend change graph are dynamically adjusted so that the data trend change graph is displayed in an appropriate size within the area enclosed by the time axis and the numerical axis.

11. The method for managing an automated external defibrillator according to claim 1, characterized in that, It also includes the following steps: Generate and share a shared medium with other user terminals to collaboratively manage the bound automated external defibrillator.

12. The method for managing an automated external defibrillator according to claim 11, characterized in that, Generate and share a shared medium for collaborative management of the bound automated external defibrillator with other user terminals, including: The management terminal initiates the sharing process and requests the cloud platform to generate a sharing medium for collaborative management of the bound automated external defibrillator; The management terminal sends the shared medium to other selected user terminals and receives sharing acceptance information from the other user terminals; In response to the sharing acceptance information, the cloud platform synchronously transmits some management permissions of the bound automated external defibrillator to the other user terminals until the management terminal ends the sharing process.

13. The automated external defibrillator management method according to claim 12, characterized in that, After the management terminal sends the shared medium to selected other user terminals, the method further includes: Determine whether the other user terminal is a registered user; if not, push a user registration link to the other user terminal.

14. The method for managing an automated external defibrillator according to claim 11, characterized in that, The sharing medium includes any one of QR codes, barcodes, and web links.

15. The method for managing an automated external defibrillator according to claim 1, characterized in that, It also includes the following steps: The management terminal generates and sends a transfer medium to other user terminals to transfer the bound automated external defibrillator.

16. The method for managing an automated external defibrillator according to claim 15, characterized in that, The management terminal generates and sends a transfer medium to other user terminals for transferring the bound automated external defibrillator, including: The management terminal selects other user terminals of the automated external defibrillator (AED) that are bound to it for takeover, and generates the handover medium for the other user terminals. In response to the other user terminal accepting the acceptance event for the handover medium, the cloud platform binds the other user terminal as a new management terminal and deletes all management permissions of the original management terminal.

17. The method for managing an automated external defibrillator according to claim 1, characterized in that, The cloud management system also grants the management terminal at least one or more of the following management permissions: user registration, device map positioning, device operation training, service rights, fault diagnosis, and device unbinding.

18. The method for managing an automated external defibrillator according to claim 1, characterized in that, The self-test includes the self-test performed when the device is first turned on after installation or the self-test performed periodically by the automated external defibrillator.

19. A cloud management system for an automated external defibrillator, characterized in that, Running on a cloud platform, including: The device binding module is used to respond to a device binding request sent by a user terminal. The device binding request includes device status information generated by the automated external defibrillator (AED) during self-testing. If the device status information is normal, the module binds the user terminal as the management terminal of the AED and grants the management terminal at least management permissions for the device application data and device status data of the AED. The device application data includes defibrillation emergency data and / or vital signs data; the device status data includes battery status data and / or electrode pad status data.

20. The cloud management system for the automated external defibrillator according to claim 19, characterized in that, The user terminal obtains the device status information by identifying or receiving the carrier medium, which is generated during the self-test. The carrier medium includes any one of the following: QR code, barcode, NFC tag, Bluetooth tag, and RFID tag.

21. The cloud management system for the automated external defibrillator according to claim 19, characterized in that, The user terminal logs into the cloud management system through a locally installed APP or mini-program platform.

22. The cloud management system for the automated external defibrillator according to claim 19, characterized in that, The device binding request also includes the network type information of the automated external defibrillator; The binding module is also used to identify the network type information and present the corresponding network configuration guidance on the user terminal according to the obtained network type. The network type includes any one of Bluetooth, 4G, 5G, 6G, and WIFI.

23. The cloud management system for the automated external defibrillator according to claim 19, characterized in that, The binding module is also used to obtain the user's personal information from the user terminal and the operation training confirmation information of the automated external defibrillator; and to generate an electronic warranty card by combining the user's personal information, the device serial information and the operation training confirmation information.

24. The cloud management system for the automated external defibrillator according to claim 19, characterized in that, During the user terminal device binding request process, the cloud management system presents a first-time power-on or non-first-time power-on button on the user terminal; in response to the operation event of the first-time power-on or non-first-time power-on button, it presents a binding operation guide for first-time power-on or non-first-time power-on on the user terminal.

25. The cloud management system for the automated external defibrillator according to claim 19, characterized in that, The management authority over the device application data includes presenting the device application data on the management terminal, including presenting the numerical values ​​of the device application data and / or data trend change graphs, wherein the data trend change graphs include any one of bar charts, scatter plots, line charts, and pie charts.

26. The cloud management system for the automated external defibrillator according to claim 19, characterized in that, Also includes: The device sharing module is used to respond to the device sharing request of the management terminal and generate a sharing medium for collaborative management of the automated external defibrillator that has been bound to the management terminal.

27. The cloud management system for an automated external defibrillator according to claim 26, characterized in that, The device sharing module is also used to respond to the sharing acceptance information and synchronously transmit some management permissions of the bound automated external defibrillator to the other user terminals until the management terminal ends the sharing process.

28. The cloud management system for an automated external defibrillator according to claim 27, characterized in that, The device sharing module is also used to determine whether the other user terminal is a registered user. If not, it pushes a user registration link to the other user terminal.

29. The cloud management system for the automated external defibrillator according to claim 19, characterized in that, Also includes: The device handover module is used to respond to the device handover request from the management terminal and generate a handover medium for handing over the bound automated external defibrillator to a designated user terminal.

30. The cloud management system for the automated external defibrillator according to claim 29, characterized in that, The device handover module is also used to respond to the other user terminal accepting an acceptance event for the handover medium, bind the other user terminal as a new management terminal, and delete all management permissions of the original management terminal.

31. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, performs the automated external defibrillator management method according to any one of claims 1-18.

Images