Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 22.261  Word version:  20.0.0

Top   Top   Up   Prev   Next
0…   4…   6…   6.4…   6.8…   6.12…   6.15…   6.16…   6.22…   6.26…   6.30…   6.37…   6.41…   6.43…   6.46…   7…   7.4…   7.9   7.10…   7.11…   8…   D…   D.3…   F…   G…   H   I   J… 
7.11 KPIs for tactile and multi-modal communication service  7.12 KPIs for direct device connection for Public Safety 
...

 

7.11  KPIs for tactile and multi-modal communication service |R18|  p. 109

The 5G system shall support tactile and multi-modal communication services with the following KPIs.
Use Cases Charac­teristic para­meter (KPI) Influ­ence quan­tity Remarks
Max allowed end-to-end la­tency Service bit rate: user-expe­rienced data rate Relia­bility Message size (byte) UE Speed Service Area
Immersive multi-modal VR (UL: device → application server)5 ms
(note 2)		16 kbit/s -2 Mbit/s
(without haptic compres­sion encoding);
0.8 - 200 kbit/s
(with haptic compres­sion encoding)		99.9%
(without haptic compres­sion encoding)
99.999%
(with haptic compres­sion encoding)
[40]		1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48
More DoFs can be supported by the haptic device		Statio­nary or Pedes­triantypically
< 100 km²
(note 5)		Haptic feedback
5 ms< 1Mbit/s99.99%
[40]		1500Statio­nary or Pedes­triantypically
< 100 km²
(note 5)		Sensing information e.g. position and view information generated by the VR glasses
Immersive multi-modal VR (DL: application sever → device)10 ms
(note1)		1-100 Mbit/s99.9%
[40]		1500Statio­nary or Pedes­triantypically
< 100 km²
(note 5)		Video
10 ms5-512 kbit/s99.9%
[40]		50Statio­nary or Pedes­triantypically
< 100 km²
(note 5)		Audio
5 ms
(note 2)		16 kbit/s -2 Mbit/s
(without haptic compres­sion encoding);
0.8 - 200 kbit/s
(with haptic compres­sion encoding)		99.9%
(without haptic compres­sion encoding)
99.999%
(with haptic compres­sion encoding)
[40]		1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48		Statio­nary or Pedes­triantypically
< 100 km²
(note 5)		Haptic feedback
Remote control robot1-20ms16 kbit/s -2 Mbit/s
(without haptic compres­sion encoding);
0.8 - 200 kbit/s
(with haptic compres­sion encoding)		99.999%
[40]		2-8 (1 DoF)high-dynamic (≤ 50 km/h)≤ 1 km²Haptic feedback
20-100ms16 kbit/s -2 Mbit/s
(without haptic compres­sion encoding);
0.8 - 200 kbit/s
(with haptic compres­sion encoding)		99.999%
[40]		2-8 (1 DoF)Statio­nary or Pedes­trian≤ 1 km²Haptic feedback
5 ms1-100 Mbit/s99.999%
[40]		1500Statio­nary or Pedes­trian≤ 1 km²Video
5 ms5-512 kbit/s99.9%
[40]		50-100Statio­nary or Pedes­trian≤ 1 km²Audio
5 ms< 1Mbit/s99.999%
[40]		-Statio­nary or Pedes­trian≤ 1 km²Sensor information
Skillset sharing low- dynamic robotics (including teleo­peration) Con­troller to con­trolee5-10ms0.8 - 200 kbit/s (with compres­sion)99,999%
[40] [45]		1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48		Statio­nary or Pedes­trian100 km²Haptic
(position, velocity)
Skillset sharing low- dynamic robotics (inclu­ding tele­operation) Con­trolee to con­troller5-10ms0.8 - 200 kbit/s (with compres­sion)99,999%
[40] [45]		1 DoF: 2-8
10 DoFs: 20-80
100 DoFs: 200-800		Statio­nary or Pedes­trian100 km²Haptic feedback
10ms1-100 Mbit/s99,999%
[40] [45]		1500Statio­nary or Pedes­trian100 km²Video
10ms5-512 kbit/s99,9%
[40] [45]		50Statio­nary or Pedes­trian100 km²Audio
Skillset sharing Highly dynamic/ mobile robotics Controller to controlee 1-5ms16 kbit/s -2 Mbit/s
(without haptic compres­sion enco­ding);
0.8 - 200 kbit/s
(with haptic compres­sion enco­ding)		99,999% (with compres­sion)
99,9% (w/o compres­sion)
[40] [45]		1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48		high-dynamic4 km²Haptic
(position, velocity)
Skillset sharing Highly dyna­mic/ mobile robo­tics Con­trolee to con­troller1-5ms0.8 - 200 kbit/s99,999% (with compres­sion)
99,9% (w/o compres­sion)
[40] [45]		1 DoF: 2-8
10 DoFs: 20-80
100 DoFs: 200-800		high-dynamic4 km²Haptic feedback
1-10ms1-10 Mbit/s99,999%
[40] [45]		2000-4000high-dynamic4 km²Video
1-10ms100-500 kbit/s99,9%
[40] [45]		100high-dynamic4 km²Audio
Immer­sive multi-modal navi­gation appli­cations Remote Site → Local Site (DL)50 ms [39]16 kbit/s -2 Mbit/s
(without haptic compres­sion enco­ding);
0.8 - 200 kbit/s
(with haptic compres­sion encoding)		99.999 %
[40]		1 DoF: 2 to 8
10 DoF: 20 to 80
100 DoF: 200 to 800		Statio­nary or Pedes­trian≤ 100 km²
(note 5)		Haptic feedback
<400 ms
[39]		1-100 Mbit/s99.999 %
[40]		1500Statio­nary or Pedes­trian≤ 100 km²
(note 5)		Video
<150 ms
[39]		5-512 kbit/s99.9 %
[40]		50Statio­nary or Pedes­trian≤ 100 km²
(note 5)		Audio
<300 ms600 Mbit/s99.9 %
[40]		1500Statio­nary or Pedes­trian≤ 100 km²
(note 5)		VR
Immer­sive multi-modal navi­gation appli­cations Local Site → Remote Site (UL)<300 ms12 kbit/s
[26]		99.999 %
[40]		1500Statio­nary or Pedes­trian≤ 100 km²
(note 5)		Biometric / Affective
<400 ms
[39]		1-100 Mbit/s99.999 %
[40]		1500Workers: Statio­nary/ or Pedes­trian, UAV: [30-300mph]≤ 100 km² (note 5)Video
<150 ms
[39]		5-512 kbit/s99.9 %
[40]		50Statio­nary or Pedes­trian≤ 100 km²
(note 5)		Audio
<300 ms600 Mbit/s99.9 %
[40]		1500Statio­nary or Pedes­trian≤ 100 km²
(note 5)		VR
NOTE 1:
Motion-to-photon delay (the time difference between the user's motion and corresponding change of the video image on display) is less than 20 ms, and the communication latency for transferring the packets of one audio-visual media is less than 10 ms, e.g. the packets corresponding to one video/audio frame are transferred to the devices within 10 ms.
NOTE 2:
According to IEEE 1918.1 [40] as for haptic feedback, the latency is less than 25 ms for accurately completing haptic operations. As rendering and hardware introduce some delay, the communication delay for haptic modality can be reasonably less than 5 ms, i.e. the packets related to one haptic feedback are transferred to the devices within 10 ms.
NOTE 3:
Haptic feedback is typically haptic signal, such as force level, torque level, vibration and texture.
NOTE 4:
The latency requirements are expected to be satisfied even when multimodal communication for skillset sharing is via indirect network connection (i.e., relayed by one UE to network relay).
NOTE 5:
In practice, the service area depends on the actual deployment. In some cases a local approach (e.g. the application servers are hosted at the network edge) is preferred in order to satisfy the requirements of low latency and high reliability.
Up

7.12  KPIs for direct device connection for Public Safety |R19|  p. 112

The functional requirements related to relaying of traffic between two Public Safety UEs using direct device connection via one or more ProSe UE-to-UE relay(s) can be found in clause 6.9.3. Performance requirements for relaying in different scenarios can be found in Table 7.12-1.
Scenario Max. data rate
(note 1)		 End-to-end latency
(note 3)		 Area traffic capacity Area user density Area Range of a single hop Estimated number of hops
Public Safety
(note 2)		12 Mbit/s125 ms40 Mbit/s /5000m230 devices /10000m210,000 m2> 50 m 2 to 6
NOTE 1:
The maximum data rate applies for both the traffic transmitted from the UE and received by the UE.
NOTE 2:
A mix of MCPTT, MCVideo, and MCData is assumed. Average 3 devices per firefighter / police officer, of which one video device. Area traffic based on 1080 p, 60 fps is 12 Mbit/s video, with an activity factor of 30% transmit from the UE (30% of devices transmit simultaneously at high bitrate) and 15% received by the UE.
NOTE 3:
End-to-end latency implies that all hops are included.
Up

Up   Top   ToC