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