Content for TS 22.261 Word version: 18.6.1
7.4 KPIs for a 5G system with satellite access
7.5 High-availability IoT traffic
7.6 High data rate and low latency
7.7 KPIs for UE to network relaying in 5G system
7.8 KPIs for 5G Timing Resiliency
7.9 KPIs for ranging based services
7.10 KPIs for AI/ML model transfer in 5GS
7.11 KPIs for tactile and multi-modal communication service
...
...
7.4 KPIs for a 5G system with satellite access |R17| Word‑p. 77
7.4.1 Description Word‑p. 77
Satellite access networks are based on infrastructures integrated on a minimum of satellites that can be placed in either GEO, MEO or LEO.
The propagation delay via satellite associated with these orbit ranges can be summarized in Table 7.4.1-1:
| UE to serving satellite propagation delay [ms] [NOTE 1] | UE to ground max propagation delay [ms] [NOTE 2] | ||
|---|---|---|---|
| Min | Max | ||
| LEO | 3 | 15 | 30 |
| MEO | 27 | 43 | 90 |
| GEO | 120 | 140 | 280 |
|
NOTE 1:
The serving satellite provides the satellite radio link to the UE
NOTE 2:
delay between UE and ground station via satellite link; Inter satellite links are not considered
|
|||
7.4.2 Requirements Word‑p. 77
A 5G system providing service with satellite access shall be able to support GEO based satellite access with up to 285 ms end-to-end latency.
A 5G system providing service with satellite access shall be able to support MEO based satellite access with up to 95 ms end-to-end latency.
A 5G system providing service with satellite access shall be able to support LEO based satellite access with up to 35 ms end-to-end latency.
A 5G system shall support negotiation on quality of service taking into account latency penalty to optimise the QoE for UE.
The 5G system with satellite access shall support high uplink data rates for 5G satellite UEs.
The 5G system with satellite access shall support high downlink data rates for 5G satellite UEs.
The 5G system with satellite access shall support communication service availabilities of at least 99,99%.
| Scenario | Experienced data rate (DL) | Experienced data rate (UL) | Area traffic capacity (DL) (Note 1) | Area traffic capacity (UL) (Note 1) | Overall user density | Activity factor | UE speed | UE type | |
|---|---|---|---|---|---|---|---|---|---|
| Pedestrian (Note 2) | [1] Mbit/s | [100] kbit/s | 1.5 Mbit/s/km² | 150 kbit/s/km² | [100]/km² | [1.5] % | Pedestrian | Handheld | |
| Public safety | [3,5] Mbit/ss | [3.5] Mbit/s | TBD | TBD | TBD | N/A | 100 km/h | Handheld | |
| Vehicular connectivity (Note 3) | 50 Mbit/s | 25 Mbit/s | TBD | TBD | TBD | 50 % | Up to 250 km/h | Vehicle mounted | |
| Airplanes connectivity (Note 4) | 360 Mbit/s/ plane | 180 Mbit/s/ plane | TBD | TBD | TBD | N/A | Up to 1000 km/h | Airplane mounted | |
| Stationary | 50 Mbit/s | 25 Mbit/s | TBD | TBD | TBD | N/A | Stationary | Building mounted | |
| Video surveillance (note 4a) | [0,5] Mbit/s | [3] Mbit/s | TBD | TBD | TBD | N/A | Up to 120km/h or stationary (note 4b) | Vehicle mounted or fixed installation | |
| Narrowband IoT connectivity | [2] kbit/s | [10] kbit/s | 8 kbit/s/km² | 40 kbit/s/km² | [400]/km² | [1] % | [Up to 100 km/h] | IoT | |
|
NOTE 1:
Area capacity is averaged over a satellite beam.
NOTE 2:
Data rates based on Extreme long-range coverage target values in clause 6.17.2. User density based on rural area in Table 7.1-1.
NOTE 3:
Based on Table 7.1-1
NOTE 4:
Based on an assumption of 120 users per plane 15/7.5 Mbit/s data rate and 20 % activity factor per user
NOTE 4a:
Refer to video surveillance data transmitted (in UL) from a UE on the ground (e.g. picture or video from a camera) using satellite NG-RAN to connect to 5GC, and video surveillance-related configuration or control data sent (in DL) to the UE/device. 0.5 Mbit/s for DL experienced data rate is based on MAVLINK protocol that is widely used for UAV control. 3 Mbit/s for UL experienced data rate is based on the assumed sum from 2.5 Mbit/s for video streaming and 0.5 Mbit/s for data transmission.
NOTE 4b:
Up to 120km/h applies to vehicle mounted while stationary applies to fixed installation.
NOTE 5:
All the values in this Table are targeted values and not strict requirements.
NOTE 6:
Performance requirements for all the values in this Table should be analyzed independently for each scenario.
|
|||||||||
7.5 High-availability IoT traffic |R17| Word‑p. 78
7.5.1 Description Word‑p. 78
Several scenarios require the support of highly reliable machine type communication such as those, typically (but not restricted to) related to medical monitoring. They involve different deployment areas, different device speeds and densities and require a high-availability communication service to transfer a low data rate uplink data stream from one or several devices to an application.
Their related performance requirements can be found in Table 7.5.2-1.
7.5.2 Requirements Word‑p. 79
| Profile | Characteristic parameter | Influence quantity | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Communication service availability: target value in % | Communication service reliability (Mean Time Between Failure) | End-to-end latency: maximum | Bit rate | Direction | Message Size [byte] | Transfer Interval | Survival Time | UE speed (km/h) | # of UEs connection | Service Area | |
| Medical monitoring (Note 2) | > 99.999 9 | < 1 year (>> 1 month) | < 100 ms | < 1 Mbit/s | Uplink | ~1,000 | 50 ms | Transfer Interval | < 500 | 10/km² to 1,000/km² | Country wide including rural areas and deep indoor. (Note 1) |
|
NOTE 1:
"deep indoor" term is meant to be places like e.g. elevators, building's basement, underground parking lot…
NOTE 2:
These performance requirements aim energy-efficient transmissions performed using a device powered with a 3.3V battery of capacity < 1000 mAh that can last at least 1 month without recharging and whereby the peak current for transmit operations stays below 50 mA.
|
|||||||||||
7.6 High data rate and low latency |R17| Word‑p. 80
7.6.1 AR/VR Word‑p. 80
Audio-visual interaction is characterised by a human being interacting with the environment or people, or controlling a UE, and relying on audio-visual feedback. In the use cases like VR and interactive conversation the latency requirements include the latencies at the application layer (e.g. codecs), which could be specified outside of 3GPP.
To support VR environments with low motion-to-photon capabilities, the 5G system shall support:
- motion-to-photon latency in the range of 7 to 15 ms while maintaining the required resolution of up to 8k giving user data rate of up to [1Gbit/s] and
- motion-to-sound delay of [< 20 ms].
- in the range of [125 ms yo 5 ms] for audio delayed and
- in the range of [45 ms to 5 ms] for audio advanced.
- Cloud/Edge/Split Rendering - Cloud/Edge/Split Rendering is characterised by the transition and exchange of the rendering data between the rendering server and device.
- Gaming or Training Data Exchanging - This use case is characterised by the exchange of the gaming or training service data between two 5G connected AR/VR devices.
- Consume VR content via tethered VR headset - This use case involves a tethered VR headset receiving VR content via a connected UE; this approach alleviates some of the computation complexity required at the VR headset, by allowing some or all decoding functionality to run locally at the connected UE. The requirements in the Table below refer to the direct wireless link between the tethered VR headset and the corresponding connected UE.
| Use Cases | Characteristic parameter (KPI) | Influence quantity | ||||
|---|---|---|---|---|---|---|
| Max allowed end-to-end latency | Service bit rate: user-experienced data rate | Reliability | # of UEs | UE Speed | Service Area (Note 2) | |
| Cloud/Edge/Split Rendering (Note 1) | 5 ms (i.e. UL+DL between UE and the interface to data network) (Note 4) | 0.1 to [1] Gbit/s supporting visual content (e.g. VR based or high definition video) with 4K, 8K resolution and up to120fps content. | 99.99 % in uplink and 99.9% in downlink (Note 4) | – | Stationary or Pedestrian | Countrywide |
| Gaming or Interactive Data Exchanging (Note 3) | 10ms (Note 4) | 0.1-[1] Gbit/s supporting visual content (e.g. VR based or high definition video) with 4K, 8K resolution and up to 120 frames per second content. | 99.99 % (Note 4) | ≤ [10] | Stationary or Pedestrian | 20 m x 10 m; in one vehicle (up to 120 km/h) and in one train (up to 500 km/h) |
| Consumption of VR content via tethered VR headset (Note 6) | [5 to 10] ms (Note 5) | 0,1 to [10] Gbit/s (Note 5) | [99.99 %] | – | Stationary or Pedestrian | – |
|
NOTE 1:
Unless otherwise specified, all communication via wireless link is between UEs and network node (UE to network node and/or network node to UE) rather than direct wireless links (UE to UE).
NOTE 2:
Length x width (x height).
NOTE 3:
Communication includes direct wireless links (UE to UE).
NOTE 4:
Latency and reliability KPIs can vary based on specific use case/architecture, e.g. for cloud/edge/split rendering, and can be represented by a range of values.
NOTE 5:
The decoding capability in the VR headset and the encoding/decoding complexity/time of the stream will set the required bit rate and latency over the direct wireless link between the tethered VR headset and its connected UE, bit rate from 100 Mbit/s to [10] Gbit/s and latency from 5 ms to 10 ms.
NOTE 6:
The performance requirement is valid for the direct wireless link between the tethered VR headset and its connected UE.
|
||||||
7.7 KPIs for UE to network relaying in 5G system |R17| Word‑p. 81
In several scenarios, it can be beneficial to relay communication between one UE and the network via one or more other UEs. The functional requirements related to relaying can be found in clause 6.9.2. Performance requirements for relaying in different scenarios can be found in Table 7.7-1.
| Scenario | Max. data rate (DL) | Max. data rate (UL) | End-to-end latency (Note 7) | Area traffic capacity (DL) | Area traffic capacity (UL) | Area user density | Area | Range of a single hop (Note 8) | Estimated number of hops |
|---|---|---|---|---|---|---|---|---|---|
| InHome Scenario (note 1) | 1 Gbit/s | 500 Mbit/s | 10 ms | 5 Gbit/s/ home | 2 Gbit/s /home | 50 devices /house | 10m x 10m - 3 floors | 10 m indoor | 2 to 3 |
| Factory Sensors (Note 2) | 100 kbit/s | 5 Mbit/s | 50 ms to 1 s | 1 Gbit/s /factory | 50 Gbit/s /factory | 10,000 devices /factory | 100m x 100m | 30 m indoor / metallic | 2 to 3 |
| Smart Metering (Note 3) | 100 bytes / 15 mins | 100 bytes / 15 mins | 10 s | 200 x 100 bytes / 15 mins /hectare | 200 x 100 bytes / 15 mins /hectare | 200 devices /hectare | 100 m x 100 m | > 100 m indoor / deep indoor | 2 to 5 |
| Containers (Note 4) | 100 bytes / 15 mins | 100 bytes / 15 mins | 10 s | 15,000 x 100 bytes / 15 mins /ship | 15,000 x 100 bytes / 15 mins /ship | 15,000 containers /ship | 400 m x 60 m x 40 m | > 100 m indoor / outdoor / metallic | 3 to 9 |
| Freight Wagons | 100 bytes / 15 mins | 100 bytes / 15 mins | 10 s | 200 x 100 bytes / 15 mins /train | 200 x 100 bytes / 15 mins /train | 120 wagons /train | 1 km | > 100 m outdoor / tunnel | 10 to 15 |
| Public Safety (Note 5) | 12 Mbit/s | 12 Mbit/s | 30 ms | 20 Mbit/s /building | 40 Mbit/s /building | 30 devices /building | 100 m x 100 m - 3 floors | > 50 m indoor (floor or stairwell) | 2 to 4 |
| Wearables (Note 6) | 10 Mbit/s | 10 Mbit/s | 10 ms | 20 Mbit/s per 100 m2 | 20 Mbit/s per 100 m2 | 10 wearables per 100 m2 | 10 m x 10 m | 10 m indoor / outdoor | 1 to 2 |
|
NOTE 1:
Area traffic capacity is determined by high bandwidth consuming devices (e.g. ultra HD TVs, VR headsets), the number of devices has been calculated assuming a family of 4 members.
NOTE 2:
Highest data rate assumes audio sensors with sampling rate of 192 kHz and 24 bits sample size.
NOTE 3:
Three meters (gas, water, electricity) per house, medium density of 50 to 70 houses per hectare.
NOTE 4:
A large containership with a mix of 20 foot and 40 foot containers is assumed.
NOTE 5:
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% in uplink (30% of devices transmit simultaneously at high bitrate) and 15% in downlink.
NOTE 6:
Communication for wearables is relayed via a UE. This relay UE can use a further relay UE.
NOTE 7:
End-to-end latency implies that all hops are included.
NOTE 8:
'Metallic' implies an environment with a lot of metal obstructions (e.g. machinery, containers). 'Deep indoor' implies that there can be concrete walls / floors between the devices.
NOTE 9:
All the values in this Table are example values and not strict requirements.
|
|||||||||
7.8 KPIs for 5G Timing Resiliency |R18| Word‑p. 82
The 5G system shall be able to support a holdover time capability with timing resiliency performance requirements defined in Table 7.8-1.
| Use case | Holdover time (note 3) | Sync target | Sync accuracy | Service area | Mobility | Remarks |
|---|---|---|---|---|---|---|
| Power grid (5G network) | Up to 24 hour | UTC (note 1) | <250 ns to1000 ns (note2) | < 20 km² | low | When 5G System provides direct PTP Grandmaster capability to sub-stations |
| Power grid (time synchronization device) | >5 s | UTC (note 1) | <250 ns to1000 ns (note2) | < 20 km² | low | When 5G sync modem is integrated into PTP grandmaster solution (with 24h holdover capability at sub-stations) |
|
NOTE 1:
A different synchronization target is acceptable as long as the offset is preconfigured when an alternatively sourced time differs from GNSS. In this case, a 5G end device will provide PPS output which can be used for measuring the difference.
NOTE 2:
Different accuracy measurements are based on different configurations needed to support the underlying requirements from IEC 61850-9-3 [32]. The range is between 250 ns and 1000 ns. The actual requirement depends on the specific deployment.
NOTE 3:
This requirement will vary based on deployment options.
|
||||||
| Type of trading activity | Maximum divergence from UTC | Granularity of the timestamp (note 1) |
|---|---|---|
| Activity using high frequency algorithmic trading technique | 100 μs | ≤1 μs |
| Activity on voice trading systems | 1 s | ≤1 s |
| Activity on request for quote systems where the response requires human intervention or where the system does not allow algorithmic trading | 1 s | ≤1 s |
| Activity of concluding negotiated transactions | 1 s | ≤1 s |
| Any other trading activity | 1 ms | ≤1 ms |
|
NOTE 1:
Only relevant for the case where the time synchronization assists in configuring the required granularity for the timestamp (for direct use), otherwise it will be configured separately as part of the financial transaction timestamp process.
|
||
7.9 KPIs for ranging based services |R18| Word‑p. 83
In several scenarios, it can be beneficial to determine the distance between two UEs and/or the direction of one UE from the other one via direct communication connection. The functional requirements related to ranging based services can be found in clause 6.36. Performance requirements for ranging based services in different scenarios can be found in Table 7.9-1.
Key performance indicators and key attributes for ranging are defined as follows:
- Ranging accuracy: describes the absolute value of the deviation of the measured distance and/or direction between two UEs to the true distance and/or direction value.
- Confidence level: describes the percentage of all the possible measured distance and/or direction that can be expected to include the true distance and/or direction considering the ranging accuracy.
- Effective ranging distance: the largest distance between the UE who initiates the ranging and target UEs in the ranging operation.
- Line-of-sight (LOS) Environment: the environment between the UE who initiates the ranging and target UEs, such as LOS and non-LOS (NLOS).
- Coverage: type of radio coverage conditions of the UEs who are involved in ranging, such as in coverage (IC), partial coverage (PC) and out of coverage (OOC). See also Figure 6.36.1-1.
- Relative UE velocity: the target UE can be either static or mobile relative to the UE who initiates the ranging. In the latter, the attribute shall also provide some elements about its motion, e.g. maximum speed, trajectory.
- Availability: percentage value of the amount of time when a ranging system is able to provide the required ranging-related data within the performance targets or requirements divided by the amount of time the system is expected to provide the ranging service in a targeted service area.
- Latency: time elapsed between the event that triggers the determination of the ranging-related data and the availability of the ranging-related data at the ranging system interface.
- Ranging interval: time difference between two consecutive ranging operations.
| Ranging scenario | Ranging Accuracy
(95 % confidence level) |
Availability | Latency | Effective ranging distance | Coverage | NLOS/LOS | Relative UE velocity | Ranging interval | Number of concurrent ranging operation for a UE | Number of concurrent ranging operation in an area | |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Distance Accuracy | Direction Accuracy | ||||||||||
| Smart TV Remoter | 10cm up to 3 meter separation | ±2° horizontal direction accuracy at 0.1 to 3 meter separation and AoA coverage of (-60°) to (+60°); ±2° Elevation direction accuracy at 0.1 to 3 meter separation and AoA coverage of (-45°) to (+45°) | 99 % | 50ms | 10m | IC/PC/OOC | LOS | Static/ Moving (<1m/s) | 50ms | - | - |
| Picture and video sharing based on Ranging results | 10cm | 2° | 99 % | 50ms | 10m | IC/PC/OOC | LOS | Static/ Moving (<1m/s) | 50ms | - | - |
| Distance based smart device control | 10cm | - | 99 % | 100ms | 20m | IC/PC/OOC | LOS | Static/ Moving (<1m/s) | 50ms | 20 | - |
| Smart Vehicle Key | 10 cm | - | 99 % | 50ms | 30m | IC/PC/OOC | LOS | Static/ Moving (<2m/s) | 25ms | - | 50UEs/ (104m²) |
| Touchless Self-checkout Machine Control | 10cm | - | 99% | 150ms | 1m | IC/PC/OOC | LOS | Static/ Moving (<1m/s) | 100ms | - | = |
| Hands Free Access | 10cm | - | 99 % | 500ms | 10 m | IC/PC/OOC | LOS | Static/ Moving (1 m/s) | 50ms | - | 20 UEs/3.14*100m² |
| Smart Transportation Metro/Bus Validation | 10cm | - | 99 % | - | 2m | IC/PC/OOC | LOS | Static/ Moving (3km/h) | 50ms | 20 | 100 in the area of 8 m² |
| Ranging of UE's in front of vending machine | 20cm | 10° | - | 1s | 5m | IC/PC/OOC | LOS | Static/ Moving (<1m/s) | 50ms | - | 10 |
| Finding Items in a supermarket | 50 cm | 5 degree | 95 % | - | 100m | IC/PC/OOC | LOS | Static/ Moving (<1m/s) | 250ms | - | 100 UEs/ (3.14*104m²) |
| distance based intelligent perception for public safety | 50cm | - | 99 % | - | 20m | IC/PC/OOC | LOS | Static/ Moving (<20km/h) | - | 100 | - |
| Long Distance Search | 20m | 5° | 99 % | - | 100m-1km | IC/PC/OOC | LOS | Static/ Moving (up to 10m/s) | 5s | - | - |
| Long range approximate location | [10m] | ±[12.5°] | 99 % | - | 500m | IC/PC/OOC | LOS | Static/ Moving (<10m/s) | - | 1 | [50]UEs/ (104m²) |
7.10 KPIs for AI/ML model transfer in 5GS |R18| Word‑p. 86
The 5G system shall support split AI/ML inference between UE and Network Server/Application function with performance requirements as given in Table 7.10-1.
| Uplink KPI | Downlink KPI | Remarks | |||||||
|---|---|---|---|---|---|---|---|---|---|
| Max allowed UL end-to-end latency | Experienced data rate | Payload size | Communication service availability | Reliability | Max allowed DL end-to-end latency | Experienced data rate | Payload size | Reliability | |
| 2 ms | 1.08 Gbit/s | 0.27 MByte | 99.999 % | 99.9 % | 99.999 % | Split AI/ML image recognition | |||
| 100 ms | 1.5 Mbit/s | 100 ms | 150 Mbit/s | 1.5 MByte /frame | Enhanced media recognition | ||||
| 4.7 Mbit/s | 12 ms | 320 Mbit/s | 40 kByte | Split control for robotics | |||||
|
NOTE 1:
Communication service availability relates to the service interfaces, and reliability relates to a given system entity. One or more retransmissions of network layer packets can take place in order to satisfy the reliability requirement.
|
|||||||||
The 5G system shall support AI/ML model downloading with performance requirements as given in Table 7.10-2.
| Max allowed DL end-to-end latency | Experienced data rate (DL) | Model size | Communication service availability | Reliability | User density | # of downloaded AI/ML models | Remarks |
|---|---|---|---|---|---|---|---|
| 1s | 1.1Gbit/s | 138MByte | 99.999 % | 99.9% for data transmission of model weight factors; 99.999% for data transmission of model topology | AI/ML model distribution for image recognition | ||
| 1s | 640Mbit/s | 80MByte | 99.999 % | AI/ML model distribution for speech recognition | |||
| 1s | 512Mbit/s(see note 1) | 64MByte | Parallel download of up to 50 AI/ML models | Real time media editing with on-board AI inference | |||
| 1s | 536MByte | up to 5000~ 10000/km2 in an urban area | AI model management as a Service | ||||
| 1s | 22Mbit/s | 2.4MByte | 99.999 % | AI/ML based Automotive Networked Systems | |||
| 1s | 500MByte | Shared AI/ML model monitoring | |||||
| 3s | 450Mbit/s | 170MByte | Media quality enhancement | ||||
|
NOTE 1:
512Mbit/s concerns AI/ML models having a payload size below 64 MB. TBD for larger payload sizes.
NOTE 2:
Communication service availability relates to the service interfaces, and reliability relates to a given system entity. One or more retransmissions of network layer packets can take place in order to satisfy the reliability requirement.
|
|||||||
The 5G system shall support Federated Learning between UE and Network Server/Application function with performance requirements as given in Table 7.10-3.
| Max allowed DL or UL end-to-end latency | DL experienced data rate | UL experienced data rate | DL packet size | UL packet size | Communication service availability | Remarks |
|---|---|---|---|---|---|---|
| 1s | 1.0Gbit/s | 1.0Gbit/s | 132MByte | 132MByte | Uncompressed Federated Learning for image recognition | |
| 1s | 80.88Mbit/s | 80.88Mbit/s | 10Mbyte | 10Mbyte | TBD | Compressed Federated Learning for image/video processing |
| 1s | TBD | TBD | 10MByte | 10MByte | Data Transfer Disturbance in Multi-agent multi-device ML Operations |
7.11 KPIs for tactile and multi-modal communication service |R18| Word‑p. 87
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 server) | 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) [40] | 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% [40] | 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% [40] | 1500 | Stationary or Pedestrian | typically
< 100 km² (note 5) | Video |
| 10 ms | 5-512 kbit/s | 99.9% [40] | 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) [40] | 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% [40] | 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% [40] | 2-8 (1 DoF) | Stationary or Pedestrian | ≤ 1 km² | Haptic feedback | |
| 5 ms | 1-100 Mbit/s | 99.999% [40] | 1500 | Stationary or Pedestrian | ≤ 1 km² | Video | |
| 5 ms | 5-512 kbit/s | 99.9% [40] | 50-100 | Stationary or Pedestrian | ≤ 1 km² | Audio | |
| 5 ms | < 1Mbit/s | 99.999% [40] | - | 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% [40] [45] | 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% [40] [45] | 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% [40] [45] | 1500 | Stationary or Pedestrian | 100 km² | Video | |
| 10ms | 5-512 kbit/s | 99,9% [40] [45] | 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) [40] [45] | 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) [40] [45] | 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% [40] [45] | 2000-4000 | high-dynamic | 4 km² | Video | |
| 1-10ms | 100-500 kbit/s | 99,9% [40] [45] | 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 % [40] | 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 % [40] | 1500 | Stationary or Pedestrian | ≤ 100 km²
(note 5) | Video | |
| <150 ms [39] | 5-512 kbit/s | 99.9 % [40] | 50 | Stationary or Pedestrian | ≤ 100 km²
(note 5) | Audio | |
| <300 ms | 600 Mbit/s | 99.9 % [40] | 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 % [40] | 1500 | Stationary or Pedestrian | ≤ 100 km²
(note 5) | Biometric / Affective |
| <400 ms [39] | 1-100 Mbit/s | 99.999 % [40] | 1500 | Workers: Stationary/ or Pedestrian, UAV: [30-300mph] | ≤ 100 km² (note 5) | Video | |
| <150 ms [39] | 5-512 kbit/s | 99.9 % [40] | 50 | Stationary or Pedestrian | ≤ 100 km²
(note 5) | Audio | |
| <300 ms | 600 Mbit/s | 99.9 % [40] | 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 [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.
|
|||||||
