A remote maintenance method, device, equipment and medium for medical equipment

Abstract

The present invention relates to the field of medical equipment maintenance technology, and in particular to a remote maintenance method, device, equipment and medium for medical equipment. The present application provides a remote maintenance method for medical equipment, which is applied to a management end, and the management end is connected to a device end in communication. The remote maintenance method includes: determining a target upgrade task that matches the upgrade request instruction according to an upgrade request instruction received from the device end; sending a target upgrade package in the target upgrade task to the device end, so that the device end upgrades the device to be upgraded according to the target upgrade package. In the present application, during the upgrade process of the device end, a connection is established between the device end and the management end, and the device end to be upgraded is uniformly managed at the management end, and the upgrade package is sent to the device end by the management end for upgrading. The upgrade process is automated, which reduces manual intervention and reduces the complexity of operation.

Description

Technical Field

[0001] The present invention relates to the technical field of medical equipment maintenance, and in particular to a remote maintenance method, device, equipment and medium for medical equipment. Background Art

[0002] As a medical device, the software part of the automatic external defibrillator plays a vital role in the functional realization and user experience of the product. These software usually contain multiple modules such as control algorithms, user interfaces, communication protocols, etc., which need to be continuously upgraded according to market feedback and technological development. Among the existing software upgrade technologies, offline upgrade is a common method. It usually requires taking the device back to the service center or updating the software through a specific upgrade tool. However, this method is complicated to operate, such as requiring user cooperation and a long time. Therefore, in the process of upgrading medical equipment, how to reduce the complexity of operation has become an urgent problem to be solved. Summary of the invention

[0003] In view of this, the embodiments of the present invention provide a remote maintenance method, apparatus, device and medium for medical equipment to solve the problem of complex operations during the upgrade of medical equipment.

[0004] In a first aspect, an embodiment of the present invention provides a remote maintenance method for a medical device, the remote maintenance method is applied to a management end, the management end is communicatively connected with a device end, and the remote maintenance method includes: Determining, according to the received upgrade request instruction sent by the device end, a target upgrade task matching the upgrade request instruction; The target upgrade package in the target upgrade task is sent to the device end, so that the device end upgrades the device to be upgraded according to the target upgrade package.

[0005] In a second aspect, an embodiment of the present invention provides a remote maintenance method for a medical device, the remote maintenance method is applied to a device end, the device end is communicatively connected with a management end, and the remote maintenance method includes: Sending an upgrade request instruction to the management terminal according to the received synchronous upgrade instruction sent by the management terminal; The device to be upgraded on the equipment side is upgraded according to the received target upgrade package sent by the management side.

[0006] In a third aspect, an embodiment of the present invention provides a remote maintenance device for medical equipment, the remote maintenance device is applied to a management end, the management end is communicatively connected with a device end, and the remote maintenance device includes: A determination module, configured to determine a target upgrade task matching the upgrade request instruction according to the received upgrade request instruction sent by the device end; The first sending module is used to send the target upgrade package in the target upgrade task to the device end, so that the device end upgrades the device to be upgraded according to the target upgrade package.

[0007] In a fourth aspect, an embodiment of the present invention provides a remote maintenance device for medical equipment, the remote maintenance device is applied to a device end, the device end is communicatively connected with a management end, and the remote maintenance device includes: A second sending module, configured to send an upgrade request instruction to the management terminal according to the received synchronous upgrade instruction sent by the management terminal; The upgrade module is used to upgrade the device to be upgraded on the equipment side according to the target upgrade package received from the management side.

[0008] In a fifth aspect, an embodiment of the present invention provides a computer device, comprising a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the training method described in the first aspect and the remote maintenance method described in the second aspect are implemented.

[0009] In a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the training method described in the first aspect and the remote maintenance method described in the second aspect are implemented.

[0010] Compared with the prior art, the present invention has the following beneficial effects: The present application provides a remote maintenance method for medical equipment. The remote maintenance method is applied to the management end, and the management end is connected to the device end in communication. The remote maintenance method includes: determining a target upgrade task that matches the upgrade request instruction according to the upgrade request instruction received from the device end; sending the target upgrade package in the target upgrade task to the device end, so that the device end upgrades the device to be upgraded according to the target upgrade package. In the present application, during the upgrade process of the device end, a connection is established between the device end and the management end, and the device end to be upgraded is uniformly managed at the management end, and the upgrade package is sent to the device end by the management end for upgrading. The upgrade process is automated, which reduces manual intervention and reduces the complexity of operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative labor.

[0012] Figure 1 This is a schematic diagram of an application environment of a remote maintenance method for medical equipment provided by an embodiment of the present invention; Figure 2 It is a flowchart of a remote maintenance method of a medical device provided by an embodiment of the present invention; Figure 3 This is an interface diagram of an upgrade package list provided by an embodiment of the present invention; Figure 4 This is a diagram of an editing interface for a newly added upgrade package provided by an embodiment of the present invention; Figure 5 This is an interface diagram of a device upgrade list provided by an embodiment of the present invention; Figure 6 This is a diagram of an editing interface for a newly added task provided by an embodiment of the present invention; Figure 7 It is a flowchart of a remote maintenance method of a medical device provided by an embodiment of the present invention; Figure 8 It is a structural block diagram of a remote maintenance device for medical equipment provided by one embodiment of the present invention; Fig. 9 It is a structural block diagram of a remote maintenance device for medical equipment provided by one embodiment of the present invention; Fig.10 It is a structural schematic diagram of a computer device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0013] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0014] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present invention. However, it should be clear to those skilled in the art that the present invention may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present invention.

[0015] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0016] It should also be understood that the term "and / or" used in the present description and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

[0017] As used in the present specification and the appended claims, the term "if" may be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" may be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]", depending on the context.

[0018] In addition, in the description of the present specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0019] References to "one embodiment" or "some embodiments" etc. described in the present specification mean that one or more embodiments of the present invention include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0020] It should be understood that the order of execution of the steps in the following embodiments does not imply a precedence of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0021] In order to illustrate the technical solution of the present invention, specific embodiments are provided below for illustration.

[0022] A remote maintenance method for medical equipment provided by an embodiment of the present invention can be applied in Figure 1In an application environment, the management end is communicatively connected with the device end, wherein the management end includes but is not limited to handheld computers, desktop computers, laptop computers, ultra-mobile personal computers (UMPC), netbooks, cloud computer devices, personal digital assistants (PDA) and other computer devices.

[0023] See also Figure 2 , is a flow chart of a remote maintenance method for a medical device provided by an embodiment of the present invention. The remote maintenance method for a medical device can be applied to Figure 1 The management end in Figure 2 As shown, the remote maintenance method of the medical device may include the following steps.

[0024] S201: Determine a target upgrade task matching the upgrade request instruction according to the upgrade request instruction received from the device end.

[0025] In step S201, the management end is connected to the device end in communication, and the management end receives the upgrade request instruction sent by the device end to determine whether the device to be upgraded on the device end meets the upgrade conditions. The upgrade request instruction includes the device to be upgraded, the current original version number and the target version number of the device to be upgraded, wherein the upgrade request instruction is used to determine whether the device end meets the upgrade conditions, and when the device end meets the upgrade conditions, the device to be upgraded on the device end is upgraded, wherein the device end is a corresponding medical device, such as a medical defibrillator device (AED), and the device to be upgraded is a device in the device end, such as a mainboard device and a defibrillator pad device in the medical defibrillator device.

[0026] In this embodiment, the remote maintenance method is applied to the management end, and the management end is communicated with the device end, that is, the upgrade task of the device end that needs to be upgraded is added to the management end, so that when the device end meets the upgrade conditions, the management end can manage the upgrade task of the device end.

[0027] It should be noted that the management end is in communication connection with the device end, that is, the management end stores the upgrade tasks and upgrade packages of the device end, wherein the upgrade package is the burning software of the device to be upgraded, that is, the version files corresponding to different version numbers of the device to be upgraded. For example, when the mainboard of the device end is upgraded from version 1.0 to version 2.0, the upgrade package includes the version files corresponding to version 2.0 of the mainboard.

[0028] It should be noted that when the management end manages the upgrade package of the device end, it is displayed in the form of a list. For example, the upgrade package list includes the upgrade package name, creation time, file size, remarks and operations, etc. For example, the upgrade package name is Mainboard Upgrade 0902v4.0, the creation time is 2024:09:02 11:40:07, the file size is 1804171 (byte), the remarks are Mainboard Upgrade 0902v4.0, and the operations include edit, download and delete.

[0029] It should be noted that the upgrade package of the device side stored in the management side may include upgrade packages with multiple version numbers, such as the mainboard upgrade package may include mainboard upgrade 0902v4.0, mainboard upgrade 0902v2.0, etc. Figure 3 , Figure 3 This is an interface diagram of an upgrade package list provided by an embodiment of the present invention. The attribute columns of the upgrade package list in the figure include serial number, upgrade package name, creation time, file size, remarks and operation.

[0030] It should be noted that when a new upgrade package needs to be stored, the new upgrade package data can be added in the new upgrade package editing interface of the management end. For example, the new upgrade package editing interface includes the upgrade package name, upgrade task type, remarks, etc. of the upgrade package to be added. Figure 4 , Figure 4 This is a diagram of an editing interface for adding an upgrade package provided by an embodiment of the present invention. When adding an upgrade package, click Add in the upgrade package list interface, add the upgrade package name, upgrade task type, remarks, and upload the corresponding upgrade package in the editing interface of the new upgrade package.

[0031] The upgrade tasks of the devices to be upgraded on the management end storage device are displayed in the form of a list and can be displayed on the management end page. The device upgrade list includes the task name, upgrade package name, upgrade task type, task progress, creation time and operation. For example, the task name is Mainboard Upgrade 0902, the upgrade package name is Mainboard Upgrade 0902v4.0, the upgrade task type is Mainboard, the task progress is 10% completion rate, the creation time is 2024:09:02 11:40:07, and the operations include task details and deletion. See Figure 5 , Figure 5 The device upgrade list interface diagram provided by an embodiment of the present invention includes a serial number, a task name, an upgrade package name, an upgrade task type, a task progress, a creation time and an operation. The upgrade task type is a device to be upgraded in the device end. It should be noted that when a new device upgrade task is needed, a new upgrade task can be added in the new task editing interface of the management end. Figure 6 , Figure 6This is a diagram of an editing interface for a newly added task provided by an embodiment of the present invention. The newly added task editing interface includes a task name, an upgrade task type, an upgrade package list, and a device list, wherein the task name corresponds to the task name in the upgrade package, the upgrade task type is the corresponding mainboard and defibrillator board, the upgrade package list is the upgrade package list mentioned above, the corresponding upgrade package name is selected from the upgrade package list, the device list includes the device end that communicates with the management end, the device list includes the number, location, and status information of the device end, and the device end to be upgraded is added from the device list. Add the corresponding upgrade task on the management end so that the management end can manage the device end to be upgraded.

[0032] In this embodiment, after the management end receives the upgrade request instruction sent by the device end, it determines the target upgrade task that matches the upgrade request instruction, that is, searches the device upgrade list for the target upgrade task that matches the upgrade request instruction, so as to send the target upgrade package in the target upgrade task to the corresponding device end.

[0033] It should be noted that the upgrade request instruction includes the number of the device end, the device to be upgraded, the current original version number and the target version number of the device to be upgraded. When determining the target upgrade task that matches the upgrade request instruction, the device end to be upgraded can be determined according to the number of the device end, and the target upgrade task that matches the upgrade request instruction can be determined according to the target version number required by the device to be upgraded in the device end to be upgraded.

[0034] It should be noted that when the management end receives upgrade request instructions sent by multiple device ends, the management end determines a target upgrade task matching each upgrade request instruction, so that the management end can manage multiple device ends simultaneously.

[0035] Optionally, determining a target upgrade task matching the upgrade request instruction according to the received upgrade request instruction sent by the device end includes: Determine whether the device to be upgraded meets the upgrade conditions according to the original version number and the target version number of the device to be upgraded; When the device to be upgraded meets the upgrade conditions, a target upgrade task matching the upgrade request instruction is determined according to the device number, the device to be upgraded, and the target version number.

[0036] In this embodiment, the upgrade request instruction includes the number of the device end, the device to be upgraded, the current original version number and target version number of the device to be upgraded, wherein the target device end to be upgraded is determined according to the number of the device end, and the corresponding upgrade task type is determined according to the device to be upgraded. The original version number and target version number of the device to be upgraded are used to determine whether the device to be upgraded meets the upgrade conditions, that is, to determine whether the device to be upgraded needs to be upgraded.

[0037] It should be noted that when judging whether the device to be upgraded meets the upgrade conditions based on the original version number and the target version number of the device to be upgraded, the judgment can be made based on the size of the original version number and the target version number. When the original version number is smaller than the target version number, it is considered that the device to be upgraded meets the upgrade conditions. When the original version number is not smaller than the target version number, it is considered that the device to be upgraded does not meet the upgrade conditions.

[0038] When the device to be upgraded meets the upgrade conditions, the target upgrade task matching the upgrade request instruction is determined according to the device number, the device to be upgraded, and the target version number. That is, the target device to be upgraded is determined according to the device number, the corresponding upgrade task type is determined according to the device to be upgraded, the upgrade package name is determined according to the target version number, and the target upgrade task matching the upgrade request instruction is determined according to the target device, the upgrade task type, and the upgrade package name.

[0039] S202: Sending the target upgrade package in the target upgrade task to the device end, so that the device end upgrades the device to be upgraded according to the target upgrade package.

[0040] In step S202, after determining the corresponding target upgrade task, the management end sends the target upgrade package in the target upgrade task to the device end, so that the device end upgrades the device to be upgraded according to the target upgrade package.

[0041] In this embodiment, after the management end determines the corresponding target task, it sends the target upgrade package in the target upgrade task to the device end, so that the device end upgrades the device to be upgraded according to the target upgrade package, thereby enabling the management end to complete the remote maintenance upgrade of the device end.

[0042] It should be noted that when the device end upgrades the device to be upgraded according to the target upgrade package, the task progress of the corresponding device end upgrade is displayed in the device upgrade list. When the management end sends the corresponding target upgrade packages to different device ends at the same time, the different device ends are upgraded at the same time, and the management end displays the upgrade progress of the corresponding upgrade tasks of the different device ends at the same time.

[0043] It should be noted that during the upgrade process on the device side, the management page can display the total number of upgraded devices, the number of devices being upgraded, the number of devices whose upgrades have been completed, the number of devices whose upgrades have failed, and the number of devices whose upgrades have been abnormal.

[0044] It should be noted that when the management end sends the target upgrade package in the target upgrade task to the device end, the target upgrade package can be sent in sub-packets, that is, the target upgrade package is split into different sub-packets, and the sub-packets are sent to the corresponding device end in sequence. The sub-packet sending reduces the size of the data so that the device end can receive the corresponding sub-packets in sequence.

[0045] Optionally, before determining the target upgrade package matching the device to be upgraded of the device end according to the received upgrade request instruction sent by the device end, the method further includes: Obtaining an upgrade package for the device to be upgraded on the device side; The upgrade package is encrypted to obtain an encrypted upgrade package.

[0046] In this embodiment, an upgrade package of the device to be upgraded on the device side is obtained, wherein the upgrade package is an executable burning file compiled according to the project engineering link. After obtaining the corresponding upgrade package, in order to transmit the corresponding upgrade package more safely, the upgrade package is encrypted to ensure the integrity and data consistency of the target upgrade package transmission process. In this embodiment, the MD5 (Message-Digest Algorithm) information digest algorithm is used to encrypt the upgrade package to obtain an encrypted upgrade package. During encryption, the MD5 value is stored in the file packet header of the upgrade package, and the data in the upgrade package is replaced to obtain the encrypted upgrade package. The encrypted upgrade package is stored in the management end, that is, the upgrade package added to the device upgrade list is the encrypted upgrade package, so as to facilitate the sending of the encrypted upgrade package to the device end.

[0047] See also Figure 7 , is a flow chart of a remote maintenance method for a medical device provided by an embodiment of the present invention. The remote maintenance method for a medical device can be applied to Figure 1 The device side in Figure 7 As shown, the remote maintenance method of the medical device may include the following steps.

[0048] S701: Send an upgrade request instruction to the management terminal according to the received synchronous upgrade instruction sent by the management terminal.

[0049] In step S701, the management end is connected to the device end in communication, and the device end sends an upgrade request instruction to the management end according to the synchronous upgrade instruction sent by the management end, wherein the synchronous upgrade instruction is an upgrade instruction sent by the management end to the corresponding device end to be upgraded according to the upgrade task in the device upgrade list, so that the management end can perform upgrade management on the device end, and the device end sends an upgrade request instruction to the management end according to the synchronous upgrade instruction sent by the management end, wherein the upgrade request instruction is a connection request sent by the device end to the management end, so as to determine that the corresponding device end is connected to the management end. The device end is a corresponding medical device, such as a medical defibrillator (AED), and the device to be upgraded is a device in the device end, such as a mainboard device and a defibrillator pad device in the medical defibrillator.

[0050] In this embodiment, according to the received synchronous upgrade instruction sent by the management end, an upgrade request instruction is sent to the management end, wherein the upgrade request instruction includes the number of the device end, the device to be upgraded, the current original version number and the target version number of the device to be upgraded. In this way, the management end can judge whether the device to be upgraded meets the upgrade conditions according to the original version number and the target version number of the device to be upgraded. When the device to be upgraded meets the upgrade conditions, the target upgrade task matching the upgrade request instruction is determined according to the number of the device end, the device to be upgraded and the target version number.

[0051] S702: Upgrading the device to be upgraded on the equipment side according to the received target upgrade package sent by the management side.

[0052] In step S702, the device end upgrades the device to be upgraded on the device end according to the target upgrade package received from the management end. When upgrading the device to be upgraded on the device end, the device end automatically upgrades according to the target upgrade package.

[0053] In this embodiment, after the device sends an upgrade request instruction to the management end, the management end sends a target upgrade package to the device end, the device end receives the target upgrade package sent by the management end, the device end automatically upgrades, and the corresponding upgrade progress is displayed on the management end.

[0054] It should be noted that if the target upgrade package is sent in sub-packets, it is necessary to determine whether the number of sub-packets received by the device is equal to the number of sub-packets split by the management end, and whether the length of each sub-packet is equal. If the number of sub-packets received by the device is equal to the number of sub-packets split by the management end, and the length of each sub-packet is equal, the device will splice the received sub-packets to obtain a complete target upgrade package.

[0055] It should be noted that if the length of the sub-packet received by the device is not equal to the length of the sub-packet sent by the corresponding management end, it is considered that an abnormality has occurred, and the management end needs to resend the corresponding target upgrade package. If the number of abnormalities exceeds the preset threshold, it is considered that the management end has failed to send, and the device to be upgraded in the device end is automatically restored to the version corresponding to the original version number.

[0056] It should be noted that if the management end encrypts the target upgrade package before transmitting it, it is also necessary to decrypt and verify the received encrypted upgrade package. If the decryption verification is successful, that is, the decrypted target upgrade package is the same upgrade package as the target upgrade package sent by the management end, then the device to be upgraded will be upgraded. The target upgrade package is decrypted and verified to ensure the integrity and data consistency of the target upgrade package.

[0057] For example, during decryption verification, if the target upgrade package is encrypted using the MD5 encryption algorithm, the MD5 value of the encrypted upgrade package is calculated to determine whether the MD5 values ​​before and after encryption are equal. If the MD5 values ​​before and after encryption are equal, the received target upgrade package is considered to be a complete upgrade package. According to the target upgrade package sent by the received management end, the device to be upgraded on the equipment side is upgraded.

[0058] Optionally, upgrading the device to be upgraded on the device side according to the received target upgrade package sent by the management side includes: If the device to be upgraded is a mainboard, the mainboard is upgraded according to the target upgrade package received from the management terminal; If the device to be upgraded is a defibrillator paddle, after the main board receives the target upgrade package sent by the management terminal, the target upgrade package is sent to the defibrillator paddle, and the defibrillator paddle is upgraded according to the received target upgrade package.

[0059] In this embodiment, the device to be upgraded includes a mainboard and a defibrillator paddle, that is, the mainboard and the defibrillator paddle in the device end can be upgraded. If the device to be upgraded is the mainboard, that is, the upgrade task type corresponding to the target upgrade package is the mainboard, then after the device end receives the target upgrade package, that is, the mainboard receives the target upgrade package, the mainboard can be directly upgraded according to the target upgrade package.

[0060] If the device to be upgraded is a defibrillator paddle, it is necessary to send the target upgrade package to the defibrillator paddle after the mainboard receives the target upgrade package sent by the management terminal, and the defibrillator paddle is upgraded according to the received target upgrade package.

[0061] It should be noted that if the target upgrade package is sent in sub-packages, after the main board receives all the sub-packages, the sub-packages are spliced ​​to obtain a complete target upgrade package, and then the complete target upgrade package sub-packages are sent to the defibrillator board.

[0062] If the target upgrade package is an encrypted upgrade package and the device to be upgraded is a defibrillator board, the defibrillator board needs to decrypt and verify the target upgrade package after receiving the target upgrade package sent by the mainboard, and upgrade after the decryption and verification pass.

[0063] It should be noted that if the target upgrade package received by the device end is the upgrade package corresponding to the mainboard upgrade and the upgrade package corresponding to the defibrillator paddle upgrade, the device end can upgrade the mainboard and the defibrillator paddle at the same time, that is, different devices to be upgraded on the device end are upgraded separately without interfering with each other, thereby improving the upgrade efficiency of the device end.

[0064] In this embodiment, the main board and the defibrillator plate can be upgraded separately or simultaneously, which increases the flexibility of the device upgrade and improves the upgrade efficiency of the device. The device upgrade is performed automatically, which reduces the complexity of the device upgrade.

[0065] Optionally, after upgrading the device to be upgraded on the equipment side according to the received target upgrade package sent by the management side, the method further includes: If the device to be upgraded on the equipment side is upgraded successfully, an upgrade success instruction is sent to the management side; If the device to be upgraded on the device side fails to upgrade, the device to be upgraded on the device side is restored to the version corresponding to the original version number.

[0066] In this embodiment, after the device to be upgraded on the equipment side is upgraded according to the target upgrade package sent by the management end, if the device to be upgraded on the equipment side is successfully upgraded, an upgrade success instruction is sent to the management end so that the management end can update the upgrade tasks in the device upgrade list. If the device to be upgraded on the equipment side fails to be upgraded, the device to be upgraded on the equipment side is restored to the version corresponding to the original version number to ensure that the device side can work normally.

[0067] The present application provides a remote maintenance method for medical equipment. The remote maintenance method is applied to the management end, and the management end is connected to the device end in communication. The remote maintenance method includes: determining a target upgrade task that matches the upgrade request instruction according to the upgrade request instruction received from the device end; sending the target upgrade package in the target upgrade task to the device end, so that the device end upgrades the device to be upgraded according to the target upgrade package. In the present application, during the upgrade process of the device end, a connection is established between the device end and the management end, and the device end to be upgraded is uniformly managed at the management end, and the upgrade package is sent to the device end by the management end for upgrading. The upgrade process is automated, which reduces manual intervention and reduces the complexity of operation.

[0068] See also Figure 8 , Figure 8 1 is a block diagram of a remote maintenance device for medical equipment provided by an embodiment of the present invention. The remote maintenance device for medical equipment is applied to the management terminal. For ease of description, only the part related to the embodiment of the present application is shown. Figure 8 The remote maintenance device 80 includes a determining module 81 and a first sending module 82 .

[0069] The determination module 81 is used to determine the target upgrade task matching the upgrade request instruction according to the received upgrade request instruction sent by the device end.

[0070] The first sending module 82 is used to send the target upgrade package in the target upgrade task to the device end, so that the device end upgrades the device to be upgraded according to the target upgrade package.

[0071] Optionally, the determination module 81 includes: The judging unit is used to judge whether the device to be upgraded meets the upgrading condition according to the original version number and the target version number of the device to be upgraded.

[0072] The determination unit is used to determine the target upgrade task matching the upgrade request instruction according to the device number, the device to be upgraded, and the target version number when the device to be upgraded meets the upgrade condition.

[0073] Optionally, the remote maintenance device 80 further includes: The acquisition module is used to acquire the upgrade package of the device to be upgraded on the device side.

[0074] The encryption module is used to encrypt the upgrade package to obtain the encrypted upgrade package.

[0075] See also Fig. 9 , Fig. 9 1 is a block diagram of a remote maintenance device for medical equipment provided by an embodiment of the present invention. The remote maintenance device for medical equipment is applied to the device end. For ease of description, only the part related to the embodiment of the present application is shown. Fig. 9 The remote maintenance device 90 includes The second sending module 91 is used to send an upgrade request instruction to the management terminal according to the received synchronous upgrade instruction sent by the management terminal.

[0076] The upgrade module 92 is used to upgrade the device to be upgraded on the equipment side according to the target upgrade package received from the management side.

[0077] Optionally, the upgrade module 92 includes: The first upgrading unit is used for upgrading the mainboard according to the target upgrading package received from the management terminal if the device to be upgraded is the mainboard.

[0078] The second upgrading unit is used for sending the target upgrading package to the defibrillator board after the main board receives the target upgrading package sent by the management terminal if the device to be upgraded is the defibrillator board, and the defibrillator board is upgraded according to the received target upgrading package.

[0079] Optionally, the remote maintenance device 90 includes: The sending module is used to send an upgrade success instruction to the management end if the device to be upgraded at the equipment end is upgraded successfully.

[0080] The recovery module is used to restore the device to be upgraded on the device side to the version corresponding to the original version number if the upgrade of the device to be upgraded on the device side fails.

[0081] It should be noted that the information interaction, execution process and other contents between the above-mentioned modules are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0082] Fig.10 FIG. 1 is a schematic diagram of the structure of a computer device provided by an embodiment of the present invention. Fig.10 As shown, the computer device of this embodiment includes: at least one processor ( Fig.10 Only one is shown in the figure), a memory, and a computer program stored in the memory and executable on at least one processor, wherein when the processor executes the computer program, the steps in any of the above-mentioned remote maintenance method embodiments are implemented.

[0083] The computer device may include, but is not limited to, a processor and a memory. Those skilled in the art will appreciate that Fig.10 This is merely an example of a computer device and does not constitute a limitation on the computer device. The computer device may include more or fewer components than those shown in the figure, or a combination of certain components, or different components. For example, it may also include a network interface, a display screen, and an input device.

[0084] The processor may be a CPU, or other general-purpose processors, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0085] The memory includes a readable storage medium, an internal memory, etc., wherein the internal memory may be the memory of a computer device, and the internal memory provides an environment for the operation of the operating system and computer-readable instructions in the readable storage medium. The readable storage medium may be a hard disk of a computer device, and in other embodiments, it may also be an external storage device of the computer device, for example, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the computer device. Further, the memory may also include both an internal storage unit of the computer device and an external storage device. The memory is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as the program code of a computer program, etc. The memory may also be used to temporarily store data that has been output or is to be output.

[0086] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned device can refer to the corresponding process in the above-mentioned method embodiment, which will not be repeated here. If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the steps of the above-mentioned method embodiment can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device capable of carrying computer program code, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.

[0087] The present application implements all or part of the processes in the above-mentioned embodiment method, and may also be completed through a computer program product. When the computer program product runs on a computer device, the computer device can implement the steps in the above-mentioned method embodiment when executing the computer program product.

[0088] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0089] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0090] In the embodiments provided in the present application, it should be understood that the disclosed devices / computer equipment and methods can be implemented in other ways. For example, the device / computer equipment embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0091] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0092] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A remote maintenance method for medical equipment, characterized in that: The remote maintenance method is applied to a management end, the management end is in communication connection with a device end, and the remote maintenance method includes: Determining, according to the received upgrade request instruction sent by the device end, a target upgrade task matching the upgrade request instruction; The target upgrade package in the target upgrade task is sent to the device end, so that the device end upgrades the device to be upgraded according to the target upgrade package.

2. The remote maintenance method according to claim 1, characterized in that: The upgrade request instruction includes the device number, the device to be upgraded, the current original version number and the target version number of the device to be upgraded; The step of determining, according to the received upgrade request instruction sent by the device, a target upgrade task matching the upgrade request instruction comprises: Determining whether the device to be upgraded meets an upgrade condition according to the original version number of the device to be upgraded and the target version number; When the device to be upgraded meets the upgrade condition, a target upgrade task matching the upgrade request instruction is determined according to the number of the device end, the device to be upgraded, and the target version number.

3. The remote maintenance method according to claim 1, characterized in that: Before determining the target upgrade package matching the device to be upgraded of the device end according to the received upgrade request instruction sent by the device end, the method further includes: Obtaining an upgrade package for the device to be upgraded on the device end; The upgrade package is encrypted to obtain an encrypted upgrade package.

4. A remote maintenance method for medical equipment, characterized in that: The remote maintenance method is applied to a device end, the device end is connected to a management end for communication, and the remote maintenance method includes: Sending an upgrade request instruction to the management terminal according to the received synchronous upgrade instruction sent by the management terminal; The device to be upgraded on the equipment side is upgraded according to the received target upgrade package sent by the management side.

5. The remote maintenance method according to claim 4, characterized in that: The device to be upgraded includes a main board and a defibrillator paddle; The method includes: upgrading the device to be upgraded on the equipment side according to the received target upgrade package sent by the management side, including: If the device to be upgraded is a mainboard, the mainboard is upgraded according to the target upgrade package received from the management terminal; If the device to be upgraded is a defibrillator paddle, after the main board receives the target upgrade package sent by the management terminal, the target upgrade package is sent to the defibrillator paddle, and the defibrillator paddle is upgraded according to the received target upgrade package.

6. The remote maintenance method according to claim 4, characterized in that: After the device to be upgraded on the equipment side is upgraded according to the received target upgrade package sent by the management side, the method further includes: If the device to be upgraded on the equipment side is upgraded successfully, an upgrade success instruction is sent to the management side; If the device to be upgraded on the device side fails to be upgraded, the device to be upgraded on the device side is restored to the version corresponding to the original version number.

7. A remote maintenance device for medical equipment, characterized in that: The remote maintenance device is applied to the management end, the management end is connected to the device end in communication, and the remote maintenance device includes: A determination module, configured to determine a target upgrade task matching the upgrade request instruction according to the received upgrade request instruction sent by the device end; The first sending module is used to send the target upgrade package in the target upgrade task to the device end, so that the device end upgrades the device to be upgraded according to the target upgrade package.

8. A remote maintenance device for medical equipment, characterized in that: The remote maintenance device is applied to the device end, the device end is connected to the management end for communication, and the remote maintenance device includes: A second sending module, configured to send an upgrade request instruction to the management terminal according to the received synchronous upgrade instruction sent by the management terminal; The upgrade module is used to upgrade the device to be upgraded on the equipment side according to the target upgrade package received from the management side.

9. A computer device, characterized in that: The computer device includes a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the remote maintenance method according to any one of claims 1 to 6 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the remote maintenance method according to any one of claims 1 to 6 is implemented.

Images