Medical robotic management systems, methods, devices, and media

Abstract

The application provides a medical robot management system, method, electronic equipment and storage medium, the management system comprises a data server, a local management server and a robot workstation, the data server is connected with the local management server through the Internet, and the local management server is connected with the robot workstation through a local area network; the robot workstation is configured to collect robot data of a medical robot, and send corresponding robot data to the local management server according to a backup data request instruction sent by the local management server; the local management server is configured to backup the received robot data; and the data server is configured to receive the robot data sent by the local management server and store the data according to an upload data request instruction sent by the local management server. The application can reduce the dependence on a U disk in the data transmission process and improve the safety in the data access process.

Description

Technical Field

[0001] This invention relates to the field of medical robot technology, and in particular to a medical robot management system, method, electronic device, and storage medium. Background Technology

[0002] Medical robots refer to robots used in hospitals and clinics for medical or auxiliary medical procedures. Taking surgical robots as an example, their design concept is to perform complex surgical procedures with precision using minimally invasive methods. Given the various limitations of traditional surgery, surgical robots have been developed to replace traditional surgery. Surgical robots overcome the limitations of the human eye, employing stereoscopic imaging technology to present internal organs to the operator with greater clarity. In areas where hands previously could not reach, robotic arms can perform 360-degree rotation, movement, swinging, and gripping, while avoiding tremors. Smaller incisions, less bleeding, and faster recovery significantly shorten postoperative hospital stays, and postoperative survival and recovery rates are also significantly improved, making them popular with both doctors and patients. Now, as a high-end medical device, they are widely used in various clinical surgeries.

[0003] Due to security and hospital privacy requirements, medical robots are not allowed to update or upload data online; data maintenance can only be performed manually. Currently, backing up medical robot data requires inserting a USB flash drive into the industrial computer's USB port and manually copying the relevant data from the computer to the flash drive. Similarly, updating the firmware requires inserting a USB flash drive into the industrial computer's USB port and manually copying the firmware to the computer and installing it. Health monitoring of the medical robot requires using various analysis tools on different platforms to analyze the device list, operating parameters, and device lifespan. Finally, memory maintenance requires manually backing up the robot's data before deleting any historical data stored on the robot.

[0004] However, copying data to medical robots using USB flash drives is not only cumbersome but also prone to leaking the robot's operating parameters, posing serious security risks. Furthermore, when using USB flash drives for firmware maintenance and upgrades, maintenance personnel cannot obtain the latest firmware system or update important system patches in a timely manner. In addition, existing medical robots cannot perform comprehensive preoperative health checks, increasing the probability of the robot becoming isolated during surgery, affecting the procedure and potentially causing failure. Moreover, because the robot's operational data is stored on the robot itself for extended periods, it cannot be updated to the maintenance database for timely health assessments, leading to decreased reliability. Simultaneously, current technology cannot provide timely and effective online detection, configuration, and consistency updates for software updates, virus definitions, and network security of medical robots.

[0005] It should be noted that the information disclosed in the background section of this invention is intended only to enhance the understanding of the general background of this invention, and should not be construed as an admission or in any way implying that the information constitutes prior art known to those skilled in the art. Summary of the Invention

[0006] The purpose of this invention is to provide a medical robot management system, method, electronic device, and storage medium that can reduce the reliance on USB flash drives during medical robot data transmission and improve the security of data access.

[0007] To achieve the above objectives, the present invention provides a medical robot management system, including a data server, a local management server, and a robot industrial control computer. The data server and the local management server are connected via the Internet, and the local management server and the robot industrial control computer are connected via a local area network.

[0008] The robot industrial control computer is configured to collect robot data from the medical robot and send the corresponding robot data to the local management server according to the backup data request instruction sent by the local management server;

[0009] The local management server is configured to back up the received robot data;

[0010] The data server is configured to receive robot data sent by the local management server according to the upload data request instruction sent by the local management server and store it accordingly.

[0011] Optionally, the robot industrial control computer is configured to send robot data to the local management server through the following steps:

[0012] Find the timestamp information of the latest locally collected robot data;

[0013] Based on the timestamp information of the latest locally collected robot data and the timestamp information of the last time robot data was successfully sent to the local management server, it is determined whether there is updated robot data locally;

[0014] If so, the updated robot data is sent to the local management server, and the corresponding timestamp is recorded after successful transmission.

[0015] Optionally, the robot industrial control computer is further configured to authenticate the local management server during communication with the local management server through the following process:

[0016] Receive the public key certificate sent by the local management server;

[0017] The validity of the public key certificate is verified using a local CA certificate;

[0018] If the verification is successful, the encryption key sent by the local management server will be received.

[0019] The encryption key is decrypted using the public key in the public key certificate to obtain the corresponding key, thereby completing the authentication of the local management server.

[0020] Optionally, the data server is further configured to classify and manage the software packages of the medical robot, and to send the corresponding software packages to the local management server according to the software package synchronization request instruction sent by the local management server;

[0021] The local management server is also configured to classify and manage the received software packages;

[0022] The robot's industrial control computer is also configured to receive and install the software package sent by the local management server.

[0023] Optionally, the data server and the local management server are configured to classify and manage the software packages using a multi-level file directory structure.

[0024] Optionally, the data server is also configured to manage the detection models of the medical robot, and send the corresponding detection models to the local management server according to the detection model synchronization request instruction sent by the local management server;

[0025] The local management server is also configured to detect the health status of the medical robot based on the detection model.

[0026] Optionally, the local management server is further configured to record maintenance data of the medical robot and send the maintenance data to the data server for storage;

[0027] The data server is also configured to send corresponding maintenance data to the local management server according to the maintenance data synchronization request instruction sent by the local management server.

[0028] Optionally, the local management server is configured to detect the health status of the medical robot through the following process:

[0029] Send a health check request command to the robot's industrial control computer;

[0030] Receive the ID of the medical robot sent by the robot's industrial control computer;

[0031] Based on the ID of the medical robot, the detection model and maintenance data corresponding to the medical robot are retrieved locally;

[0032] Send a self-test data request command to the robot industrial control computer, and receive the self-test data of the medical robot sent by the robot industrial control computer;

[0033] Based on the self-test data, detection model, and maintenance data of the medical robot, the health status detection results of the medical robot are obtained.

[0034] Optionally, the detection model includes any one or more of the following: usage limit information of basic components, operating distance limit information, usage limit information of device consumables, resource occupation limit information, and operating temperature limit information.

[0035] Optionally, the local management server is also configured to display the health status detection results of the medical robot in the form of a list.

[0036] To achieve the above objectives, the present invention also provides a medical robot management method, applied to the robot industrial control computer in the medical robot management system described above, the medical robot management method comprising:

[0037] Collect robot data from medical robots;

[0038] According to the backup data request instruction sent by the local management server, the corresponding robot data is sent to the local management server;

[0039] The local management server sends an upload data request command to the data server and sends the corresponding robot data to the data server for storage.

[0040] To achieve the above objectives, the present invention also provides a medical robot management method, applied to a local management server in the medical robot management system described above, the medical robot management method comprising:

[0041] Send a backup data request command to the robot's industrial control computer;

[0042] Receive robot data sent by the robot's industrial control computer;

[0043] Send an upload data request instruction to the data server, and send the corresponding robot data to the data server for storage according to the upload data request instruction.

[0044] To achieve the above objectives, the present invention also provides a medical robot management method, applied to the data server in the medical robot management system described above, the medical robot management method comprising:

[0045] The local management server sends a backup data request command to the robot industrial control computer, so that the robot industrial control computer sends the corresponding robot data to the local management server.

[0046] Receive the data upload request instruction sent by the local management server;

[0047] Receive robot data sent by the local management server and store the robot data accordingly.

[0048] To achieve the above objectives, the present invention also provides an electronic device, including a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the medical robot management method described above is implemented.

[0049] To achieve the above objectives, the present invention also provides a readable storage medium storing a computer program, which, when executed by a processor, implements the medical robot management method described above.

[0050] Compared with the prior art, the medical robot management system, method, electronic device, and storage medium provided by the present invention have the following advantages:

[0051] The medical robot management system provided by this invention includes a data server, a local management server, and a robot industrial control computer. The data server and the local management server are connected via the Internet, and the local management server and the robot industrial control computer are connected via a local area network (LAN). The robot industrial control computer is configured to collect robot data from the medical robot and send corresponding robot data to the local management server according to a backup data request instruction sent by the local management server. The local management server is configured to back up the received robot data. The data server is configured to receive the robot data sent by the local management server according to an upload data request instruction sent by the local management server and store it accordingly. Therefore, the medical robot management system provided by this invention, through the local management server, can perform off-site backup of robot data within the local area network system without the use of a USB flash drive. This not only automatically frees up local disk space on the robot industrial control computer but also effectively prevents data leakage during transmission, improving the security of robot data transmission. Furthermore, since the local management server and the robot industrial control computer communicate via a local area network, data transmission between the local management server and the robot industrial control computer can be supported even in surgical environments without a network (no external network).

[0052] Since the medical robot management method, electronic device and storage medium provided by this invention belong to the same inventive concept as the medical robot management system provided by this invention, the medical robot management method, electronic device and storage medium provided by this invention have all the advantages of the medical robot management system provided by this invention. Therefore, the beneficial effects of the medical robot management method, electronic device and storage medium provided by this invention will not be described in detail here. Attached Figure Description

[0053] Figure 1 This is a schematic diagram illustrating an application scenario of the surgical robot provided in one embodiment of the present invention;

[0054] Figure 2 This is a schematic diagram of the structure of a patient trolley provided in one embodiment of the present invention;

[0055] Figure 3 A schematic diagram of the structure of a doctor's control console provided in one embodiment of the present invention;

[0056] Figure 4 A block diagram illustrating the structure of a medical robot management system according to an embodiment of the present invention;

[0057] Figure 5 A schematic diagram of a robot data storage strategy provided in one embodiment of the present invention;

[0058] Figure 6 This is a schematic diagram of the data interaction process between a robot industrial control computer and a local management server according to an embodiment of the present invention;

[0059] Figure 7 This is a schematic diagram illustrating the process of uploading robot data to a local management server according to an embodiment of the present invention.

[0060] Figure 8 A schematic diagram of the identity authentication process between a local management server and the data server provided in one embodiment of the present invention;

[0061] Figure 9 This is a schematic diagram of the identity authentication process between a robot industrial control computer and a local management server according to an embodiment of the present invention;

[0062] Figure 10 A schematic diagram illustrating a software package classification management strategy provided in one embodiment of the present invention;

[0063] Figure 11 A schematic diagram illustrating the process of downloading software packages from a local management server according to an embodiment of the present invention;

[0064] Figure 12 A schematic diagram of a detection model provided according to an embodiment of the present invention;

[0065] Figure 13 This is a schematic diagram illustrating the specific process for detecting the health status of a medical robot according to an embodiment of the present invention.

[0066] Figure 14 This is a schematic diagram showing the health status detection results of a medical robot according to an embodiment of the present invention;

[0067] Figure 15 A flowchart illustrating a medical robot management method according to an embodiment of the present invention;

[0068] Figure 16 A flowchart illustrating a medical robot management method according to another embodiment of the present invention;

[0069] Figure 17 A flowchart illustrating a medical robot management method according to another embodiment of the present invention;

[0070] Figure 18 This is a block diagram of an electronic device provided according to an embodiment of the present invention. Detailed Implementation

[0071] The medical robot management system, method, electronic device, and storage medium proposed in this invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. The advantages and features of this invention will become clearer from the following description. It should be noted that the drawings are in a very simplified form and use non-precise proportions, used only to facilitate and clarify the illustration of the embodiments of this invention. Please refer to the drawings to make the objectives, features, and advantages of this invention more apparent and understandable. It should be understood that the structures, proportions, sizes, etc., depicted in the accompanying drawings are only for illustrative purposes and to enable those skilled in the art to understand and read them, and are not intended to limit the implementation conditions of this invention. Any modifications to the structure, changes in proportions, or adjustments to the size, provided that the effects and objectives achieved by this invention are the same or similar, should still fall within the scope of the technical content disclosed in this invention.

[0072] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0073] Furthermore, in the description of this specification, the reference to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., means that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in a suitable manner in any one or more embodiments or examples. Furthermore, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0074] The core idea of ​​this invention lies in providing a medical robot management system, method, electronic device, and storage medium, which can reduce the reliance on USB flash drives during data transmission in medical robots and improve the security of data access. It should be noted that, as those skilled in the art will understand, the electronic device provided by this invention can be a personal computer, a mobile terminal, etc., and the mobile terminal can be a mobile phone, tablet computer, or other hardware device with various operating systems. Furthermore, it should be noted that although this invention uses a surgical robot as an example of a medical robot, as those skilled in the art will understand, this invention does not limit the application field of medical robots; the medical robot can also be other medical robots besides surgical robots used in the surgical field, such as rehabilitation robots.

[0075] Example 1

[0076] To achieve the above ideas, this embodiment provides a medical robot management system. For ease of understanding, before introducing the medical robot management system provided in this embodiment, we will first use a surgical robot as an example to illustrate the application scenarios of medical robots. Please refer to... Figure 1 The diagram illustrates an application scenario of the surgical robot provided in the first embodiment of this work. Figure 1 As shown, the surgical robot includes a doctor's console 100, a patient carriage 200, and an image carriage 300 that are connected in communication.

[0077] Please continue to refer to this. Figure 2 The diagram illustrates the structure of the patient cart provided in the first embodiment of this work. Figure 2 As shown, the patient trolley 200 includes a first base 210 and at least one robotic arm 220 mounted on the first base 210. A surgical instrument 400 and an endoscope 500 are mounted at the end of at least one robotic arm 220. It should be noted that, as those skilled in the art will understand, when only one robotic arm 220 is provided on the first base 210, the surgical instrument 400 and the endoscope can be mounted on the same robotic arm 220; when multiple robotic arms 220 are provided on the first base 210, the surgical instrument 400 and the endoscope 500 can be mounted on different robotic arms 220.

[0078] Specifically, the surgical instrument 400 and the endoscope 500 can be inserted into the patient's body through a puncture hole on the patient's surface. The endoscope 500 can acquire endoscopic images, specifically including images of human tissues and organs, surgical instruments 400, blood vessels, and body fluids, etc., of the surgical scene. The acquired endoscopic images can be transmitted to the first display unit 310 of the image carriage 300 (for ease of distinction, the display components on the image carriage 300 are referred to as the first display unit 310, and the display components on the doctor's control console 100 are referred to as the second display unit 120) for display.

[0079] Please continue to refer to this. Figure 3 The diagram illustrates the structure of the doctor's control console provided in the first embodiment of this work. Figure 3 As shown, the doctor's console 100 includes at least one main control arm 110. During surgery, the operator (i.e., the doctor) sitting at the doctor's console 100 can control the movement of the surgical instruments 400 and endoscope 500 located on the robotic arm 220 by manipulating the main control arm 110, thereby completing various operations to achieve the purpose of performing surgery on the patient. In actual operation, the operator observes the transmitted endoscopic images through the second display unit 120 on the doctor's console 100, and controls the movement of the surgical instruments 400 and endoscope 500 located on the robotic arm 220 by manipulating the main control arm 110.

[0080] Furthermore, such as Figure 3 As shown, the doctor's console 100 also includes a second base 130. The main control arm 110 and the second display unit 120 are both mounted on the second base 130. The second base 130 is equipped with a foot switch (not shown) to detect the switching control signal issued by the operator. The operator can control some actions through the foot switch, such as inputting related operations like electrocautery and electrocoagulation.

[0081] Please continue to refer to this. Figure 1 ,like Figure 1 As shown, in one exemplary embodiment, the surgical robot further includes a tool cart 600 for storing surgical instruments 400 and auxiliary carts 700 (including a ventilator and anesthesia machine) for use during surgery. It should be noted that, as those skilled in the art will understand, these auxiliary carts 700 can be selected and configured according to existing technology, and therefore will not be described in detail here. Furthermore, it should be noted that more information regarding the working principles of the surgical robot can be found in existing technology, and will not be elaborated upon here.

[0082] Please continue to refer to this. Figure 4The diagram illustrates the block structure of the medical robot management system provided in the first embodiment of this work. Figure 4 As shown, the medical robot management system provided in this embodiment includes a data server 10, a local management server 20, and a robot industrial control computer 30. The data server 10 and the local management server 20 are connected via the Internet, and the local management server 20 and the robot industrial control computer 30 are connected via a local area network. The robot industrial control computer 30 is configured to collect robot data from the medical robot and send corresponding robot data to the local management server 20 according to the backup data request instruction sent by the local management server 20. The local management server 20 is configured to back up the received robot data. The data server 10 is configured to receive the robot data sent by the local management server 20 according to the upload data request instruction sent by the local management server 20 and store it accordingly.

[0083] Therefore, the medical robot management system provided by this invention can perform off-site backup of robot data within a local area network system without the need for a USB flash drive, through the local management server 20. This not only automatically frees up local disk space on the robot industrial control computer 30, but also effectively prevents data leakage during transmission, improving the security of robot data transmission. Furthermore, since the local management server 20 and the robot industrial control computer 30 communicate via a local area network, data transmission between them can be supported even in surgical environments without a network (no external network).

[0084] It should be noted that, as those skilled in the art will understand, each medical robot corresponds to a unique robot industrial control computer 30. When the medical robot is the surgical robot described above, the robot industrial control computer 30 can be located at the doctor's control console 100, the patient carriage 200, or the image carriage 300, etc. In some embodiments, the robot industrial control computer 30 can also be set up independently, and this embodiment does not limit this. Furthermore, it should be noted that, as those skilled in the art will understand, the local management server 20 is freely movable and can be installed on a laptop or desktop computer. The same local management server 20 can communicate with multiple robot industrial control computers 30, and the same robot industrial control computer 30 can also communicate with multiple local management servers 20.

[0085] Specifically, such as Figure 4As shown, the data server 10 includes a first data storage module 11 and a first communication module 12. The first data storage module 11 is configured to store received robot data, and the first communication module 12 is configured to establish a communication connection between the data server 10 and the local management server 20. The local management server 20 includes a second data storage module 21, a second communication module 22, and a third communication module 23. The second data storage module 21 is configured to store backed-up robot data, the second communication module 22 is configured to establish a communication connection between the local management server 20 and the data server 10, and the third communication module 23 is configured to establish a communication connection between the local management server 20 and the robot industrial control computer 30. The robot industrial control computer 30 includes a data acquisition module 31 and a fourth communication module 32. The data acquisition module 31 is configured to acquire robot data corresponding to the medical robot, and the fourth communication module 32 is configured to establish a communication connection between the robot industrial control computer 30 and the local management server 20. Therefore, the first communication module 12 and the second communication module 22 can communicate via the Internet, thereby enabling data interaction between the data server 10 and the local management server 20; the third communication module 23 and the fourth communication module 32 can communicate via a local area network, thereby enabling data interaction between the local management server 20 and the robot industrial control computer 30. Thus, when internet access (external network) is unavailable in the operating room, the local management server 20 can use a time-sharing connection to solve the problem of robot data transmission failure. Specifically, outside the operating room, the local management server 20 and the data server 10 can communicate via the Internet (external network); inside the operating room, the local management server 20 and the robot industrial control computer 30 can communicate via a local area network.

[0086] In one exemplary embodiment, the robot industrial computer 30 is configured to send robot data to the local management server 20 through the following steps:

[0087] Find the timestamp information of the latest locally collected robot data;

[0088] Based on the timestamp information of the latest locally collected robot data and the timestamp information of the last time robot data was successfully sent to the local management server 20, it is determined whether there is updated robot data locally;

[0089] If so, the updated robot data is sent to the local management server 20, and the corresponding timestamp is recorded after successful transmission.

[0090] Specifically, if the timestamp of the latest robot data collected locally by the robot industrial control computer 30 is later than the timestamp of the last successful transmission of robot data to the local management server 20, it indicates that the robot data locally collected by the robot industrial control computer 30 has been updated. Then, based on the timestamp of the robot data stored locally by the robot industrial control computer 30 and the timestamp of the last successful transmission of robot data to the local management server 20, all updated robot data (i.e., all newly collected robot data after the last successful transmission of robot data to the local management server 20) can be found and sent to the local management server 20. After all the updated robot data has been sent, the corresponding timestamp is recorded.

[0091] Furthermore, the robot data includes log data and device data. The log data is stored in the form of log files, and the device data is stored in a database. Therefore, the robot industrial control computer 30 can search the local log file directory to find the timestamp information of the latest log file creation, thereby identifying all updated log data. Similarly, the robot industrial control computer 30 can search the database to find the timestamp information of the latest piece of device data, thereby identifying all updated device data.

[0092] Please continue to refer to this. Figure 5 The diagram illustrates the robot data storage strategy provided in the first embodiment of this diagram. Figure 5 As shown, each robot industrial control computer 30 has a unique ID (i.e., each medical robot has a unique ID). Each robot industrial control computer 30 independently stores log files (log data) and device data, wherein the device data is stored in its local database DB. The same local management server 20 can back up robot data (including log data and device data) from different robot industrial control computers 30, and the local management server 20 allocates a storage space for each medical robot and saves the corresponding robot data based on the medical robot's ID (i.e., the ID of the corresponding robot industrial control computer 30). The data server 10 also allocates a storage space for each medical robot and saves the corresponding robot data based on the medical robot's ID (i.e., the ID of the corresponding robot industrial control computer 30).

[0093] In one exemplary embodiment, the robot industrial control computer 30 is further configured to send a data update completion command to the local management server 20 after the updated robot data has been successfully sent. Therefore, by having the robot industrial control computer 30 send an update completion command to the local management server 20 after all updated robot data has been successfully sent, it is easier for medical robot maintenance personnel to understand the update status of the robot data.

[0094] Please continue to refer to this. Figure 6 This illustration shows a schematic diagram of the data interaction process between the robot industrial control computer 30 and the local management server 20 provided in the first embodiment of this invention. Figure 6 As shown, the local management server 20 can proactively initiate a connection request to the robot industrial control computer 30 to avoid repeated communication connection operations by the medical robot. After successfully establishing a connection with the robot industrial control computer 30, the local management server 20 sends a backup data request command to the robot industrial control computer 30. After successfully receiving the backup data request command, the robot industrial control computer 30 retrieves the latest local robot data to determine if the local robot data has been updated. If so, it sends the updated robot data to the local management server 20. The local management server 20 receives the robot data and saves it to its local database. After sending all the updated robot data, the robot industrial control computer 30 also sends a data update completion command to the local management server 20.

[0095] Please continue to refer to this. Figure 7 This illustration shows a flowchart of the process of uploading robot data by the local management server 20 provided in the first embodiment of this invention. Figure 7As shown, the local management server 20 connects to the data server 10 via the IP address and port configured in the system. After a successful connection, the local management server 20 can send an upload data request command through, but not limited to, the UI interface. The fields of the upload data request command may include: upload data, the ID of the medical robot, data type, and size, etc. Specifically, when log data needs to be uploaded, the data type in the upload data request command field is log data, that is, the upload data request command sent by the local management server 20 is an upload log data request command, to inform the data server 10 that it will send the relevant medical robot log data next, and then start to retrieve the log data that has not been synchronized locally (i.e., has not yet been sent to the data server 10) and send it to the data server 10. When device data needs to be uploaded, the data type in the upload data request command field is device data, that is, the upload data request command sent by the local management server 20 is an upload device data request command, to inform the data server 10 that it will send the relevant medical robot device data next, and then start to retrieve the device data that has not been synchronized locally (i.e., has not yet been sent to the data server 10) and send it to the data server 10.

[0096] Please continue to refer to this. Figure 4 ,like Figure 4 As shown, in one exemplary embodiment, the data server 10 further includes a first authentication module 13, and the local management server 20 further includes a second authentication module 24. Thus, through the first authentication module 13 and the second authentication module 24, authentication can be achieved between the local management server 20 and the data server 10 during the establishment of a communication connection, effectively preventing unauthorized access and further improving the security and reliability of data interaction.

[0097] Furthermore, the local management server 20 and the data server 10 use the standard HTTPS protocol for authentication. For details, please refer to... Figure 8 This illustration shows the identity authentication process between the local management server 20 and the data server 10 provided in the first embodiment of this diagram. Figure 8As shown, after receiving a connection request initiated by the local management server 20, the data server 10 sends a CA certificate to the local management server 20. After receiving the CA certificate, the local management server 20 decrypts the CA certificate to obtain the public key, and uses the public key to encrypt the generated key to obtain the encryption key. The encryption key is then sent to the data server 10. After receiving the encryption key, the data server 10 decrypts the encryption key using the corresponding private key to obtain the key, thereby completing the identity authentication between the two parties. The data server 10 and the local management server 20 can then interact with each other using the key in subsequent communication processes.

[0098] Please continue to refer to this. Figure 4 ,like Figure 4 As shown, in one exemplary embodiment, the robot industrial control computer 30 further includes a third identity authentication module 33, which is configured to authenticate the local management server 20 during the establishment of a communication connection with the local management server 20. This prevents malicious access of the local management server 20 to the robot industrial control computer 30. Furthermore, it allows the same robot industrial control computer 30 (i.e., the same medical robot) to interact with multiple local management servers 20, enabling different maintenance personnel to perform data management and other operations on the same robot industrial control computer 30 (i.e., the same medical robot) through their respective local management servers 20.

[0099] Furthermore, the robot industrial control computer 30 is configured to authenticate the local management server 20 during communication with the local management server 20 through the following process:

[0100] Receive the public key certificate sent by the local management server 20;

[0101] The validity of the public key certificate is verified using a local CA certificate;

[0102] If the verification is successful, the encryption key sent by the local management server 20 will be received.

[0103] The encryption key is decrypted using the public key in the public key certificate to obtain the corresponding key, thereby completing the authentication of the local management server 20.

[0104] For details, please refer to Figure 9 This illustration shows the identity authentication process between the robot industrial control computer 30 and the local management server 20 provided in the first embodiment of this invention. Figure 9As shown, the local management server 20 first reads the local public key certificate, and then sends the public key certificate to the robot industrial control computer 30 via communication protocols such as TCP / IP. After receiving the public key certificate sent by the local management server 20, the robot industrial control computer 30 verifies the validity of the public key certificate using its local CA certificate. If the verification result is valid, communication continues; otherwise, communication is disconnected. After the public key certificate is verified, the local management server 20 generates a key and encrypts it using its private key before sending it to the robot industrial control computer 30. After receiving the encryption key, the robot industrial control computer 30 decrypts the encryption key using the public key in the public key certificate to obtain the key, thereby completing the identity authentication between the robot industrial control computer 30 and the local management server 20. The robot industrial control computer 30 and the local management server 20 can then exchange data using the key during subsequent communication.

[0105] In one exemplary embodiment, the data server 10 is further configured to classify and manage the software packages of the medical robot, and to send the corresponding software packages to the local management server 20 according to the software package synchronization request instruction sent by the local management server 20.

[0106] The local management server 20 is also configured to classify and manage the received software packages;

[0107] The robot industrial control computer 30 is also configured to receive and install the software package sent by the local management server 20.

[0108] Therefore, the medical robot management system provided by this invention can also uniformly update the software and important system patches of the medical robot within a local area network system without the use of a USB flash drive, through the local management server 20, thereby ensuring the consistency and stability of the software system after the update. It should be noted that, as those skilled in the art will understand, the data in the software package includes system software data and system patch data. It should also be noted that, as those skilled in the art will understand, the local management server 20 can batch download the software packages required by the medical robot to upgrade the software of the medical robot.

[0109] For details, please continue to refer to Figure 4 ,like Figure 4As shown, the data server 10 further includes a first software package management module 14, which is configured to classify and manage software packages stored on the data server 10. The local management server 20 further includes a second software package management module 25, which is configured to classify and manage software packages stored on the local management server 20. The robot industrial control computer 30 further includes a software upgrade module 34, which is configured to update and upgrade the software of the medical robot according to the received software packages.

[0110] Furthermore, the data server 10 (specifically the first software package management module 14) and the local management server 20 (specifically the second software package management module 25) are configured to manage the software packages using a multi-level file directory structure. Therefore, by using a multi-level file directory structure to manage the software packages, it is easier to implement categorized management of the software packages.

[0111] For details, please refer to Figure 10 This illustration shows a schematic diagram of the software package classification and management strategy provided in the first embodiment of this work. Figure 10 As shown, a primary file directory can be created based on the type of medical robot, such as a primary file directory for laparoscopic robots, orthopedic robots, etc. Additionally, a primary file directory for common applications can be created to store common software packages unrelated to the type of medical robot. Each primary directory can be further divided into multiple secondary file directories based on the specific model of the medical robot, such as XX robot generation 1, XX robot generation 5, etc. The robots can be of the same type or different types, such as laparoscopic surgical robots, bronchial surgical robots, etc. Each secondary file directory can be further divided into multiple tertiary file directories based on a specific project, with each tertiary file directory storing all software packages for the corresponding project. Furthermore, a tertiary file directory for common applications can be created under each secondary file directory to store common software packages for the model (e.g., XX generation 1) of the medical robot corresponding to that secondary file directory.

[0112] Please continue to refer to this. Figure 11 This illustration shows a flowchart of the local management server 20 downloading software packages according to the first embodiment of this diagram. Figure 11As shown, the local management server 20 can connect to the data server 10 via the IP address and port configured in the system. After a successful connection, the local management server 20 can send a software package synchronization request command through, but not limited to, the UI interface. The fields of the software package synchronization request command may include: synchronize software package data, robot type, robot model, and software package name. For example, when the fields of the software package synchronization request command are: synchronize software package data, XX robot, XX1 generation, Project1, it indicates that all software packages related to Project1 for the medical robot of type XX robot and model XX1 generation under the Project1 project need to be synchronized. After receiving the software package synchronization request command, the data server 10 finds the corresponding software package and sends it to the local management server 20. The local management server 20 receives the software package and processes it according to... Figure 10 The classification management strategy shown stores the received software packages.

[0113] Please continue to refer to this. Figure 11 ,like Figure 11 As shown, the local management server 20 is also configured to detect whether all software packages have been received (i.e., whether the software packages have been successfully synchronized). If so, the local management server 20 will display a notification via, but not limited to, a UI pop-up indicating that the software package synchronization is complete. Therefore, by issuing a notification that the software package synchronization is complete after receiving all software packages, the local management server 20 can facilitate subsequent operations for maintenance personnel.

[0114] In one exemplary embodiment, the data server 10 is also configured to manage the detection models of the medical robot and send the corresponding detection models to the local management server 20 according to the detection model synchronization request instruction sent by the local management server 20.

[0115] The local management server 20 is also configured to detect the health status of the medical robot according to the detection model.

[0116] Therefore, the medical robot management system provided in this embodiment can perform health checks on medical robots (surgical robots) in a surgical environment without a network (no external network), which improves the safety and reliability of the surgical process and reduces the probability of isolated operation during the surgical process.

[0117] For details, please continue to refer to Figure 4 ,like Figure 4As shown, the data server 10 further includes a first detection model management module 15, which is configured to manage the detection models stored on the data server 10. The local management server 20 further includes a second detection model management module 26 and a health detection module 27. The second detection model management module 26 is configured to manage the detection models stored on the local management server 20, and the health detection module 27 is configured to detect the health status of the medical robot based on the detection models.

[0118] In one exemplary implementation, the detection model includes any one or more of the following: usage limit information for basic components, operating distance limit information, usage limit information for device consumables, resource usage limit information, and operating temperature limit information.

[0119] For details, please refer to Figure 12 The diagram illustrates the detection model provided in the first embodiment of this text. Figure 12 As shown, the basic components include, but are not limited to, slide rails, steel wires, and foot pedals. Each basic component has its own usage limit or operating distance limit. For example, the safe operating distance limit for a slide rail is 1000m. The operating distance of a medical robot (surgical robot) in a single surgery is approximately 50m. After each surgery, the robot's industrial control computer 30 records the operating distance of the slide rail. Instrument consumables include, but are not limited to, needle forceps, ultrasonic scalpels, and straight scissors. Each instrument consumable has its own usage limit. For example, the needle forceps cannot be used more than 10 times. The usage limit increases by one for each surgery performed. Resource usage is also a factor affecting the stability of the medical robot; therefore, resource usage needs to be limited. For example, the CPU utilization limit is 80%. If the current CPU utilization exceeds 80%, an alarm is triggered. Operating temperature is also a factor affecting the stability of the medical robot; therefore, the operating temperature needs to be limited. For example, the operating temperature limit is 60℃. If the current operating temperature exceeds 60℃, an alarm is triggered. It should be noted that, as those skilled in the art will understand… Figure 12 The detection model shown is merely an illustrative example and does not constitute a limitation of the present invention. The specific data in the detection model can be set according to the specific circumstances of the medical robot.

[0120] In one exemplary embodiment, the local management server 20 is further configured to record maintenance data of the medical robot and send the maintenance data to the data server 10 for storage;

[0121] The data server 10 is also configured to send corresponding maintenance data to the local management server 20 according to the maintenance data synchronization request instruction sent by the local management server 20.

[0122] Therefore, the medical robot management system provided by this invention records the maintenance data of the medical robot, which makes it easy for maintenance personnel to check the maintenance data of the medical robot in a timely manner, so as to provide data support for the health monitoring of the medical robot.

[0123] Please continue to refer to this. Figure 4 ,like Figure 4 As shown, the data server 10 further includes a first maintenance data management module 16, which is configured to manage the maintenance data of the medical robot stored on the data server 10. The local management server 20 further includes a second maintenance data management module 28, which is configured to manage the maintenance data of the medical robot stored on the local management server 20.

[0124] Furthermore, the local management server 20 is configured to detect the health status of the medical robot through the following process:

[0125] Send a health check request command to the robot's industrial control computer 30;

[0126] Receive the ID of the medical robot sent by the robot industrial control computer 30;

[0127] Based on the ID of the medical robot, the detection model and maintenance data corresponding to the medical robot are retrieved locally;

[0128] Send a self-test data request command to the robot industrial control computer 30, and receive the self-test data of the medical robot sent by the robot industrial control computer 30;

[0129] Based on the self-test data, detection model, and maintenance data of the medical robot, the health status detection results of the medical robot are obtained.

[0130] For details, please refer to Figure 13 This illustration shows a schematic diagram of the specific process for detecting the health status of a medical robot according to the first embodiment of this invention. Figure 13As shown, the local management server 20 sends a health check request command to the robot industrial control computer 30 of the medical robot that needs to undergo health check. The triggering method includes, but is not limited to, clicking the health check button on the UI interface. After receiving the health check request command, the robot industrial control computer 30 sends the ID of the medical robot to the local management server 20. After receiving the ID of the medical robot, the local management server 20 matches the locally synchronized detection model and the locally synchronized maintenance data according to the obtained medical robot ID. Then, it obtains the self-check data of the medical robot from the robot industrial control computer 30. Then, based on the self-check data, detection model and maintenance data of the medical robot, it comprehensively evaluates the health status of the medical robot and outputs the health status detection report (i.e., health status detection result) of the medical robot.

[0131] Please continue to refer to this. Figure 4 ,like Figure 4 As shown, the robot industrial control computer 30 also includes a system detection module 35, which is configured to detect the current state of the medical robot in order to collect the self-test data of the medical robot.

[0132] In one exemplary embodiment, the local management server 20 is also configured to display the health status detection results of the medical robot in a list format.

[0133] For details, please refer to Figure 14 This diagram schematically illustrates the display of the health status detection results of the medical robot provided in the first embodiment of this invention. Figure 14 As shown, by displaying the health status detection results of the medical robot in the form of a list, maintenance personnel can clearly see the specific content of each inspection item of the medical robot.

[0134] In one exemplary implementation, the local management server 20 is also configured to classify the health status level for each of the health status detection results of the medical robot.

[0135] like Figure 14 As shown, by classifying the health status level of each test result in the health status detection results of the medical robot, it is easier for maintenance personnel to predict the failure of the medical robot.

[0136] In one exemplary implementation, the health status levels include normal, dangerous, and warning, and the local management server 20 is further configured to identify detection items with a health status level of dangerous and / or warning.

[0137] Therefore, by marking detection items with a health status level of danger and / or warning, maintenance personnel can be more clearly alerted. Specifically, detection items with a health status level of danger can be marked in red, and detection items with a health status level of warning can be marked in yellow. Of course, as those skilled in the art will understand, other methods can also be used to mark detection items with a health status level of danger and / or warning, and this embodiment does not limit this.

[0138] In summary, the medical robot management system provided in this embodiment connects the data server 10 and the robot industrial control computer 30 via a time-sharing connection through a local management server 20, enabling data interaction. This solves the problems of difficult software upgrades and easy data leakage during backups when the medical robot cannot connect to the internet (cannot connect to the external network). The local management server 20 can be directly connected to the robot industrial control computer 30 of the medical robot via a network cable (local area network). Certificate authentication is used during communication, which not only reduces the reliance on USB drives during robot data backup but also prevents unauthorized access. Furthermore, the local management server 20 can synchronize the software package data of the data server 10, enabling consistent updates to the medical robot's software system and improving the stability of the medical robot during operation. Additionally, the local management server 20, through integrated detection models, can provide health checks (preoperative health checks) for the medical robot (surgical robot), simplifying the operations of maintenance personnel, providing timely fault prediction for the medical robot, and thus ensuring the smooth operation of the medical robot.

[0139] Example 2

[0140] Corresponding to the aforementioned medical robot management system, this embodiment provides a medical robot management method. In this embodiment, the executing entity of the medical robot management method is the robot industrial control computer 30 mentioned above. Please refer to... Figure 15 This illustration shows a flowchart of the medical robot management method provided in the first embodiment of this text. Figure 15 As shown, in this embodiment, the medical robot management method includes:

[0141] Step S110: Collect robot data from the medical robot.

[0142] Step S120: Send the corresponding robot data to the local management server 20 according to the backup data request instruction sent by the local management server 20.

[0143] Step S130: Send an upload data request instruction to the data server 10 through the local management server 20, and send the corresponding robot data to the data server 10 for corresponding storage through the local management server 20.

[0144] Therefore, the medical robot management method provided in this embodiment can perform off-site backup of robot data within a local area network system without the need for a USB flash drive, through the local management server 20. This not only automatically frees up local disk space on the robot industrial control computer 30, but also effectively prevents data leakage during transmission, improving the security of robot data transmission. Furthermore, since the local management server 20 and the robot industrial control computer 30 communicate via a local area network, data transmission between them can be supported even in surgical environments without a network (no external network).

[0145] In one exemplary embodiment, sending the corresponding robot data to the local management server 20 according to the backup data request instruction sent by the local management server 20 includes:

[0146] Find the timestamp information of the latest locally collected robot data;

[0147] Based on the timestamp information of the latest locally collected robot data and the timestamp information of the last time robot data was successfully sent to the local management server 20, it is determined whether there is updated robot data locally;

[0148] If so, the updated robot data is sent to the local management server 20, and the corresponding timestamp is recorded after successful transmission.

[0149] In one exemplary embodiment, before sending the corresponding robot data to the local management server 20 according to the backup data request instruction sent by the local management server 20, the medical robot management method further includes:

[0150] The local management server 20 is authenticated.

[0151] Furthermore, the authentication of the local management server 20 includes:

[0152] Receive the public key certificate sent by the local management server 20;

[0153] The validity of the public key certificate is verified using a local CA certificate;

[0154] If the verification is successful, the encryption key sent by the local management server 20 will be received.

[0155] The encryption key is decrypted using the public key in the public key certificate to obtain the corresponding key, thereby completing the authentication of the local management server 20.

[0156] In one exemplary embodiment, the medical robot management method further includes:

[0157] Receive a health check request command sent by the local management server 20;

[0158] Send the ID of the medical robot to the local management server 20 so that the local management server 20 can find the detection model and maintenance data corresponding to the medical robot locally based on the ID of the medical robot;

[0159] According to the self-test data request instruction sent by the local management server 20, the corresponding self-test data is sent to the local management server 20, so that the local management server 20 can obtain the health status detection result of the medical robot based on the self-test data, detection model and maintenance data of the medical robot.

[0160] In one exemplary embodiment, the medical robot management method further includes:

[0161] Receive the software package sent by the local management server 20 and install it.

[0162] Example 3

[0163] Corresponding to the medical robot management system described above, this embodiment provides a medical robot management method. In this embodiment, the executing entity of the medical robot management method is the local management server 20 mentioned above.

[0164] Please continue to refer to this. Figure 16 This illustration shows a flowchart of the medical robot management method provided in the first embodiment of this text. Figure 16 As shown, in this embodiment, the medical robot management method includes:

[0165] Step S210: Send a backup data request command to the robot industrial control computer 30.

[0166] Step S220: Receive robot data sent by the robot industrial control computer 30;

[0167] Step S230: Send an upload data request instruction to the data server 10, and send the corresponding robot data to the data server 10 for corresponding storage according to the upload data request instruction.

[0168] Therefore, the medical robot management method provided in this embodiment can perform off-site backup of robot data within a local area network system without the need for a USB flash drive, through the local management server 20. This not only automatically frees up local disk space on the robot industrial control computer 30, but also effectively prevents data leakage during transmission, improving the security of robot data transmission. Furthermore, since the local management server 20 and the robot industrial control computer 30 communicate via a local area network, data transmission between them can be supported even in surgical environments without a network (no external network).

[0169] In one exemplary embodiment, the medical robot management method further includes, prior to sending a backup data request instruction to the robot's industrial control computer 30:

[0170] Identity authentication is performed between the robot and the industrial control computer 30.

[0171] Specifically, the identity authentication between the robot industrial control computer 30 and the robot includes:

[0172] Send a public key certificate to the robot industrial control computer 30 so that the robot industrial control computer 30 can verify the validity of the public key certificate through its local CA certificate;

[0173] If the verification is successful, a key is generated and encrypted using the corresponding private key to obtain the encryption key;

[0174] The encryption key is sent to the robot industrial control computer 30 so that the robot industrial control computer 30 can decrypt the encryption key using the public key in the public key certificate to obtain the corresponding key, thereby completing the identity authentication between the robot industrial control computer 30 and the robot industrial control computer 30.

[0175] In one exemplary embodiment, the medical robot management method further includes, before sending an upload data request instruction to the data server 10:

[0176] Identity authentication is performed between the data server 10 and the data server 10.

[0177] Specifically, the identity authentication with the data server 10 includes:

[0178] Receive the CA certificate sent by the data server 10;

[0179] Decrypt the CA certificate to obtain the public key;

[0180] Generate a key and encrypt the key using the public key to obtain an encryption key;

[0181] The encryption key is sent to the data server 10 so that the server can decrypt the encryption key using the corresponding private key to obtain the corresponding key, thereby completing the identity authentication between the server and the data server 10.

[0182] In one exemplary embodiment, the data management method further includes:

[0183] Send a software package synchronization request instruction to the data server 10;

[0184] Receives software packages sent by the data server 10 and classifies and manages the received software packages;

[0185] The software package is sent to the robot's industrial control computer 30 for installation.

[0186] In one exemplary embodiment, the data management method further includes:

[0187] Send a health check request command to the robot's industrial control computer 30;

[0188] Receive the ID of the medical robot sent by the robot industrial control computer 30;

[0189] Based on the ID of the medical robot, the detection model and maintenance data corresponding to the medical robot are retrieved locally;

[0190] Send a self-test data request command to the robot industrial control computer 30, and receive the self-test data of the medical robot sent by the robot industrial control computer 30;

[0191] Based on the self-test data, detection model, and maintenance data of the medical robot, the health status detection results of the medical robot are obtained.

[0192] Example 4

[0193] Corresponding to the aforementioned medical robot management system, this embodiment provides a medical robot management method. In this embodiment, the executing entity of the medical robot management method is the data server 10 mentioned above. Please continue to refer to... Figure 17 This illustration shows a flowchart of the medical robot management method provided in the first embodiment of this text. Figure 17 As shown, in this embodiment, the medical robot management method includes:

[0194] Step S310: Send a backup data request instruction to the robot industrial control computer 30 through the local management server 20, so that the robot industrial control computer 30 sends the corresponding robot data to the local management server 20.

[0195] Step S320: Receive the data upload request instruction sent by the local management server 20;

[0196] Step S330: Receive robot data sent by the local management server 20 and store the robot data accordingly.

[0197] Therefore, the medical robot management method provided in this embodiment can perform off-site backup of robot data within a local area network system without the need for a USB flash drive, through the local management server 20. This not only automatically frees up local disk space on the robot industrial control computer 30, but also effectively prevents data leakage during transmission, improving the security of robot data transmission. Furthermore, since the local management server 20 and the robot industrial control computer 30 communicate via a local area network, data transmission between them can be supported even in surgical environments without a network (no external network).

[0198] In one exemplary embodiment, the medical robot management method further includes, prior to receiving the upload data request instruction sent by the local management server 20:

[0199] Authentication is performed between the local management server 20 and the local management server 20.

[0200] Specifically, the authentication process with the local management server 20 includes:

[0201] Send a CA certificate to the local management server 20 so that the local management server 20 can decrypt the CA certificate to obtain the public key, thereby enabling the local management server 20 to encrypt the generated key based on the public key to obtain the encryption key;

[0202] Receive the encryption key sent by the local management server 20;

[0203] The encryption key is decrypted using the corresponding private key to obtain the corresponding key, thereby completing the identity authentication with the local management server 20.

[0204] In one exemplary embodiment, the medical robot management method further includes:

[0205] Receive the software package synchronization request instruction sent by the local management server 20;

[0206] According to the software package synchronization request instruction, the corresponding software package is sent to the local management server 20 so that the local management server 20 can classify and manage the received software packages.

[0207] In one exemplary embodiment, the medical robot management method further includes:

[0208] Receive the detection model synchronization request instruction sent by the local management server 20;

[0209] According to the detection model synchronization request instruction, the corresponding detection model is sent to the local management server 20, so that the local management server 20 can detect the health status of the medical robot according to the detection model.

[0210] Example 5

[0211] This embodiment also provides an electronic device, please refer to... Figure 18 The diagram illustrates the block structure of the electronic device provided in the first embodiment of this invention. Figure 18 As shown, the electronic device includes a processor 41 and a memory 43. The memory 43 stores a computer program, which, when executed by the processor 41, implements the medical robot management method described above. Since the electronic device provided in this embodiment belongs to the same inventive concept as the medical robot management system described above, it possesses all the advantages of the medical robot management system described above. Therefore, the beneficial effects of the electronic device provided in this embodiment will not be elaborated further here. It should be noted that, as those skilled in the art will understand, when the electronic device provided in this embodiment can implement the medical robot management method provided in Embodiment 2, it can be used as a robot industrial control computer 30; when the electronic device provided in this embodiment can implement the medical robot management method provided in Embodiment 3, it can be used as a local management server 20; and when the electronic device provided in this embodiment can implement the medical robot management method provided in Embodiment 4, it can be used as a data server 10.

[0212] like Figure 18As shown, the electronic device also includes a communication interface 42 and a communication bus 44, wherein the processor 41, the communication interface 42, and the memory 43 communicate with each other through the communication bus 44. The communication bus 44 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus 44 can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not indicate that there is only one bus or one type of bus. The communication interface 42 is used for communication between the aforementioned electronic device and other devices.

[0213] In this embodiment, the processor 41 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor. The processor 41 is the control center of the electronic device, connecting various parts of the entire electronic device through various interfaces and lines.

[0214] The memory 43 can be used to store the computer program. The processor 41 implements various functions of the electronic device by running or executing the computer program stored in the memory 43 and calling the data stored in the memory 43.

[0215] The memory 43 may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0216] Example 6

[0217] This embodiment provides a readable storage medium storing a computer program. When executed by a processor, the computer program can implement the medical robot management method described above. Since the readable storage medium provided in this embodiment belongs to the same inventive concept as the medical robot management system described above, it possesses all the advantages of the medical robot management system described above. Therefore, the beneficial effects of the readable storage medium provided in this embodiment will not be elaborated further here. It should be noted that, as those skilled in the art will understand, when the readable storage medium provided in this embodiment can implement the medical robot management method provided in Embodiment 2, the readable storage medium provided in this embodiment can be configured on the robot industrial control computer 30; when the readable storage medium provided in this embodiment can implement the medical robot management method provided in Embodiment 3, the readable storage medium provided in this embodiment can be configured on the local management server 20; when the readable storage medium provided in this embodiment can implement the medical robot management method provided in Embodiment 4, the readable storage medium provided in this embodiment can be configured on the data server 10.

[0218] The readable storage medium provided in this embodiment can be any combination of one or more computer-readable media. The readable medium can be a computer-readable signal medium or a computer-readable storage medium. Computer-readable storage media can be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable computer hard disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in combination with an instruction execution system, apparatus, or device.

[0219] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of transmitting, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wireline, optical fiber, RF, etc., or any suitable combination thereof.

[0220] In summary, compared with the prior art, the medical robot management system, method, electronic device, and storage medium provided by the present invention have the following advantages:

[0221] The medical robot management system provided by this invention includes a data server, a local management server, and a robot industrial control computer. The data server and the local management server are connected via the Internet, and the local management server and the robot industrial control computer are connected via a local area network (LAN). The robot industrial control computer is configured to collect robot data from the medical robot and send corresponding robot data to the local management server according to a backup data request instruction sent by the local management server. The local management server is configured to back up the received robot data. The data server is configured to receive the robot data sent by the local management server according to an upload data request instruction sent by the local management server and store it accordingly. Therefore, the medical robot management system provided by this invention, through the local management server, can perform off-site backup of robot data within the local area network system without the use of a USB flash drive. This not only automatically frees up local disk space on the robot industrial control computer but also effectively prevents data leakage during transmission, improving the security of robot data transmission. Furthermore, since the local management server and the robot industrial control computer communicate via a local area network, data transmission between the local management server and the robot industrial control computer can be supported even in surgical environments without a network (no external network).

[0222] Since the medical robot management method, electronic device and storage medium provided by this invention belong to the same inventive concept as the medical robot management system provided by this invention, the medical robot management method, electronic device and storage medium provided by this invention have all the advantages of the medical robot management system provided by this invention. Therefore, the beneficial effects of the medical robot management method, electronic device and storage medium provided by this invention will not be described in detail here.

[0223] It should be noted that computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. These programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0224] It should be noted that the apparatus and methods disclosed in the embodiments herein can also be implemented in other ways. The apparatus embodiments described above are merely illustrative; for example, the flowcharts and block diagrams in the accompanying drawings show the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments herein. In this regard, each block in a flowchart or block diagram may represent a module, program, or part of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system to perform the specified function or action, or can be implemented using a combination of dedicated hardware and computer instructions.

[0225] In addition, the functional modules in the various embodiments of this article can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0226] The above description is merely a description of preferred embodiments of the present invention and is not intended to limit the scope of the invention in any way. Any changes or modifications made by those skilled in the art based on the above disclosure are within the protection scope of the present invention. Obviously, those skilled in the art can make various modifications and variations to the present invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the present invention and its equivalents, the present invention also intends to include these modifications and variations.

Claims

1. A medical robot management system characterized by comprising: It includes a data server, a local management server, and a robot industrial control computer. The data server and the local management server communicate with each other via the Internet, and the local management server and the robot industrial control computer communicate with each other via a local area network. The robot industrial control computer is configured to collect robot data from the medical robot and send the corresponding robot data to the local management server according to the backup data request instruction sent by the local management server; The local management server is configured to back up the received robot data; The data server is configured to receive robot data sent by the local management server according to the upload data request instruction sent by the local management server and store it accordingly; The data server is also configured to manage the detection models of the medical robot, and send the corresponding detection models to the local management server according to the detection model synchronization request instruction sent by the local management server; The local management server is also configured to record maintenance data for the medical robot and to detect the health status of the medical robot through the following process: Send a health check request command to the robot's industrial control computer; Receive the ID of the medical robot sent by the robot's industrial control computer; Based on the ID of the medical robot, the detection model and maintenance data corresponding to the medical robot are retrieved locally; Send a self-test data request command to the robot industrial control computer, and receive the self-test data of the medical robot sent by the robot industrial control computer; Based on the self-test data, detection model, and maintenance data of the medical robot, the health status detection results of the medical robot are obtained.

2. The medical robot management system according to claim 1, characterized by, The robot's industrial control computer is configured to send robot data to the local management server via the following steps: Find the timestamp information of the latest locally collected robot data; Based on the timestamp information of the latest locally collected robot data and the timestamp information of the last time robot data was successfully sent to the local management server, it is determined whether there is updated robot data locally; If so, the updated robot data is sent to the local management server, and the corresponding timestamp is recorded after successful transmission.

3. The medical robot management system according to claim 1, characterized by, The robot's industrial control computer is also configured to authenticate the local management server during communication with the local management server through the following process: Receive the public key certificate sent by the local management server; The validity of the public key certificate is verified using a local CA certificate; If the verification is successful, the encryption key sent by the local management server will be received. The encryption key is decrypted using the public key in the public key certificate to obtain the corresponding key, thereby completing the authentication of the local management server.

4. The medical robot management system according to claim 1, characterized by, The data server is also configured to classify and manage the software packages of the medical robot, and to send the corresponding software packages to the local management server according to the software package synchronization request instruction sent by the local management server; The local management server is also configured to classify and manage the received software packages; The robot's industrial control computer is also configured to receive and install the software package sent by the local management server; The data server and the local management server are configured to classify and manage the software packages using a multi-level file directory structure.

5. The medical robot management system according to claim 1, characterized by, The local management server is also configured to send the maintenance data to the data server for storage; The data server is also configured to send corresponding maintenance data to the local management server according to the maintenance data synchronization request instruction sent by the local management server.

6. The medical robot management system according to claim 1, characterized by, The detection model includes any one or more of the following: usage limit information for basic components, operating distance limit information, usage limit information for device consumables, resource usage limit information, and operating temperature limit information.

7. The medical robot management system according to claim 1, characterized by, The local management server is also configured to display the health status detection results of the medical robot in a list format.

8. A medical robot management method characterized by comprising: The robot industrial control computer applied in the medical robot management system according to any one of claims 1 to 7, the medical robot management method comprising: Collect robot data from medical robots; According to the backup data request instruction sent by the local management server, the corresponding robot data is sent to the local management server; The local management server sends an upload data request command to the data server and sends the corresponding robot data to the data server for storage. The method further includes: Receive a health check request command sent by the local management server; The ID of the medical robot is sent to the local management server, enabling the local management server to locate the detection model and maintenance data corresponding to the medical robot based on the ID. according to; According to the self-test data request instruction sent by the local management server, the corresponding self-test data is sent to the local management server so that the local management server can obtain the health status detection result of the medical robot based on the self-test data, detection model and maintenance data of the medical robot.

9. A medical robot management method characterized by comprising: The local management server applied in the medical robot management system according to any one of claims 1 to 7, the medical robot management method comprising: Send a backup data request command to the robot's industrial control computer; Receive robot data sent by the robot's industrial control computer; Send an upload data request instruction to the data server, and send the corresponding robot data to the data server for storage according to the upload data request instruction; The method further includes: Send a health check request command to the robot's industrial control computer; Receive the ID of the medical robot sent by the robot's industrial control computer; Based on the ID of the medical robot, the detection model and maintenance data corresponding to the medical robot are retrieved locally; Send a self-test data request command to the robot industrial control computer, and receive the self-test data of the medical robot sent by the robot industrial control computer; Based on the self-test data, detection model, and maintenance data of the medical robot, the health status detection results of the medical robot are obtained.

10. A medical robot management method characterized by comprising: The data server is applied in the medical robot management system according to any one of claims 1 to 7, and the medical robot management method includes: The local management server sends a backup data request command to the robot industrial control computer, so that the robot industrial control computer sends the corresponding robot data to the local management server. Receive the data upload request instruction sent by the local management server; Receive robot data sent by the local management server and store the robot data accordingly; The method further includes: Receive the detection model synchronization request instruction sent by the local management server; According to the detection model synchronization request instruction, the corresponding detection model is sent to the local management server so that the local management server can detect the health status of the medical robot according to the detection model.

11. An electronic device, comprising: It includes a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, it implements the medical robot management method according to any one of claims 8 to 10.

12. A readable storage medium, characterized by, The readable storage medium stores a computer program, which, when executed by a processor, implements the medical robot management method according to any one of claims 8 to 10.

Images