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

TR 28.851
Study on Charging aspects of Next Generation Real Time Communication services Phase 2

V19.1.0 (Wzip)  2025/06  22 p.
Rapporteur:
Dr. Chen, Ai
China Mobile Com. Corporation

full Table of Contents for  TR 28.851  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
4Overview  p. 8
4.1General  p. 8
4.2Networks functionality and architecture of IMS data channel  p. 8
4.3Data channel application download  p. 9
4.4Avatar communication  p. 10
5Charging scenarios and key issues  p. 11
5.1Topic 1: Support of standalone IMS Data Channel sessions  p. 11
5.1.1Use cases  p. 11
5.1.1.1Use case #1a: Establishment and modification of standalone IMS Data Channel sessions  p. 11
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: Duration-based charging for standalone IMS Data Channel  p. 11
5.1.4.1.1General  p. 11
5.1.4.1.2Description  p. 12
5.1.4.2Solution #1.2: Volume-based charging for standalone IMS Data Channel  p. 12
5.1.4.2.1General  p. 12
5.1.4.2.2Description  p. 12
5.1.5Evaluation  p. 12
5.1.6Conclusion  p. 12
5.2Topic 2: charging for DC application download and usage  p. 13
5.2.1Use cases  p. 13
5.2.1.1Use case #2a: Download application via bootstrap data channel  p. 13
5.2.1.2Use case #2b: Using application via application data channel in P2A and P2A2P scenarios  p. 13
5.2.2Potential charging requirements  p. 13
5.2.3Key issues  p. 14
5.2.4Possible solutions  p. 14
5.2.4.1Solution #2.1: DC application download charging by event  p. 14
5.2.4.1.1General  p. 14
5.2.4.1.2Description  p. 14
5.2.4.2Solution #2.2: DC application usage charging by duration  p. 15
5.2.4.2.1General  p. 15
5.2.4.2.2Description  p. 15
5.2.4.3Solution #2.3: DC application usage charging by data volume per IMS session  p. 16
5.2.4.3.1General  p. 16
5.2.4.3.2Description  p. 16
5.2.4.4Solution #2.4: DC application download charging by reporting volume per bootstrap DC  p. 16
5.2.4.4.1General  p. 16
5.2.4.4.2Description  p. 16
5.2.4.5Solution #2.5: DC application usage charging by volume per application DC  p. 16
5.2.4.5.1General  p. 16
5.2.4.5.2Description  p. 16
5.2.5Evaluation  p. 17
5.2.6Conclusion  p. 17
5.3Topic 3: Support IMS network capabilities exposure  p. 17
5.3.1Use cases  p. 17
5.3.1.1Use case #3a: IMS network capabilities exposure to an external NF/AF  p. 17
5.3.2Potential charging requirements  p. 18
5.3.3Key issues  p. 18
5.3.4Possible solutions  p. 18
5.3.4.1Solution #3.1: Reuse of Northbound API converged charging  p. 18
5.3.4.1.1General  p. 18
5.3.4.1.2Description  p. 18
5.3.5Evaluation  p. 18
5.3.6Conclusion  p. 18
5.4Topic 4: Support IMS Data Channel as a PS Data Off Exempt Service  p. 19
5.4.1Use cases  p. 19
5.4.1.1Use case #4a: Services over IMS Data Channel is configured as a PS Data Off Exempted Service  p. 19
5.4.2Potential charging requirements  p. 19
5.4.3Key issues  p. 19
5.4.4Possible solutions  p. 19
5.4.4.1Solution #4.1: Reuse of 3GPP PS Data Off Status  p. 19
5.4.4.1.1General  p. 19
5.4.4.1.2Description  p. 19
5.4.5Evaluation  p. 19
5.4.6Conclusion  p. 19
5.5Topic 5: Support of Avatar communication  p. 20
5.5.1Use cases  p. 20
5.5.1.1Use case #5a: Network centric IMS Avatar communication  p. 20
5.5.2Potential charging requirements  p. 20
5.5.3Key issues  p. 20
5.5.4Possible solutions  p. 20
5.5.4.1Solution #5.1: IMS AS based charging solution for Avatar communication  p. 20
5.5.4.1.1General  p. 20
5.5.4.1.2Description  p. 21
5.5.5Evaluation  p. 21
5.5.6Conclusion  p. 21
6Conclusions and recommendations  p. 21
$Change history  p. 22

Up   Top