Use Cases | Characteristic parameter (KPI) | Influence quantity | Remarks | |||||||
---|---|---|---|---|---|---|---|---|---|---|
Max allowed end-to-end latency | Service bit rate: user-experienced data rate | Reliability | Area Traffic capacity | Message Data Volume (bits) | Transfer interval | Position accuracy | UE speed | Service Area | ||
Metaverse-based Tele-Operated Driving | [100] ms [25] (NOTE 1) | [10~50 Mbit/s] [25] | 99%
[25] | [~360 Mbit/s/km2 ]
(NOTE 4) | ~8Mbps video stream. Four cameras per vehicle (one for each side): 4*8=32Mbps.
Sensor data (interpreted objects).
Assuming 1 kB/object/100 ms and 50 objects: 4 Mbps [25] |
20~100 ms [25]
(NOTE 2) | [10] cm [25] | [10-50] km/h (vehicle) [25] Stationary/Pedestrian (user) |
Up to 10km radius [25]
(NOTE 3) | UL (NOTE 5) |
[20] ms [25] | [0.1~0.4 Mbit/s] [25] | 99,999% [25] | [~4 Mbit/s/km2 ]
(NOTE 4) | Up to 8Kb
per message [25] |
20 ms [25]
(NOTE 2) | [10] cm [25] | [10-50] km/h (vehicle) [25] Stationary/Pedestrian (user) |
Up to 10km radius [25]
(NOTE 3) | DL (NOTE 5) | |
1-20ms (NOTE 6) | 16 kbit/s -2 Mbit/s
(without haptic compression encoding); 0.8 - 200 kbit/s (with haptic compression encoding) (NOTE 6) | 99.999%
(NOTE 6) | [~20 Mbit/s/km2 ]
(NOTE 4) | 2-8 (1 DoF) (NOTE 6) | Stationary/ Pedestrian (user) |
Up to 10km radius [25]
(NOTE 3) | Haptic feedback | |||
NOTE 1:
The end-to-end latency refers to the transmission delay between a UE and the mobile metaverse server or vice-versa, not including sensor acquisition or actuator control on the vehicle side, processing, and rendering on the user side (estimated additional 100ms total). Target e2e user experienced max delay depends on reaction time of the remote driver (e.g. at 50km/h, 20ms means 27cm of remote vehicle movement).
NOTE 2:
UL data transfer interval around 20ms (video) to 100ms (sensor), DL data transfer interval (commands) around 20ms.
NOTE 3:
The service area for teleoperation depends on the actual deployment; for example, it can be deployed for a warehouse, a factory, a transportation hub (seaport, airport etc.), or even a city district or city. In some cases, a local approach (e.g., the application servers are hosted at the network edge) is preferred to satisfy low latency and high-reliability requirements.
NOTE 4:
The area traffic capacity is calculated for one 5G network, considering 4 cameras + sensors on each vehicle. Density is estimated to 10 vehicles/km2, each of the vehicles with one user controlling them. [25]
NOTE 5:
Based on [25]. UL is real-time vehicle data (video streaming and/or sensor data), DL is control traffic (commands from the remote driver).
NOTE 6:
KPI comes from clause 7.11 of TS 22.261"remote control robot" use case.
|