Application: Remote Robotic Endovascular Telesurgery
Description
image guided, haptic controls for remote tactile interaction, real-time high-definition video transmission
Devices
- On the patient side, this application may require several cameras (some of which could be wearable by the local staff).
Robotic-assisted surgical device.
On the remote expert/surgeon side, these applications may require a VR interface to provide an immersive experience.
Scope: fluoroscopy-heavy endovascular/neurovascular robotic interventions; surgeon operating remotely.
KPIs
| KPI | Value | Notes |
|---|---|---|
| DL E2E Packet Latency | High: < 100 ms | ≤ 100 ms (one way). Implies RTT ≤ 200 ms for robotic control; audiovisual pipeline may add codec delay but packet transport budget should meet this bound. |
| UL E2E Packet Latency | Moderate: 10 ms - 100 ms | Control acknowledgments and safety interlocks remain within RTT ≤ 200 ms. |
| E2E Packet Jitter | Sensitive (ms) | Target ≤ 5–10 ms. Very low jitter required to keep control loops stable and video smooth; µs level is not realistic E2E. |
| DL User Experience Data Rate (Mbps) | Very high data rate: 101 Mbps - 500 Mbps | Fluoroscopic + auxiliary video streams; higher for multi view/3D. |
| UL User Experience Data Rate (Mbps) | Low: < 10 Mbps | ≥ 1 Mbps (typically < 10 Mbps). Uplink mainly kinesthetic/control, telemetry, and audio; reserve headroom for secondary video/AR if used. |
| Communication Service Availability | Very high: > 99.999% | ~ 5.26 min outage/year budget. Redundancy required. |
| Guaranteed Bit Rate | GBR | Deterministic bandwidth for imaging/control. |
| Criticality | Safety critical | — |
| Priority Service (NS/EP) | No | Unless jurisdiction requires. |
| Service Continuity | Required | — |
| Mobility | Pedestrian: > 0 km/h to 10 km/h | — |
| Synchronization Precision | > 100 µs | Tight time sync for sensor fusion; keep ≤1 ms. |
| Connection Density | Low: < 1000 | — |
| Communication Direction | Two-way | — |
| Common Communication Mode | Unicast | — |
| Data Reporting Mode | Hybrid driven | — |
| Device Type and Form Factor | > 1 applicable device type | — |
| Device Integration | Integrated | — |
| Device Lifespan | Medium: 4 - 8 years | — |
| Device Power Constraints | Very limited: < 50 mW | — |
| DL E2E Packet Reliability | Moderate: < 10E-4 | Packet error/loss budget aligned to five nines service. |
| Survival Time | > 100 ms | — |
| APIs | Both | — |
| Connectivity Type (BAN/PAN/WAN/LAN) | WAN - Cellular/LPWA/Satellite | WAN. GEO/LEO satellite latencies are too high for control. |
| Sidelink Connectivity | Required | As needed for local OR device mesh |
| Position Accuracy | Stringent (0.1 m - 1 m ) | — |
| Sensing Range Resolution | Very stringent (1 mm - 10 cm) | — |
| False Alarm (FA) | < 1 % | — |
| Missed Detection (MD) | < 1 % | — |
| Edge Computing Service | Required | — |
| AI/ML Service | Required | — |
| AIML: Personalization | Required | — |
| AIML: Training Data Security | Required | — |
| AIML: Service Location | On-premise | — |
| AIML: Ownership, Traceability and Accountability | Required | — |
| AIML: Incentivized/Distributed/Collaborative AI/ML | Required | — |
| Distributed Ledger Service | Required | — |
| Connectivity Subscription Provisioning | Not pre-subscribed (Single or multiple subscriptions supported) | — |
| Number of Subscriptions Supported by the Device | > 1 | — |
| Connectivity Subscription Management | Local device-implemented management (maybe required in IoT without UI) | — |
| User Interface for Device Management | Full keyboard & display, or equivalent (e.g. audible/voice I/O) | — |
| Local Connectivity for Device Configuration and Management | Cellular NPN | — |
| Device Configuration and Customization | Required post-deployment | — |