Telesurgery — robotic surgery performed at a distance, with the surgeon at a console separate from the patient — imposes strict requirements on the communication link connecting them. 5G networks address these requirements through low-latency radio transmission, high throughput, and network slicing for defined quality-of-service levels. China has been among the most active environments for clinical telesurgery demonstrations using 5G.
What Telesurgery Requires from a Network
In local robotic surgery, the master console and slave robot are in the same room connected by a cable. End-to-end latency is under 1 millisecond and is imperceptible. Moving the surgeon to a remote location introduces a communication link whose performance determines whether surgery remains safe and controllable.
The three critical network parameters for telesurgery are:
Latency
Latency is the time for a data packet to travel from source to destination. In telesurgery, latency affects two paths:
Control path: Commands from the surgeon’s master console travel to the slave robot at the patient site. Every millisecond of latency means the slave robot executes a command that was issued a millisecond ago — the system is operating on slightly stale information.
Feedback path: Camera video, instrument position data, and any force feedback travel from the patient site back to the surgeon’s console.
Round-trip latency — the total loop from master input to slave response visible on screen — determines how well the surgeon can maintain control. Research on teleoperation control theory indicates that round-trip latencies above approximately 150–200 ms cause noticeable degradation in fine motor task performance, and latencies above 300 ms make stable haptic feedback impossible without specialized control algorithms.
5G’s target latency for ultra-reliable low-latency communications (URLLC) is under 1 ms at the radio access network level. Network-to-network latency over longer distances adds propagation delay, so end-to-end latency for a telesurgery link spanning hundreds of kilometers is dominated by physics (speed of light in fiber) rather than radio technology.
Bandwidth
Telesurgery requires real-time high-definition video from the surgical endoscope — typically 1080p or 4K at 30–60 frames per second, which requires several tens of megabits per second per stream. Stereo (3D) video doubles this. Multiple camera angles further increase requirements.
Control and feedback data (position, force, status) require far less bandwidth than video — typically kilobits per second — but must be transmitted with low latency.
5G New Radio supports peak throughput in the gigabits-per-second range under ideal conditions, more than sufficient for surgical video. The practical bandwidth available to a specific telesurgery link depends on spectrum allocated, cell load, and the deployed 5G configuration.
Reliability
A telesurgery system must detect communication interruption within milliseconds and trigger a safe state — instruments hold position or retract. The communication link must be reliable enough that interruptions are rare, and the system must fail safely when they occur.
According to 3GPP technical specifications for URLLC (ultra-reliable low-latency communications), 5G targets 99.9999% availability for safety-critical applications. Achieving this in practice requires network engineering — redundant paths, dedicated network slices, edge computing to minimize hops — beyond what consumer 5G connections provide.
Network Slicing for Telesurgery
A key 5G architectural capability is network slicing: the ability to partition the radio and core network into logically separate virtual networks, each with its own quality-of-service parameters. A telesurgery slice can be configured with defined latency and bandwidth budgets, isolated from consumer traffic on the same physical infrastructure.
Without network slicing, a telesurgery control link would compete for bandwidth and latency with all other traffic on the same 5G cell — unacceptable for a safety-critical application. With dedicated slicing, the telesurgery traffic receives priority and guaranteed resources.
Deploying network slices for clinical telesurgery requires coordination between the hospital network, the 5G carrier’s core network, and in inter-city scenarios, transit network operators. This is currently a custom integration rather than a standardized service, which contributes to why telesurgery over 5G remains in demonstration and pilot phases rather than routine clinical practice.
Chinese Telesurgery Context
China’s 5G infrastructure rollout has been among the largest in scale and pace, which has made it an active environment for 5G-enabled medical robotics demonstrations. MicroPort MedBot’s Toumai Tele-Robotic System is one platform designed specifically for telesurgical applications. Tinavi has demonstrated orthopedic navigation over remote links.
Chinese regulatory guidance on telesurgery is still developing. The NMPA has indicated that telesurgical capability in a robotic system requires specific clinical evidence and software validation addressing communication-dependent safety risks — latency monitoring, communication quality thresholds that trigger safe-stop, and logging requirements. The KangDuo SR2000 from Sagebot has incorporated telesurgery functionality in its design specification.
Edge Computing and Latency Reduction
One architectural technique for reducing effective latency is mobile edge computing (MEC): placing processing resources at the edge of the 5G network, close to the radio access point, rather than in a distant data center. By running video compression and robot control computations at an edge server near the patient site, the data that must traverse the long-haul network is minimized.
For a telesurgery link where surgeon and patient are 500 km apart, the speed-of-light propagation delay through fiber adds approximately 5 ms per 1,000 km (one-way) — roughly 10 ms round-trip per 1,000 km of separation. Edge computing cannot reduce this physics-based latency floor, but it reduces the software processing and routing latency that adds on top.
Regulatory and Safety Requirements
Regulators have not yet established globally harmonized requirements for telesurgery communication specifications. Published research and draft guidance from several regulators identify common requirements:
- Latency monitoring: the system must measure and display real-time latency to the surgeon and alert when latency exceeds a defined threshold.
- Communication quality thresholds: defined limits above which the system automatically enters a safe state regardless of surgeon action.
- Safe-stop behavior: documented and validated behavior when communication is interrupted — instruments must not move unpredictably.
- Logging: complete logs of communication quality during telesurgical procedures for post-market surveillance.
The regulatory question of who bears liability for adverse events in telesurgery — surgeon, hospital, robot manufacturer, or network operator — has not been definitively resolved in any jurisdiction.
Frequently Asked Questions
What latency is acceptable for telesurgery?
Research consensus generally places the practical upper bound for stable teleoperation at approximately 150–200 ms round-trip for fine manipulation tasks. For telesurgery with haptic feedback, the requirement is stricter — under 100 ms round trip. For camera-only feedback without haptics, somewhat higher latencies may be tolerable for coarser movements.
Can telesurgery be done over 4G LTE?
In principle, yes — 4G latency can fall below 20 ms in low-load conditions. In practice, 4G networks do not support network slicing for defined quality-of-service levels, and real-world latency variability on 4G is too high for reliable telesurgery. Demonstrations over 4G have been conducted, but 5G URLLC with dedicated slicing provides substantially better reliability assurance.
Is telesurgery currently used in routine clinical practice?
As of 2026, telesurgery remains in pilot and demonstration phases rather than routine clinical practice. Technical demonstrations — some covering hundreds of kilometers — have been published, but widespread clinical deployment requires resolved regulatory frameworks, commercial network slicing services, and broader clinical evidence.
How does distance affect telesurgery feasibility?
Speed of light propagation sets a physical lower bound on latency: approximately 5 ms per 1,000 km one-way for fiber optic transmission, or about 10 ms round-trip per 1,000 km. Transcontinental telesurgery (e.g., surgeon in Beijing, patient in a rural county 2,000 km away) would have a minimum ~20 ms round-trip propagation-based latency, which is within acceptable ranges. However, routing overhead and processing add to this. Global telesurgery across intercontinental distances adds enough latency to require specialized control algorithms.
What are the most important safety requirements for a telesurgical system?
Automatic safe-stop on communication loss, real-time latency monitoring with surgeon alerts, documented and validated behavior at degraded communication quality levels, and complete logging for post-market surveillance are the key requirements appearing in published regulatory guidance and academic safety analysis.