Data Types | Latency | Jitter | Packet Loss Rate | Data Ref | |
---|---|---|---|---|---|
2D Camera Flow | <150ms | 3-30ms | <10-3 | <10Mbps | |
Real-Time Multimedia Stream | 3D Camera Flow | <150ms | 3-30ms | <10-3 | 137 Mbps - 1.6Gbps [for good imaging this could be up to 4Gbps] |
Audio Flow | <150ms | <30ms | <10-2 | 22-200Kbps | |
Temp | <250ms | <10-3 | <10kbps | ||
Blood Pressure | <250ms | <10-3 | <10kbps | ||
Physical Vital Sign | Heart Rate | <250ms | <10kps | ||
Respiration Rate | <250ms | <10kps | |||
ECG | <250ms | 72kbps | |||
EEG | <250ms | 86.4kps | |||
EMG | <250ms | 1.536Mbs | |||
Haptic Feedback | Force (considering human reaction) | 3-10ms (20ms) | <2ms | <10-4 | 128-400kps |
Vibration | <5.5ms | <2ms | <10-4 | 128-400kps |
Reference number | Requirement text | Application / Transport | Comment |
---|---|---|---|
5.6.1 | Clock synchronization service level requirements related to global clock domain management | T | See TS 22.104 |
8.9 | The 5G system shall support data integrity protection and confidentiality methods that serve URLLC and energy constrained devices. | T | Requirement taken from TS 22.261, however need to add "high data rates" to the requirement text. The medical equipment being used in this use case may require solutions that serve URLLC communication as well as very high data rates. The equipment is typically not energy constrained. |
Use case | Characteristic parameter | Influence quantity | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
5.3.3 - Communication QoS requirement for robotic telesurgery | Communication service availability: target value in % | Communication service reliability: Mean Time Between Failure | End-to-end latency: maximum | Bit rate | Direction | Message Size [byte] | Survival time | UE speed | # of active UEs | Service Area [m2] (note 2) |
Stereoscopic 4K 60 fps HDR 10bits frame packed real time video (loss less compressed) | 99.9999 | >1 year | < 250 ms | 6 Gbit/s | UE to Network; Network to UE | ~1500 - ~9000 (note 1) | ~16 ms | stationary | < 2 per 1000 km2 | <400 |
4K 60 fps 12 bits per pixel color coded (e.g. YUV 4:1:1) real time video (loss less compressed) | 99.999 | >>1 month (<1 year) | < 250 ms | 2 Gbit/s | Network to UEs | ~1500 - ~9000 (note 1) | ~16 ms | stationary | < 5 per 100m2 (note 3) | <400 |
Haptic Feedback | 99.9999 | >1 year | <20 ms | 2 Mbits/s | Network to UE | 250 | ~1 ms | stationary | < 2 per 1000 km2 | <400 |
Haptic Feedback | 99.9999 | >1 year | <20 ms | 16 Mbits/s | UE to Network | ~2000 | ~1 ms | stationary | < 2 per 1000 km2 | <400 |
NOTE 1:
MTU size of 1500 bytes is not generally suitable to gigabits connections as it induces many interruptions and loads on CPUs. On the other hand, Ethernet jumbo frames of up to 9000 bytes require all equipment on the forwarding path to support that size in order to avoid fragmentation.
NOTE 2:
Straight line distance between surgeon's console at the hospital and the remote robotic telesurgery system.
NOTE 3:
This comprises a maximum of 5 displays gathered in the same room considering a room density <2 per 1000 km2
|
Number of devices for clock synchronisation | Clock synchronicity requirement | Service area (note 1) |
---|---|---|
Up to 10 UEs (note 2) | < 50 μs | 400 km |
NOTE 1:
Straight line distance between surgeon's console at the hospital and the remote telesurgery system
NOTE 1:
This comprises displays, robotic actuators, haptic feedback sensors, located at either end of the robotic system (robot or console) and training monitors at an intermediary location
|