Tech-
invite
3GPP
space
IETF
space
◀
▶
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
TR 28.853
Study on Charging aspects of Uncrewed Aerial Systems
3GPP‑Page
fToC
↓
Partial Content
→
V19.1.0 (Wzip)
2025/06 22 p.
Rapporteur:
Miss Dong, Jia
China Mobile E-Commerce Co.
full Table of Contents for
TR 28.853
Word version: 19.1.0
each clause number in
'red'
refers to the equivalent title in the Partial Content
1
Scope
p. 7
2
References
p. 7
3
Definitions of terms, symbols and abbreviations
p. 8
3.1
Terms
p. 8
3.2
Symbols
p. 8
3.3
Abbreviations
p. 8
4
Background
p. 9
4.1
General
p. 9
4.2
Architecture for Support of Uncrewed Aerial Systems
p. 9
4.3
Business roles
p. 10
5
Charging scenarios and key issues
p. 10
5.1
Topic 1: Converged charging with UAV Information
p. 10
5.1.1
Use cases
p. 10
5.1.1.1
Use case #1a: Converged charging with UAV Information
p. 10
5.1.2
Potential charging requirements
p. 11
5.1.3
Key issues
p. 11
5.1.4
Possible solutions
p. 11
5.1.4.1
Solution #1.1: Data Connectivity Charging between SMF and CHF
p. 11
5.1.4.1.1
General description
p. 11
5.1.4.1.2
Procedures description
p. 11
5.1.4.2
Solution #1.2: Connection and Mobility Charging between AMF and CHF
p. 11
5.1.4.2.1
General description
p. 11
5.1.4.2.2
Procedures description
p. 12
5.1.4.3
Solution #1.3: Generic User Information to identify UAV
p. 12
5.1.4.3.1
General description
p. 12
5.1.5
Evaluation
p. 12
5.1.6
Conclusion
p. 13
5.2
Topic 2: Charging support of C2 Communication
p. 13
5.2.1
Use cases
p. 13
5.2.1.1
Use case #2a: Charging support of UTM-Navigated C2 Communication
p. 13
5.2.1.2
Use case #2b: Charging support of Direct C2 Communication
p. 13
5.2.2
Potential charging requirements
p. 13
5.2.3
Key issues
p. 13
5.2.4
Possible solutions
p. 14
5.2.4.1
Solution #2.1: C2 Communication over Uu reference point
p. 14
5.2.4.1.1
General description
p. 14
5.2.4.1.2
Architecture description
p. 14
5.2.4.1.3
Procedures description
p. 14
5.2.5
Evaluation
p. 14
5.2.6
Conclusion
p. 14
5.3
Topic 3: Service Exposure to the USS
p. 14
5.3.1
Use Case
p. 14
5.3.1.1
Use Case #3a: Service Exposure for UAV Tracking
p. 14
5.3.1.2
Use Case #3b: Service Exposure for QoS controlling
p. 15
5.3.2
Potential charging requirements
p. 15
5.3.3
Key issues
p. 15
5.3.3.1
Key issue #3a: Chargeable events and charging information required
p. 15
5.3.4
Solutions
p. 15
5.3.4.1
Solution #3.1: API invocation via UAS NF/NEF
p. 15
5.3.4.1.1
General description
p. 15
5.3.4.1.2
Architecture description
p. 15
5.3.4.1.3
Procedures description
p. 16
5.3.5
Evaluation
p. 17
5.3.5.1
Solutions evaluation for Key issue #3a
p. 17
5.3.6
Conclusion
p. 17
5.4
Topic 4: Aircraft-to-Everything (A2X) services for UAS Charging
p. 17
5.4.1
Use cases
p. 17
5.4.1.1
Use Case #4.1: AF-based service parameter provisioning for A2X communication
p. 17
5.4.1.2
Use Case #4.2: Non-roaming 5G System for A2X communication
p. 17
5.4.1.3
Use Case #4.3: Roaming 5G System architecture for A2X communication
p. 17
5.4.2
Potential charging requirements
p. 18
5.4.3
Key issues
p. 18
5.4.3.1
Key issue #4a: Charging information required for A2X service parameter provisioning
p. 18
5.4.3.2
Key issue #4b: Charging information required for non-roaming A2X communication
p. 18
5.4.3.3
Key issue #4c: Charging information required for roaming A2X communication
p. 18
5.4.4
Solutions
p. 19
5.4.4.1
Solution #4.1: Provisioning for A2X communication via UAS NF/NEF
p. 19
5.4.4.1.1
General description
p. 19
5.4.4.1.2
Architecture description
p. 19
5.4.4.1.3
Procedures description
p. 19
5.4.4.2
Solution #4.2: Non-roaming A2X Communication over Uu reference point
p. 19
5.4.4.2.1
General description
p. 19
5.4.4.2.2
Architecture description
p. 19
5.4.4.2.3
Procedures description
p. 19
5.4.4.3
Solution #4.3: Roaming A2X Communication over Uu reference point
p. 19
5.4.4.3.1
General description
p. 19
5.4.4.3.2
Architecture description
p. 20
5.4.4.3.3
Procedures description
p. 20
5.4.5
Evaluation
p. 20
5.4.5.1
Solutions evaluation for Key issue #4a
p. 20
5.4.5.2
Solutions evaluation for Key issue #4b
p. 20
5.4.5.3
Solutions evaluation for Key issue #4c
p. 20
5.4.6
Conclusion
p. 20
6
Conclusions and Recommendations
p. 20
$
Change history
p. 22