full Contents for TS 22.261 Word version: 17.2.0
A Latency needs to support example use cases from vertical industries Word-p. 64
The latency values required to support the potential opportunities in the use cases on vertical industries are summarised in Table A.1-1 based on the NGMN white paper on vertical industries [4]. Latency in this table refers to the end-to-end latency at the application layer as defined in clause 3.
Services/ Use cases
Automotive use cases
Transport, logistics, IoT use cases
Health and wellness, smart cities use cases
Media and entertainment
Description
Expand detectable range beyond on board sensor capability by sharing views or detected objects among traffic participants, coordinate trajectories among vehicles, sharing coarse driving intention, real-time remote operation of vehicles
Real-time sensing, reporting, feedback, control, remote, asset tracking, monitoring; context-aware services, recommendations at shopping mall, airport
Live video feed (4K, 8K, 3D for remote healthcare (consultation, monitoring) and assisted surgery, real-time commands to control medical devices for treatment (e.g. medication, surgery); remote monitoring, surveillance and guidance for citizens and law enforcement officers.
Media production services based on aggregation of various media feeds at servers; real-time peer-to-peer or server-client sharing of data (object information) for collaborative gaming, live streaming at live events
Latency
For mid/long-term environment modelling (dynamic high-definition digital map update): Not critical (100 ms end-to-end)
For short term environment modelling (sensor sharing): < 20 ms end-to-end
For cooperation (coordinated control):
- < 3 ms end-to-end for platooning,
- < 10 ms end-to-end for cooperative manoeuvres.
- < 100 ms end-to-end for coarse driving intention
For remote vehicle operation:
10-30 ms end-to-end
For short term environment modelling (sensor sharing): < 20 ms end-to-end
For cooperation (coordinated control):
- < 3 ms end-to-end for platooning,
- < 10 ms end-to-end for cooperative manoeuvres.
- < 100 ms end-to-end for coarse driving intention
For remote vehicle operation:
10-30 ms end-to-end
For massive connectivity for time-critical sensing and feedback:
< 30 ms end-to-end.
For remote drone operation and cooperative farm machinery:
10-30 ms end-to-end
Real-time control for discrete automation:
≤1 ms end-to-end
< 30 ms end-to-end.
For remote drone operation and cooperative farm machinery:
10-30 ms end-to-end
Real-time control for discrete automation:
≤1 ms end-to-end
For real-time video/ telepresence/augmented reality for remote healthcare and assisted surgery, for monitoring and guidance (smart cities):
100 ms end-to-end
Real-time command and control for remote medication and surgery:
10-100 ms end-to-end
For smart grid:
- < 5 ms end-to-end for transmission/grid backbone,
- < 50 ms end-to-end for distribution/grid backhaul,
Time-critical sensing and feedback for smart cities:
30 ms end-to-end
100 ms end-to-end
Real-time command and control for remote medication and surgery:
10-100 ms end-to-end
For smart grid:
- < 5 ms end-to-end for transmission/grid backbone,
- < 50 ms end-to-end for distribution/grid backhaul,
Time-critical sensing and feedback for smart cities:
30 ms end-to-end
For live streaming in crowded areas, services for media production, augmented reality for collaborative gaming etc.:
20 ms end-to-end
20 ms end-to-end
