Remote medical network control system and method and electronic equipment

Abstract

The invention discloses a remote medical network control system and method and electronic equipment. The system comprises a first device, a first switch, N pairs of routers, a second switch, a second device and a cloud server, the first equipment is connected with the first switch, and the second equipment is connected with the second switch; the first switch and the second switch establish N first communication links through the N pairs of routers; the cloud server establishes a second communication link with each router; the N first communication links are all online, M first communication links serve as target communication links to be in a data transmission state, and the other N-M first communication links serve as hot backups of the target communication links; according to the embodiment of the invention, the cloud server can obtain the state data of each router through the second communication link independent of the first communication link, so that the state monitoring of each first communication link is realized, and the first equipment can perform link switching when the target communication link is abnormal. Through the scheme of the application, the transmission reliability of the service data can be improved while the transmission privacy of the service data in a telemedicine application scene is guaranteed.

Description

Technical Field

[0001] This application belongs to the field of communication technology, and in particular relates to a remote medical network control system, a remote medical network control method, and an electronic device. Background Technology

[0002] Currently, telemedicine solutions typically use a single network communication link, or multiple network communication links with cold backup and manual switching. A single network communication link lacks network backup capabilities; when a network failure occurs, the remote surgical process is passively interrupted. Multi-link cold backup solutions require a dedicated network engineer to be present during surgery, resulting in wasted manpower, long switching times, and a higher probability of errors, thus reducing the reliability of remote surgery. Therefore, telemedicine still faces the challenge of network fluctuations affecting surgical accuracy. Summary of the Invention

[0003] This application provides a remote medical network control system, a remote medical network control method, and an electronic device, which can improve the reliability of business data transmission while ensuring the privacy of business data transmission in remote medical application scenarios.

[0004] In a first aspect, this application provides a remote medical network control system, comprising: a first device, a first switch, N pairs of routers, a second switch, a second device, and a cloud server; the first device is connected to the first switch, and the second device is connected to the second switch; the first switch and the second switch establish N first communication links via the N pairs of routers, each first communication link corresponding to a pair of routers; the cloud server establishes a second communication link with each router.

[0005] All N first communication links are online, of which M first communication links are in data transmission state as target communication links, and the remaining NM first communication links are hot backups of the target communication links; N is a positive integer greater than 1, and M is a positive integer greater than 0 and less than N;

[0006] The first device is used to transmit service data with the second device through the first switch, the second switch and the target communication link;

[0007] The cloud server is used to obtain the status data of each router through each second communication link, and to transmit data back to the first device based on the status data;

[0008] The first device is used to switch the target communication link when the target communication link is determined to be abnormal based on the content of the data feedback.

[0009] In one implementation, when the first device switches the target communication link after determining that the target communication link is abnormal based on the content of the data feedback, it is specifically used for:

[0010] Analyze the data returned to determine whether the target communication link is abnormal, and the type of abnormality when the target communication link is abnormal;

[0011] In the event of an anomaly in the target communication link, the target communication link is switched according to the link switching strategy corresponding to the anomaly type.

[0012] In one implementation, when the first device analyzes the content of the data transmission to determine whether the target communication link is abnormal and the type of abnormality when the target communication link is abnormal, it specifically performs the following:

[0013] Determine whether the data backhaul content for the target communication link is empty within a preset time period;

[0014] If the data returned to the target communication link is empty within a preset time period, the target communication link is determined to be abnormal, and the abnormality type is device abnormality.

[0015] In one implementation, after determining whether the data backhaul content for the target communication link is empty within a preset time period, the first device is further specifically used for:

[0016] If the data returned to the target communication link is not empty within a preset time period, then all data returned content will be compared with the preset abnormal threshold conditions.

[0017] If all data returned meets the anomaly threshold condition, the target communication link is determined to be abnormal, and the anomaly type is link anomaly.

[0018] In one implementation, when the first device switches the target communication link according to the link switching policy corresponding to the exception type, it is specifically used for:

[0019] In the event of an anomaly type of device anomaly, a first port switching command is sent to the first switch. The first port switching command is used to control the first switch to switch the currently enabled network ports based on a preset port sequence until the target communication link is successfully switched.

[0020] Correspondingly, the cloud server is also used to send a device anomaly alert message to the second device in the event that the data transmission to the first device fails.

[0021] Accordingly, the second device is also used to send a second port switching command to the second switch after receiving a device abnormality alert message. The second port switching command is used to control the second switch to switch the currently enabled network ports based on a preset port sequence until the target communication link is successfully switched.

[0022] In one implementation, when the first device switches the target communication link according to the link switching policy corresponding to the exception type, it is specifically used for:

[0023] In the case of an anomaly type of link anomaly, the desired communication link is determined from NM first communication links;

[0024] Send a third port switching command to the first switch. The third port switching command is used to control the first switch to close the network port corresponding to the target communication link and enable the network port corresponding to the desired communication link, so that the desired communication link becomes the new target communication link.

[0025] Send a link switching command to the second device via the cloud server;

[0026] Accordingly, the second device is also used to send a fourth port switching instruction to the second switch after receiving the link switching instruction. The fourth port switching instruction is used to control the second switch to close the network port corresponding to the target communication link and enable the network port corresponding to the desired communication link, so that the desired communication link becomes the new target communication link.

[0027] In one implementation, when the cloud server transmits data back to the first device based on status data, it specifically performs the following functions:

[0028] The status data is periodically transmitted back to the first device.

[0029] In one implementation, when the cloud server transmits data back to the first device based on status data, it specifically performs the following functions:

[0030] The system analyzes the status data obtained within a preset time period to determine whether network fluctuations occur in the target communication link.

[0031] In the event of network fluctuations in the target communication link, the analysis results and the status data obtained within a preset period are transmitted back to the first device.

[0032] In one implementation, among the N first communication links, at least two first communication links are established using the same communication method.

[0033] In one implementation, the status data includes one or more of the following: public IP address, signal strength, routing status, packet loss rate, and latency.

[0034] Secondly, this application provides a remote medical network control method, which is applied to a first device in a remote medical network control system. The remote medical network control system further includes: a first switch, N pairs of routers, a second switch, a second device, and a cloud server. The first device is connected to the first switch, and the second device is connected to the second switch. The first switch and the second switch establish N first communication links via the N pairs of routers, each first communication link corresponding to a pair of routers. The cloud server establishes second communication links with each router. All N first communication links are online, of which M first communication links are in data transmission state as target communication links, and the remaining NM first communication links serve as hot backups of the target communication links. N is a positive integer greater than 1, and M is a positive integer greater than 0 and less than N. The remote medical network control method includes:

[0035] The service data is transmitted with the second device via the first switch, the second switch and the target communication link.

[0036] The content of the data returned by the cloud server is received, wherein the content of the data returned is determined by the status data of each router obtained by the cloud server through each of the second communication links.

[0037] When the target communication link is determined to be abnormal based on the data feedback, the target communication link will be switched.

[0038] Thirdly, this application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method described in the second aspect above.

[0039] The advantages of this application compared to existing technologies are as follows: In the remote medical network control system proposed in this application, since all N first communication links are online, and non-target communication links serve as hot backups rather than cold backups of the target communication links, manual maintenance is unnecessary when switching links, significantly optimizing link switching efficiency and convenience, thereby improving the reliability of business data transmission. Furthermore, in this remote medical network control system, the cloud server obtains the status data of each router through a second communication link independent of the first communication links, enabling status monitoring of each first communication link. This separates medical-related business data from monitoring-related status data, ensuring the privacy of business data transmission. In summary, the solution proposed in this application can improve the reliability of business data transmission while ensuring the privacy of business data transmission in remote medical application scenarios.

[0040] It is understood that the beneficial effects of the second and third aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a schematic diagram of the system architecture of the remote medical network control system provided in the embodiments of this application;

[0043] Figure 2 This is a communication example diagram of the remote medical network control system provided in the embodiments of this application;

[0044] Figure 3 This is another communication example diagram of the remote medical network control system provided in the embodiments of this application;

[0045] Figure 4 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0046] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

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

[0048] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0049] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0050] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0051] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0052] To illustrate the above-described technical solutions of this application, specific embodiments are described below.

[0053] This application proposes a remote medical network control system, which will be explained and described below. Please refer to... Figure 1 , Figure 1 The architecture of this remote medical network control system is shown below:

[0054] From the perspective of realizing telemedicine functions, the telemedicine network control system can be divided into three parts: the doctor side, the patient side, and the network side.

[0055] The doctor's side serves as the control terminal, responding to various doctor commands and performing corresponding controls. In practical applications, this doctor's side primarily possesses three functions: two-way audio and video communication, main operator control, and network switching. This embodiment focuses on the network switching function, specifically enabling network switching (e.g., switching to the optimal network) in case of network anomalies, ensuring the normal transmission of medical-related business data streams. The patient's side is the controlled terminal, responding to the doctor's commands and executing corresponding operations. The network side establishes a communication link between the doctor's and patient's sides to transmit medical-related business data and monitoring-related status data. This business data includes, but is not limited to, audio and video stream data and surgical control I / O data.

[0056] Specifically, the hardware configuration of the remote medical network control system may include: a first device deployed on the doctor's side, a second device deployed on the patient's side, and a first switch, N pairs of gateways, a second switch, and a cloud server deployed on the network side. The first device and the second device can interact with each other through the first switch, N pairs of gateways, and the second switch. In this embodiment, the first device may be a master station, including but not limited to various electronic devices with interactive interfaces; the gateway may be a router, such as an industrial router; the second device may be a slave station, including but not limited to various controllable medical devices, such as robotic arms, electrosurgical units, and computed tomography (CT) machines. The specific device types of the master station, gateway, and slave station are not limited here. For ease of understanding, the following description uses the first device as the master station and the second device as the slave station to illustrate the remote medical network control system proposed in this embodiment.

[0057] like Figure 1 As shown, the master station can provide a network interface to connect with the first switch; the slave station can provide a network interface to connect with the second switch; the first switch can establish N first communication links with the second switch through N pairs of routers, each first communication link corresponding to a pair of routers. For example, the first switch establishes the first first communication link with the second switch through router 11 and router 12, the first switch establishes the second first communication link with the second switch through router 21 and router 22, and so on, until the first switch establishes the Nth first communication link with the second switch through router N1 and router N2. This will not be elaborated here. In addition, the cloud server can establish second communication links with each router respectively.

[0058] Specifically, please refer to Figure 2 , Figure 2A communication example of a remote medical network control system is given. The master station, first switch, second switch, and slave stations are private network devices, configured only with private IP addresses. Each router typically has a Local Area Network (LAN) interface and a Wide Area Network (WAN) interface; the LAN interface connects to the private network, so its LAN address can serve as the gateway address for both the master and slave stations; the WAN interface connects to the public network, allowing access to networks that provide fixed public IP addresses. Each router can establish a Virtual Private Network (VPN) tunnel with its paired router based on a public IP address. For example, Figure 2 Wired router 1 and wired router 2 established VPN tunnels, as did 5G router 1 and 5G router 2. This not only ensured network security to a certain extent but also facilitated private network address traversal, enabling smooth data interaction between the master and slave stations. The cloud server has a fixed public IP address and can maintain Transmission Control Protocol (TCP) connections with each router; it can also establish bidirectional connections with the master and slave stations via static routing or VPN.

[0059] In this embodiment, all N first communication links are online, meaning they are all in a network-connected state. However, only M of these first communication links are in data transmission mode as target communication links; that is, only these M first communication links actually transmit service data. The remaining NM first communication links serve as hot backups for the target communication links and do not transmit service data simultaneously with them. Here, N is a positive integer greater than 1, and M is a positive integer greater than 0 and less than N. The master station can thus transmit service data with the slave station through the first switch, the second switch, and the target communication links. Since the hardware devices in the remote medical network control system proposed in this embodiment are not mobile devices but rather devices connected to a power source, even if hot backup results in significant energy consumption, it will not affect the normal operation of the remote medical network control system.

[0060] In practical applications, since all routers on one side share the same gateway address, adding routers in pairs requires no modification to the configurations of the switches, master station, and slave station. This not only saves manpower costs but also eliminates the risks associated with configuration changes. Furthermore, based on these characteristics, there's no need to distinguish router addresses; the target communication link can be maintained directly by managing the status of the switch's network ports. This allows for easy switching of the target communication link. Specifically, the network port of the switch corresponding to the target communication link is enabled (set to an active (up) state); the network ports of the switches corresponding to the remaining first communication link (i.e., the non-target communication link within the first communication link) are disabled (set to an inactive (down) state. Let's continue with... Figure 2 For example, assuming only the first communication links corresponding to wired router 1 and wired router 2 are selected as the target communication links, then: network ports Port1 of the first switch and Port2 of the second switch are enabled, i.e., set to active state; network ports Port2 of the first switch and Port2 of the second switch are closed, i.e., set to inactive state. It is important to note that whether the network ports of the switches are enabled or not does not affect the online status of the corresponding communication links. That is, even if network ports Port2 of the first switch and Port2 of the second switch are closed, the first communication links corresponding to 5G router 1 and 5G router 2 will still remain online.

[0061] It is understood that in the remote medical network control system provided in this application embodiment, the transmission of business data between routers does not involve any other devices, and there is no relay of business data. For example, when router 11 transmits business data to router 12, it does not relay data through a cloud server (or any other server). This effectively prevents the leakage of business data and protects the privacy of business data during transmission. In addition, for each router, its transmission peer is fixed and its transmission path cannot be changed arbitrarily. For example, router 11 can only interact with router 12 for business data, and cannot interact with router 22 or router 22 for business data. All of the above significantly improves the privacy of business data transmission and is more suitable for remote medical scenarios.

[0062] In this embodiment, the cloud server can obtain the status data of each router through each second communication link. In some examples, the status data includes, but is not limited to, public IP address, signal strength, routing status, packet loss rate, and latency. It can be understood that since each first communication link is established through a corresponding pair of routers, the status of the router actually represents the status of the first communication link corresponding to that router. Based on this, the router status data obtained by the cloud server is essentially equivalent to the status data of the first communication link corresponding to that router. In this way, the cloud server can monitor the first communication links through the second communication links. It is particularly important to note that no business data is transmitted through the second communication links; that is, the second communication links completely isolate business data. After obtaining the status data of each router, the cloud server can send data back to the main station based on this status data. In some examples, the status data can be sent back to the main station directly, or it can be analyzed before sending the analysis results and status data back to the main station. This embodiment does not limit this approach. In this way, the master station can determine whether the currently selected target communication link is abnormal based on the content of the data return, and switch the link when the target communication link is abnormal, that is, select another first communication link as the target communication link.

[0063] It is understood that in the remote medical network control system provided in this application embodiment, all established first communication links are online, and therefore non-target communication links can serve as hot backups for target communication links. Compared with cold backup, hot backup has a higher degree of link readiness, faster link recovery speed, and does not require manual configuration of the switch by the user. This effectively ensures the reliability of business data transmission and is more suitable for remote medical scenarios.

[0064] In some embodiments, to enable the master station to promptly obtain information on the status of each first communication link, especially the target communication link, the cloud server may employ a periodic backhaul strategy. Specifically, this involves periodically backhauling status data to the master station. It is understood that when using this backhaul strategy, the cloud server may only backhaul the status data obtained within the current period, excluding status data obtained in previous periods, to avoid duplicate data backhauls. The master station may send feedback to the cloud server after receiving the backhauled data; details are omitted here. Considering that an excessively long period may prevent timely detection of anomalies, while an excessively short period may increase network resource consumption and hardware pressure, the period can be appropriately set based on practical experience. For example, it may be set to 100 milliseconds or 1 second; no specific limitation is made here.

[0065] In some embodiments, since data backhaul still involves occupying the first communication link, the cloud server may also adopt a fluctuation-triggered backhaul strategy to conserve network resources as much as possible. Specifically, it analyzes the status data obtained within a preset period to determine whether network fluctuations have occurred on the target communication link. If network fluctuations have occurred on the target communication link, the analysis results and the status data obtained within the preset period are backhauled to the main station. It is understood that the cloud server itself has certain data processing and analysis capabilities. It can first perform simple data analysis on the status data of the routers on the target communication link obtained within the current period, such as analyzing whether the latency is too high, the packet loss rate is too high, and / or the signal strength is too low. If the analysis results indicate that the latency, packet loss rate, and / or signal strength of the routers on the target communication link are too high, it can be preliminarily determined that network fluctuations have occurred on the target communication link within the current period, and this network fluctuation may lead to an anomaly. Only then is it necessary for the cloud server to perform data backhaul, and it can backhaul the analysis results and all status data obtained within the current period to the main station. The main station can send feedback to the cloud server after receiving the backhauled data; this will not be elaborated here.

[0066] It is understandable that the cloud server can transmit back via the original link path or by finding the shortest link path based on the original link path. For example, if the cloud server obtains the status data of router 12 through the second communication link with router 12, then its original link path is: cloud server - router 12 - router 11 - first switch - master station; and since router 12 and router 11 are on the same first communication link, the shortest link path that can be optimized is: cloud server - router 11 - first switch - master station.

[0067] In some embodiments, to adapt to different network anomaly situations, the master station can switch the target communication link through the following operations:

[0068] Analyze the data returned to determine if the target communication link is abnormal and what type of abnormality it is. If the target communication link is abnormal, switch the target communication link according to the link switching strategy corresponding to the abnormality type.

[0069] The main station itself also possesses certain data processing and analysis capabilities. As described earlier, the cloud server transmits data back to the main station based on the status data obtained from monitoring. Therefore, the main station can analyze the transmitted data to determine whether the current target communication link is abnormal. This analysis process can also output the type of abnormality corresponding to the target communication link, i.e., the cause of the abnormality. Generally, there are two types of abnormality causes: device abnormality and link abnormality. In the case of device abnormality, data transmission on the target communication link is usually blocked; in the case of link abnormality, the transmission quality of data transmission on the target communication link usually decreases. Therefore, since different types of abnormalities will bring different degrees of adverse consequences to data transmission, this application embodiment sets different link switching strategies for different abnormality types to help improve the success rate of target communication link switching.

[0070] In some embodiments, based on the characteristics of device malfunction, the master station can determine whether the link is malfunctioning and the type of malfunction in the following way: determine whether the data back transmission content for the target communication link is empty within a preset time period; if the data back transmission content for the target communication link is empty within the preset time period, then determine that the target communication link is malfunctioning, and the malfunction type is device malfunction.

[0071] When a cloud server employs a periodic data backhaul strategy, meaning it periodically backhauls data, the master station should theoretically be able to periodically receive the backhauled data if all communication devices in the network (such as routers and switches) are functioning correctly. Considering the possibility of packet loss or delay, the master station can set a preset time period longer than the data backhaul cycle time; for example, the preset time period should be an integer multiple of the data backhaul cycle time. The master station can check whether the received data backhaul content for the target communication link is empty within the preset time period. As described earlier, since data backhaul is usually achieved through the original link path or the shortest link path obtained based on the original link path, if the communication device (or the network port of that communication device) associated with the target communication link fails, the data backhaul content received by the master station will not contain content related to the target communication link (i.e., the pair of routers corresponding to that target communication link), meaning it cannot receive the data backhaul content for the target communication link.

[0072] In some embodiments, based on the characteristics of link anomalies, the master station can determine whether a link is abnormal and the type of anomaly in the following way: if the data back transmission content for the target communication link is not empty within a preset time period, then compare all the data back transmission content with the preset anomaly threshold condition; if all the data back transmission content meets the anomaly threshold condition, then determine that the target communication link is abnormal, and the anomaly type is link anomaly.

[0073] As described earlier, when a cloud server employs a periodic data backhaul strategy, meaning it periodically backhauls data, if all communication devices in the network (such as routers and switches) are functioning correctly, the master station should theoretically be able to periodically receive the backhauled data. Therefore, if the data backhauled content for the target communication link is not empty within a preset time period, the master station can confirm that there is no risk of device malfunction on the current target communication link. At this point, the master station can perform further analysis, specifically comparing all the data backhauled this time with a preset anomaly threshold condition. This anomaly threshold condition is used to determine whether the current target communication link is of poor quality and whether there are other first communication links with significantly better quality than the current target communication link. It is understood that if the quality of the current target communication link is still at a relatively good level, and / or if the quality of other first communication links is close to that of the current target communication link, then there is no need to switch the target communication link. Only when the quality of the current target communication link is too poor, and the quality of other first communication links (i.e., non-target communication links in the first communication links) is significantly better than that of the current target communication link, is the content of the data return considered to meet the abnormal threshold condition. The master station can then determine that the target communication link is abnormal, and the abnormality type is link abnormality.

[0074] In some embodiments, to achieve target communication link switching in the event of device malfunction, the link switching strategy adopted by the master station may specifically be as follows: A first port switching command is sent to the first switch. This first port switching command controls the first switch to switch the currently enabled network ports according to a preset port sequence until the target communication link is successfully switched. Correspondingly, if the cloud server fails to receive feedback from the master station after initiating data backhaul for the target communication link, it can know that the data backhaul for the target communication link has failed, thereby analyzing and confirming that there is a device malfunction in the current target communication link, and can send a device malfunction alert message to the slave station. In response, the slave station can receive the device malfunction alert message and send a second port switching command to the second switch. This second port switching command controls the second switch to switch the currently enabled network ports according to a preset port sequence until the target communication link is successfully switched.

[0075] It is understandable that network ports of a switch are usually sequentially numbered, such as Port1, Port2, and so on up to PortN, which will not be elaborated here. Based on this, for the first and second switches, the preset port order can be either from smallest to largest or largest to smallest port number, until all network ports with established first communication connections have been traversed. After each switch of the currently active network port, the first and second switches can wait for a certain period and attempt to send service data through the newly active network port. If service data can be received through the newly active network port, it indicates that the target communication link has been successfully switched, and further switching of network ports is unnecessary; conversely, if service data cannot be received through the newly active network port, it indicates that the target communication link has not been successfully switched, and the switch needs to continue switching and enabling the next network port according to the preset port order, and so on, which will not be elaborated here.

[0076] Still with Figure 2For example, suppose the first switch and the second switch also establish a third first communication link through a pair of routers (X communication router 1 and X communication router 2), where X communication router 1 corresponds to network port Port3 of the first switch, and X communication router 2 corresponds to network port Port3 of the second switch. Initially, the target communication link is selected as a wired communication link, so both the first switch and the second switch have network port Port1 open and network ports Port2 and Port3 closed. After a period of time, network port Port1 of the first switch fails, causing business data transmission to be blocked, and the cloud server fails to transmit data back to the target communication link. When the master station determines that the current target communication link is abnormal and the abnormality type is device abnormality, it can send a first port switching command to the first switch. Similarly, the cloud server will also send a device abnormality alert message to the slave station due to the failure of data back transmission to the target communication link. The transmission path of this device abnormality alert message is: cloud server - a router (e.g., wired router 2) - second switch - slave station, thereby causing the slave station to send a second port switching command to the second switch. Therefore, in response to the first port switching command, the first switch can switch the enabled network port to Port2 (i.e., disable network port Port1 and enable network port Port2) and attempt to send service data; the second switch can respond to the second port switching command, switching the enabled network port to Port2 (i.e., disable network port Port1 and enable network port Port2) and attempt to send service data. If both network ports Port2 of the first and second switches are functioning correctly, bidirectional transmission of service data can be successfully achieved, thus enabling the master and slave stations to confirm that the current target communication link has been successfully switched, and the new target communication link is the first communication link corresponding to network ports Port2 of the first and second switches, i.e., the 5G communication link. Conversely, if bidirectional transmission of service data cannot be achieved through network port Port2 of the first switch and network port Port2 of the second switch, the master station and slave station can confirm that the current target communication link switching has failed. The second switch can switch the enabled network port to Port3 (that is, close network port Port2 and enable network port Port3). The second switch can also switch the enabled network port to Port3 (that is, close network port Port2 and enable network port Port3), and so on, until the target communication link switching is successful. This will not be elaborated here.

[0077] In some embodiments, to achieve target communication link switching in the event of a link failure, the link switching strategy adopted by the master station can be specifically as follows: First, determine the desired communication link from NM first communication links; then, send a third port switching command to the first switch, which controls the first switch to close the network port corresponding to the target communication link and enable the network port corresponding to the desired communication link, so that the desired communication link becomes the new target communication link; finally, send a link switching command to the slave station through the cloud server. Correspondingly, after receiving the link switching command, the slave station can send a fourth port switching command to the second switch, which controls the second switch to close the network port corresponding to the target communication link and enable the network port corresponding to the desired communication link, so that the desired communication link becomes the new target communication link.

[0078] It is understandable that the master station can respond to the link selection command input by the doctor and determine the desired communication link from NM first communication links; that is, the master station actually selects the desired communication link according to the doctor's wishes to ensure the necessity and reliability of link switching. Subsequently, the master station can send a third port switching command to the first switch, enabling the first switch to close the network port corresponding to the current target communication link and enable the network port corresponding to the desired communication link. Furthermore, the master station can also send a link switching command to the slave station through the cloud server and the pair of routers corresponding to the current target communication link, enabling the slave station to know the desired communication link selected by the user. In this way, the slave station can also send a fourth port switching command to the second switch, enabling the second switch to close the network port corresponding to the current target communication link and enable the network port corresponding to the desired communication link. The transmission path of the link switching command is: master station - first switch - router directly connected to the first switch in the current target communication link - cloud server - router directly connected to the second switch in the current target communication link - second switch - slave station.

[0079] Still with Figure 2For example, assuming the initial target communication link is a wired communication link, both the first and second switches will have network port Port1 open and network ports Port2 and Port3 closed. After a period of time, if the target communication link experiences a link anomaly, the user will input a link selection command to the master station, confirming that the 5G communication link is the desired communication link. The master station can then send a third port switching command to the first switch. Furthermore, the master station can also send a link switching command to the slave station via the following transmission path: Master station - First switch - Wired router 1 - Cloud server - Wired router 2 - Second switch - Slave station. The slave station can then respond to this link switching command by sending a fourth port switching command to the second switch. Thus, the first switch can respond to the second port switching command by closing network port Port1 and opening network port Port2; similarly, the second switch can respond to the second port switching command by closing network port Port1 and opening network port Port2. In this way, the 5G communication link becomes the new target communication link, and the master and slave stations can continue transmitting service data.

[0080] It should be noted that the data size of the link switching command is usually very small. Therefore, the transmission time of the link switching command is generally comparable to the inherent latency of the network, which is within an acceptable range and will not cause significant timeout problems.

[0081] In some embodiments, two or more first communication links may be established using the same communication method; this application does not limit the communication method. In some examples, for ease of deployment and cost considerations, two 5G first communication links can be established between the first switch and the second switch via two pairs of 5G routers using 5G communication. Both of these 5G first communication links are online, thereby achieving hot redundancy backup of 5G communication. Accordingly, the relevant equipment in the remote medical network control system can support multiple 5G hardware modules, which will not be elaborated here. Please refer to... Figure 3 , Figure 3 A communication example of a remote medical network control system with two 5G first communication links is given. Similarly, in other examples, for the sake of communication stability, two wired first communication links can also be established between the first and second switches via two pairs of wired routers, which will not be elaborated here.

[0082] As can be seen from the above, in the remote medical network control system proposed in this application, since all N first communication links are online, and the non-target communication links are hot backups rather than cold backups of the target communication links, manual maintenance is not required when switching links, significantly optimizing the efficiency and convenience of link switching, thereby improving the reliability of business data transmission. Furthermore, in this remote medical network control system, the cloud server obtains the status data of each router through a second communication link independent of the first communication links, realizing status monitoring of each first communication link. This allows medical-related business data to be separated from monitoring-related status data, ensuring the privacy of business data transmission. In summary, the solution of this application can improve the reliability of business data transmission while ensuring the privacy of business data transmission in remote medical application scenarios.

[0083] Corresponding to the first device in the remote medical network control system described above, this application also provides an electronic device. Please refer to... Figure 4 The electronic device 4 in this embodiment includes: a memory 401, one or more processors 402 ( Figure 4 (Only one is shown in the image) and a computer program stored in memory 401 and executable on the processor. Memory 401 stores software programs and units. Processor 402 executes various functional applications and data processing by running the software programs and units stored in memory 401 to obtain resources corresponding to various preset events. Specifically, processor 402 implements the various steps executable by the first device described above by running the aforementioned computer program stored in memory 401; these will not be elaborated upon here.

[0084] Those skilled in the art will recognize that the modules and method steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of external device software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0085] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A remote medical network control system, characterized in that, The remote medical network control system includes: a first device, a first switch, N pairs of routers, a second switch, a second device, and a cloud server; the first device is connected to the first switch, and the second device is connected to the second switch; the first switch and the second switch establish N first communication links through the N pairs of routers, and each first communication link corresponds to a pair of routers; the cloud server establishes a second communication link with each router. All N first communication links are online, of which M first communication links are in data transmission state as target communication links, and the remaining NM first communication links are hot backups of the target communication links; N is a positive integer greater than 1, and M is a positive integer greater than 0 and less than N; The first device is used to transmit service data with the second device through the first switch, the second switch and the target communication link; The cloud server is used to obtain the status data of each router through each of the second communication links, and to transmit data back to the first device based on the status data; The first device is used to switch the target communication link when it is determined that the target communication link is abnormal based on the content of the data feedback.

2. The remote medical network control system as described in claim 1, characterized in that, When the first device switches the target communication link after determining that the target communication link is abnormal based on the data feedback content, it is specifically used for: The data returned is analyzed to determine whether the target communication link is abnormal, and the type of abnormality when the target communication link is abnormal. In the event of an anomaly in the target communication link, the target communication link is switched according to the link switching strategy corresponding to the anomaly type.

3. The remote medical network control system as described in claim 2, characterized in that, When the first device analyzes the data transmission content to determine whether the target communication link is abnormal and the type of abnormality when the target communication link is abnormal, it is specifically used for: Determine whether the data backhaul content for the target communication link is empty within a preset time period; If the data transmission content of the target communication link is empty within a preset time period, the target communication link is determined to be abnormal, and the abnormality type is device abnormality.

4. The remote medical network control system as described in claim 3, characterized in that, After determining whether the data backhaul content for the target communication link is empty within a preset time period, the first device is further specifically used for: If the data back transmission content for the target communication link is not empty within a preset time period, then all the data back transmission content is compared with a preset abnormal threshold condition. If all the data returned satisfies the abnormal threshold condition, the target communication link is determined to be abnormal, and the abnormality type is link abnormality.

5. The remote medical network control system as described in claim 2, characterized in that, When the first device switches the target communication link according to the link switching policy corresponding to the anomaly type, it is specifically used for: In the case of device anomaly, a first port switching instruction is sent to the first switch. The first port switching instruction is used to control the first switch to switch the currently enabled network ports based on a preset port sequence until the target communication link is successfully switched. Accordingly, the cloud server is also configured to send a device anomaly alert message to the second device in the event that data transmission to the first device fails; Accordingly, the second device is also configured to send a second port switching instruction to the second switch after receiving the device abnormality alert message. The second port switching instruction is used to control the second switch to switch the currently enabled network ports based on a preset port sequence until the target communication link is successfully switched.

6. The remote medical network control system as described in claim 2, characterized in that, When the first device switches the target communication link according to the link switching policy corresponding to the anomaly type, it is specifically used for: In the case where the anomaly type is a link anomaly, the desired communication link is determined from NM first communication links; A third port switching command is sent to the first switch. The third port switching command is used to control the first switch to close the network port corresponding to the target communication link and enable the network port corresponding to the desired communication link, so that the desired communication link becomes the new target communication link. Send a link switching command to the second device through the cloud server; Accordingly, the second device is further configured to send a fourth port switching instruction to the second switch after receiving the link switching instruction. The fourth port switching instruction is used to control the second switch to close the network port corresponding to the target communication link and enable the network port corresponding to the desired communication link, so that the desired communication link becomes the new target communication link.

7. The remote medical network control system as described in claim 1, characterized in that, When the cloud server transmits data back to the first device based on the status data, it is specifically used for: The status data is periodically transmitted back to the first device.

8. The remote medical network control system as described in claim 1, characterized in that, When the cloud server transmits data back to the first device based on the status data, it is specifically used for: The system analyzes the status data obtained within a preset period to determine whether the target communication link experiences network fluctuations. In the event of network fluctuations in the target communication link, the analysis results and the status data obtained within the preset period are transmitted back to the first device.

9. The remote medical network control system as described in any one of claims 1 to 8, characterized in that, Of the N first communication links, at least two of them are established using the same communication method.

10. A remote medical network control method, characterized in that, The remote medical network control method is applied to a first device in a remote medical network control system. The remote medical network control system further includes: a first switch, N pairs of routers, a second switch, a second device, and a cloud server. The first device is connected to the first switch, and the second device is connected to the second switch. The first switch and the second switch establish N first communication links via the N pairs of routers, each first communication link corresponding to a pair of routers. The cloud server establishes second communication links with each router. All N first communication links are online, of which M first communication links are in data transmission state as target communication links, and the remaining NM first communication links serve as hot backups of the target communication links. N is a positive integer greater than 1, and M is a positive integer greater than 0 and less than N. The remote medical network control method includes: The service data is transmitted with the second device through the first switch, the second switch and the target communication link; The cloud server receives data back from the cloud server, wherein the data back is determined by the status data of each router obtained by the cloud server through each of the second communication links. When the target communication link is determined to be abnormal based on the data returned, the target communication link is switched.

11. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in claim 10.

Images