Content for TR 22.847 Word version: 18.2.0
6 Consolidated requirements
6.1 Consolidated potential requirements
6.2 Consolidated potential KPIs
7 Conclusions and recommendations
$ Change history
6 Consolidated requirements p. 31
6.1 Consolidated potential requirements p. 31
| CPR # | Original PR # | Consolidated Potential Requirement | Comment |
|---|---|---|---|
| CPR 6.1-1 | [PR 5.2.6-2]
[PR 5.3.6-2] [PR 5.5.6-1] [PR 5.6.6-1] [PR 5.7.6-2 [PR 5.8.6-1] | The 5G system shall enable an authorized 3rd party to provide policy(ies) for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information. | |
| CPR 6.1-2 | [PR 5.5.6-2]
[PR 5.6.6-2] [PR 5.7.6-3] [PR 5.8.6-2] | The 5G system shall support a means to apply 3rd party provided policy(ies) for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information. |
6.2 Consolidated potential KPIs p. 31
The 5G system shall support tactile and multi-modal communication services with the following KPIs.
| Use Cases | Characteristic parameter (KPI) | Influence quantity | Remarks | ||||
|---|---|---|---|---|---|---|---|
| Max allowed end-to-end latency | Service bit rate: user-experienced data rate | Reliability | Message size (byte) | UE Speed | Service Area | ||
| Immersive multi-modal VR (UL: device → application sever) | 5 ms
(note 2) | 16 kbit/s - 2 Mbit/s
(without haptic compression encoding); 0.8 - 200 kbit/s (with haptic compression encoding) | 99.9%
(without haptic compression encoding) 99.999% (with haptic compression encoding) [3] | 1 DoF: 2-8 3 DoFs: 6-24 6 DoFs: 12-48 More DoFs can be supported by the haptic device | Stationary or Pedestrian | typically
< 100 km²
(note 5) | Haptic feedback |
| 5 ms | < 1Mbit/s | 99.99% [3] | 1500 | Stationary or Pedestrian | typically
< 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/s | 99.9% [3] | 1500 | Stationary or Pedestrian | typically
< 100 km² (note 5) | Video |
| 10 ms | 5-512 kbit/s | 99.9% [3] | 50 | Stationary or Pedestrian | typically
< 100 km² (note 5) | Audio | |
| 5 ms
(note 2) | 16 kbit/s - 2 Mbit/s
(without haptic compression encoding); 0.8 - 200 kbit/s (with haptic compression encoding) | 99.9%
(without haptic compression encoding) 99.999% (with haptic compression encoding) [3] | 1 DoF: 2-8 3 DoFs: 6-24 6 DoFs: 12-48 | Stationary or Pedestrian | typically
< 100 km² (note 5) | Haptic feedback | |
| Remote control robot | 1-20ms | 16 kbit/s - 2 Mbit/s
(without haptic compression encoding); 0.8 - 200 kbit/s (with haptic compression encoding) | 99.999% [3] | 2-8 (1 DoF) | high-dynamic (≤ 50 km/h) | ≤ 1 km² | Haptic feedback |
| 20-100ms | 16 kbit/s - 2 Mbit/s
(without haptic compression encoding); 0.8 - 200 kbit/s (with haptic compression encoding) | 99.999% [3] | 2-8 (1 DoF) | Stationary or Pedestrian | ≤ 1 km² | Haptic feedback | |
| 5 ms | 1-100 Mbit/s | 99.999% [3] | 1500 | Stationary or Pedestrian | ≤ 1 km² | Video | |
| 5 ms | 5-512 kbit/s | 99.9% [3] | 50-100 | Stationary or Pedestrian | ≤ 1 km² | Audio | |
| 5 ms | < 1Mbit/s | 99.999% [3] | - | Stationary or Pedestrian | ≤ 1 km² | Sensor information | |
| Skillset sharing low- dynamic robotics
(including teleoperation)
Controller to controlee | 5-10ms | 0.8 - 200 kbit/s (with compression) | 99,999% [3][27] | 1 DoF: 2-8 3 DoFs: 6-24 6 DoFs: 12-48 | Stationary or Pedestrian | 100 km² | Haptic (position, velocity) |
| Skillset sharing low- dynamic robotics
(including teleoperation) Controlee to controller | 5-10ms | 0.8 - 200 kbit/s (with compression) | 99,999% [3] [27] | 1 DoF: 2-8 10 DoFs: 20-80 100 DoFs: 200-800 | Stationary or Pedestrian | 100 km² | Haptic feedback |
| 10ms | 1-100 Mbit/s | 99,999% [3] [27] | 1500 | Stationary or Pedestrian | 100 km² | Video | |
| 10ms | 5-512 kbit/s | 99,9% [3] [27] | 50 | Stationary or Pedestrian | 100 km² | Audio | |
| Skillset sharing Highly dynamic/ mobile robotics
Controller to controlee | 1-5ms | 16 kbit/s - 2 Mbit/s
(without haptic compression encoding); 0.8 - 200 kbit/s (with haptic compression encoding) | 99,999%
(with compression) 99,9% (w/o compression) [3] [27] | 1 DoF: 2-8 3 DoFs: 6-24 6 DoFs: 12-48 | high-dynamic | 4 km² | Haptic (position, velocity) |
| Skillset sharing Highly dynamic/ mobile robotics
Controlee to controller | 1-5ms | 0.8 - 200 kbit/s | 99,999%
(with compression) 99,9% (w/o compression) [3] [27] | 1 DoF: 2-8 10 DoFs: 20-80 100 DoFs: 200-800 | high-dynamic | 4 km² | Haptic feedback |
| 1-10ms | 1-10 Mbit/s | 99,999% [3] [27] | 2000-4000 | high-dynamic | 4 km² | Video | |
| 1-10ms | 100-500 kbit/s | 99,9% [3] [27] | 100 | high-dynamic | 4 km² | Audio | |
| Immersive multi-modal navigation applications
Remote Site → Local Site (DL) | 50 ms [39] | 16 kbit/s - 2 Mbit/s
(without haptic compression encoding); 0.8 - 200 kbit/s (with haptic compression encoding) | 99.999 % [3] | 1 DoF: 2 to 8 10 DoF: 20 to 80 100 DoF: 200 to 800 | Stationary or Pedestrian | ≤ 100 km²
(note 5) | Haptic feedback |
| <400 ms [39] | 1-100 Mbit/s | 99.999 % [3] | 1500 | Stationary/ or Pedestrian, | ≤ 100 km²
(note 5) | Video | |
| <150 ms [39] | 5-512 kbit/s | 99.9 % [3] | 50 | Stationary or Pedestrian | ≤ 100 km²
(note 5) | Audio | |
| <300 ms | 600 Mbit/s | 99.9 % [3] | 1500 | Stationary or Pedestrian | ≤ 100 km²
(note 5) | VR | |
| Immersive multi-modal navigation applications
Local Site → Remote Site (UL) | <300 ms | 12 kbit/s [26] | 99.999 % [3] | 1500 | Stationary or Pedestrian | ≤ 100 km²
(note 5) | Biometric / Affective |
| <400 ms [39] | 1-100 Mbit/s | 99.999 % [3] | 1500 | Workers: Stationary/ or Pedestrian, UAV: [30-300mph] | ≤ 100 km²
(note 5) | Video | |
| <150 ms [39] | 5-512 kbit/s | 99.9 % [3] | 50 | Stationary or Pedestrian | ≤ 100 km²
(note 5) | Audio | |
| <300 ms | 600 Mbit/s | 99.9 % [3] | 1500 | Stationary or Pedestrian | ≤ 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 [3] 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.
|
|||||||
7 Conclusions and recommendations p. 34
This TR provides a number of use cases for tactile and multi-modality communication services such as immersive multi-modal virtual reality (VR) application, remote controlled robots, support of skillset sharing for robots, haptic feedback for dangerous environments, live event selective immersion, virtual factory, and others.
The potential new requirements for each use cases are compiled into a set of potential consolidated requirements, including functional requirements and performance requirements, wherein a set of KPIs are defined, such as max allowed end-to-end latency, service bit rate, user-experienced data rate, reliability, message size, service area.
The resulting consolidated potential requirements and KPIs identified in this TR can be considered for the development of normative requirements.
$ Change history p. 35
