Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TR 28.853
Study on Charging aspects of Uncrewed Aerial Systems

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
Here   Top
1Scope  p. 7
2References  p. 7
3Definitions of terms, symbols and abbreviations  p. 8
3.1Terms  p. 8
3.2Symbols  p. 8
3.3Abbreviations  p. 8
4Background  p. 9
4.1General  p. 9
4.2Architecture for Support of Uncrewed Aerial Systems  p. 9
4.3Business roles  p. 10
5Charging scenarios and key issues  p. 10
5.1Topic 1: Converged charging with UAV Information  p. 10
5.1.1Use cases  p. 10
5.1.1.1Use case #1a: Converged charging with UAV Information  p. 10
5.1.2Potential charging requirements  p. 11
5.1.3Key issues  p. 11
5.1.4Possible solutions  p. 11
5.1.4.1Solution #1.1: Data Connectivity Charging between SMF and CHF  p. 11
5.1.4.1.1General description  p. 11
5.1.4.1.2Procedures description  p. 11
5.1.4.2Solution #1.2: Connection and Mobility Charging between AMF and CHF  p. 11
5.1.4.2.1General description  p. 11
5.1.4.2.2Procedures description  p. 12
5.1.4.3Solution #1.3: Generic User Information to identify UAV  p. 12
5.1.4.3.1General description  p. 12
5.1.5Evaluation  p. 12
5.1.6Conclusion  p. 13
5.2Topic 2: Charging support of C2 Communication  p. 13
5.2.1Use cases  p. 13
5.2.1.1Use case #2a: Charging support of UTM-Navigated C2 Communication  p. 13
5.2.1.2Use case #2b: Charging support of Direct C2 Communication  p. 13
5.2.2Potential charging requirements  p. 13
5.2.3Key issues  p. 13
5.2.4Possible solutions  p. 14
5.2.4.1Solution #2.1: C2 Communication over Uu reference point  p. 14
5.2.4.1.1General description  p. 14
5.2.4.1.2Architecture description  p. 14
5.2.4.1.3Procedures description  p. 14
5.2.5Evaluation  p. 14
5.2.6Conclusion  p. 14
5.3Topic 3: Service Exposure to the USS  p. 14
5.3.1Use Case  p. 14
5.3.1.1Use Case #3a: Service Exposure for UAV Tracking  p. 14
5.3.1.2Use Case #3b: Service Exposure for QoS controlling  p. 15
5.3.2Potential charging requirements  p. 15
5.3.3Key issues  p. 15
5.3.3.1Key issue #3a: Chargeable events and charging information required  p. 15
5.3.4Solutions  p. 15
5.3.4.1Solution #3.1: API invocation via UAS NF/NEF  p. 15
5.3.4.1.1General description  p. 15
5.3.4.1.2Architecture description  p. 15
5.3.4.1.3Procedures description  p. 16
5.3.5Evaluation  p. 17
5.3.5.1Solutions evaluation for Key issue #3a  p. 17
5.3.6Conclusion  p. 17
5.4Topic 4: Aircraft-to-Everything (A2X) services for UAS Charging  p. 17
5.4.1Use cases  p. 17
5.4.1.1Use Case #4.1: AF-based service parameter provisioning for A2X communication  p. 17
5.4.1.2Use Case #4.2: Non-roaming 5G System for A2X communication  p. 17
5.4.1.3Use Case #4.3: Roaming 5G System architecture for A2X communication  p. 17
5.4.2Potential charging requirements  p. 18
5.4.3Key issues  p. 18
5.4.3.1Key issue #4a: Charging information required for A2X service parameter provisioning  p. 18
5.4.3.2Key issue #4b: Charging information required for non-roaming A2X communication  p. 18
5.4.3.3Key issue #4c: Charging information required for roaming A2X communication  p. 18
5.4.4Solutions  p. 19
5.4.4.1Solution #4.1: Provisioning for A2X communication via UAS NF/NEF  p. 19
5.4.4.1.1General description  p. 19
5.4.4.1.2Architecture description  p. 19
5.4.4.1.3Procedures description  p. 19
5.4.4.2Solution #4.2: Non-roaming A2X Communication over Uu reference point  p. 19
5.4.4.2.1General description  p. 19
5.4.4.2.2Architecture description  p. 19
5.4.4.2.3Procedures description  p. 19
5.4.4.3Solution #4.3: Roaming A2X Communication over Uu reference point  p. 19
5.4.4.3.1General description  p. 19
5.4.4.3.2Architecture description  p. 20
5.4.4.3.3Procedures description  p. 20
5.4.5Evaluation  p. 20
5.4.5.1Solutions evaluation for Key issue #4a  p. 20
5.4.5.2Solutions evaluation for Key issue #4b  p. 20
5.4.5.3Solutions evaluation for Key issue #4c  p. 20
5.4.6Conclusion  p. 20
6Conclusions and Recommendations  p. 20
$Change history  p. 22

Up   Top