Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 22.125  Word version:  17.2.0

Top   Top   Up   Prev   None
0…   7…

 

7  Performance requirements |R17|

7.1  KPIs for services provided to the UAV applications

The 5G system shall be able to provide unmanned aerial vehicle with the service performance requirements reported in Table 7.1-1.
UAV originated QoS in the table refers to the QoS of Uplink data (e.g. from UAV to the network side). UAV terminated QoS is the QoS of downlink data (e.g. from the network side to UAV).
The data transmitted by the 5G system includes data collected by hardware devices installed on UAV such as cameras, e.g. pictures, videos and files. It is also possible to transmit some software calculation or statistical data, e.g. UAV management data. The service control data of transmitted by the 5G system may be based on application triggers, such as switch, rotation, promotion and demotion control of equipment on UAV. Various UAV applications may require different uplink and downlink QoS at the same time. The 5G system may simultaneously provide services to other users on the ground (e.g., the KPIs for rural and urban scenarios as defined in clause 7.1 of TS 22.261) in the same area without service degradation.
Use case
Services
Data rate
End to end Latency
Altitude AGL
service area (Note 4)

1
8K video live broadcast
100 Mbps UAV originated
200 ms
< 100 m
Urban, scenic area
600Kbps UAV terminated
20 ms
< 100 m
Urban, scenic area
2
Laser mapping/HD patrol (Note 7)
120 Mbps UAV originated (Note 1)
200 ms
30-300 m
Urban, rural area, scenic area
300Kbps UAV terminated
20 ms
30-300 m
Urban, rural area, scenic area
3
4*4K AI surveillance
120 Mbps UAV originated
20 ms
< 200 m
Urban, rural area
50Mbps UAV terminated
20 ms
< 200 m
Urban, rural area
4
Remote UAV controller through HD video
≥ 25Mbps UAV originated (Note 3)
100 ms
< 300 m
Urban, rural area
300Kbps UAV terminated
20 ms
<300 m
Urban, rural area
5
Real-Time Video
0.06 Mbps w/o video UAV originated
100 ms
Urban, rural, countryside
6
Video streaming
4 Mbps for 720p video  9 Mbps for 1080p video UAV originated
100 ms
Urban, rural, countryside
7
Periodic still photos
1Mbps UAV originated  1 S  0.1 m  < 120m  –  Urban, rural area
1s
< 120 m
Urban, rural, countryside


Up

7.2  KPIs for UAV command and controlWord‑p. 12
UAVs may use a variety of flight command and control modes. Command and control (C2) communications refers to the two-way communication, which may include video, required to control the operation of the UAV itself. C2 messages may be communicated with the UAV controller, the UTM or both and may or may not be periodic. UAV controller and UTM communications may happen at essentially the same time with different required QoS. Any mission specific communication (e.g. HD video for area surveillance), if required, is additional. Different modes of control and their typical KPIs are listed in this clause below. The 5G system shall support UAV operation at altitudes of at least 120m / 400ft above ground level, e.g. the services should be provided and characterized up to 3000ft AGL.
Control Mode
Function
Typical Message Interval
Max UAV ground speed
Typical message Size (note 1)
End to end Latency
Reliability (note 2)
Positive ACK (note 8)

Steer to waypoints (note 3)
UAV terminated C2 message
≥ 1 s
300 km/h
100 byte
1 s
99.9%
Required
UAV originated C2 message (note 4)
1 s
300 km/h
84-140 byte
1 s
99.9%
Not Required
Direct stick steering (note 5)
UAV terminated C2 message
40 ms (note 6)
60 km/h
24 byte
40 ms
99.9%
Required
UAV originated C2 message (note 7)
40 ms
60 km/h
84-140 byte
40 ms
99.9%
Not Required
Automatic flight on UTM (note 10)
UAV terminated C2 message
1 s
300 km/h
< 10K byte
5 s (note 9)
99.9%
Required
UAV originated C2 message
1 s (note 9)
300 km/h
1500 byte
5 s (note 9)
99.9%
Required
Approaching Autonomous Navigation Infrastructure
UAV terminated C2 message
500 ms
50 km/h
4k byte
10 ms
99%
Required
UAV originated C2 message
500 ms
50 km/h
4k byte
140 ms
99.99%
Required


 
Scenario (note 2)
Data rate
End to end Latency
Reliability (note 1)
Direction
Positive ACK required

VLOS (visual line of sight)
2 Mpbs at 480 p, 30 fps
1 s
99.9%
Sent by UAV
Not Required
Non-VLOS
4 Mbps at 720 p, 30 fps
140 ms
99.99%
Sent by UAV
Not Required


Up

7.3  Positioning performance requirementsWord‑p. 13
Table 7.3-1 below lists typical scenarios and the corresponding positioning requirements for horizontal and vertical accuracy, availability, heading, latency, and UE speed.
Scenario
Accuracy (95 % confidence level)
Horizontal accuracy
Vertical accuracy
Availability
Heading
Latency for position estimation of UE
UE Speed
Corresponding Positioning Service Level in TS 22.261

8K video live broadcast
[0.5 m]
[1 m]
99%
1s
[< 120 km/h]
5
Laser mapping/HD patrol
[0.5 m]
[1 m]
99%
1s
[<120 km/h]
5
4*4K AI surveillance
[0.1 m]
[<60 km/h]
Remote UAV controller through HD video
[0.5 m]
[1 m]
99%
1s
[<120 km/h]
5
Periodic still photos
[0.1 m]
[1 m]
[<60 km/h]


Up

7.4  Other requirementsWord‑p. 14
[R-7.4-001]
The 5G system shall support a mechanism to switch between C2 communication modes for UAS operation, e.g. from indirect C2 communication to direct C2 communication, and ensure the disconnect time is below the latency requirements.
[R-7.4-002]
The 3GPP system shall enable concurrent communications between the UAV-controller and UAV and between the UTM and the UAV that may require different KPIs.
[R-7.4-003]
The 3GPP system shall be capable of switching between the KPIs, as requested by the UAV-controller or the UTM, within [500ms].
Up

A  UAS Reference ModelWord‑p. 15

A.1  UAS Reference Model in 3GPP ecosystem

Reproduction of 3GPP TS 22.125, Figure B.1-1: UAS model in 3GPP ecosystem.
Up
In the UAS reference model:
  • a UAS is composed of one UAV and one UAV controller in this illustration
  • UAVs are connected over cellular connectivity
  • a UAV can be controlled by a UAV controller connected via the 3GPP mobile network
  • a UAV can be controlled by a UAV controller not connected via the 3GPP mobile network, using a C2 interface not in 3GPP scope
  • a UAV controller connected via the 3GPP mobile network can control one or more UAV(s)
  • the UAS exchanges application data traffic with a UTM
Up

$  Change historyWord‑p. 16

Up   Top