Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TR 28.827
Study on 5G Charging for additional Roaming Scenarios and Actors

3GPP‑Page  
V18.0.0 (Wzip)  2023/09  86 p.
Rapporteur:
Mr. Törnkvist, Robert
Ericsson LM

full Table of Contents for  TR 28.827  Word version:  18.0.0

Here   Top
1 Scope  2 References  3 Definitions of terms, symbols and abbreviations  4 Business roles  5 Concepts and overview  6 Architecture considerations  7 Charging scenarios and key issues  8 Conclusions and recommendations  $ Change history 

 

1  Scope  p. 10

The present document studies the potential use cases, requirements, and solutions for the 5G charging for additional roaming scenarios and actors, in regards to roaming local break out and home routed and taking the requirements brought by adoption of GSMA BCE (Billing Charging Evolution), as a replacement for TAP.
The study will cover and identify gaps for:
  • charging in the visited MNO network for the purpose of wholesale charging towards the home MNO
  • capabilities for reconciliation of wholesale charging reports from the visited MNO network with MNO home network information
  • charging in the visited MNO network and convey it to the home MNO network for the purpose of retail charging
  • charging in the MNO's network for the purpose of wholesale charging towards an additional charging model actor e.g. MVNO
  • charging in the visited MNO network and convey it to the home MNO's network for the purpose of home MNO wholesale charging towards an additional charging model actor e.g. MVNO
  • charging in the visited MNO network and convey it to an MVNO hosted by a home MNO for the purpose of retail charging
Up

2  References  p. 10

3  Definitions of terms, symbols and abbreviations  p. 11

3.1  Terms  p. 11

3.2  Symbols  p. 11

3.3  Abbreviations  p. 11

4  Business roles  p. 12

5  Concepts and overview  p. 12

5.1  General  p. 12

5.2  Home Routed  p. 12

5.3  Local Breakout  p. 12

5.4  Billing and Charging Evolution (BCE)  p. 13

6  Architecture considerations  p. 13

6.1  Non-roaming reference architecture  p. 13

6.2  Roaming reference architecture  p. 13

7  Charging scenarios and key issues  p. 14

7.1  Charging in visited MNO for wholesale charging towards home MNO  p. 14

7.1.1  Use cases  p. 14

7.1.1.1  Use case #1a: Visited MNO charging home MNO for 5G data connectivity provided to the home MNO's subscribers  p. 14

7.1.1.2  Use case #1b: Visited MNO charging home MNO for 5G connection and mobility provided to the home MNO's CSCs  p. 15

7.1.1.3  Use case #1c: Visited MNO charging home MNO for SMS provided to the home MNO's subscribers  p. 15

7.1.2  Potential charging requirements  p. 15

7.1.3  Key issues  p. 15

7.1.4  Potential solutions  p. 16

7.1.4.1  Solution #1.1: CDR in VPLMN for wholesale of 5G data connectivity  p. 16

7.1.4.1.1  General  p. 16
7.1.4.1.2  Reference architecture  p. 16
7.1.4.1.3  Message flows  p. 17

7.1.4.2  Solution #1.2: CDR in VPLMN for wholesale of 5G connection and mobility  p. 17

7.1.4.2.1  General  p. 17
7.1.4.2.2  Reference architecture  p. 17
7.1.4.2.3  Message flows  p. 18

7.1.4.3  Solution #1.3: Nchf to VPLMN for wholesale of 5G data connectivity  p. 19

7.1.4.3.1  General  p. 19
7.1.4.3.2  Reference architecture  p. 19
7.1.4.3.3  Message flows  p. 19

7.1.4.4  Solution #1.4: Roaming Charging Profile update  p. 21

7.1.4.4.1  General  p. 21
7.1.4.4.2  Reference architecture  p. 21
7.1.4.4.3  Message flows  p. 21

7.1.4.5  Solution #1.5: CDR in VPLMN for wholesale of SMS  p. 22

7.1.4.5.1  General  p. 22
7.1.4.5.2  Reference architecture  p. 22
7.1.4.5.3  Message flows  p. 23

7.1.4.6  Solution #1.6: Nchf to VPLMN for wholesale of 5G connection and mobility  p. 24

7.1.4.6.1  General  p. 24
7.1.4.6.2  Reference architecture  p. 25
7.1.4.6.3  Message flows  p. 25

7.1.4.7  Solution #1.7: Roaming charging trigger preconfigured in VPLMN based on negotiation with HPLMN  p. 25

7.1.4.7.1  General  p. 25
7.1.4.7.2  Reference architecture  p. 25
7.1.4.7.3  Message flows  p. 25

7.1.4.8  Solution #1.8: Only QBC trigger negotiation towards the V-CHF  p. 26

7.1.4.8.1  General  p. 26
7.1.4.8.2  Reference architecture  p. 26
7.1.4.8.3  Message flows  p. 26

7.1.4.9  Solution #1.9: V-SMF connects to V-CHF with two charging sessions  p. 26

7.1.4.9.1  General  p. 26
7.1.4.9.2  Reference architecture  p. 26
7.1.4.9.3  Message flows  p. 26

7.1.4.10  Solution #1.10: Separate QBC and FBC PDU session level triggers  p. 28

7.1.4.10.1  General  p. 28
7.1.4.10.2  Reference architecture  p. 28
7.1.4.10.3  Message flows  p. 28

7.1.4.11  Solution #1.11: QBC triggers common for all QoS flows  p. 28

7.1.4.11.1  General  p. 28
7.1.4.11.2  Reference architecture  p. 28
7.1.4.11.3  Message flows  p. 29

7.1.4.12  Solution #1.12: QBC and FBC common PDU session level triggers  p. 29

7.1.4.12.1  General  p. 29
7.1.4.12.2  Reference architecture  p. 29
7.1.4.12.3  Message flows  p. 29

7.1.5  Evaluation  p. 29

7.1.6  Conclusion  p. 30

7.2  Convey charging information from visited MNO to home MNO  p. 31

7.2.1  Use cases  p. 31

7.2.1.1  Use case #2a: Home MNO charging subscriber for 5G data connectivity at roaming using local breakout  p. 31

7.2.1.2  Use case #2b: Home MNO charging subscriber for 5G data connectivity at roaming using home routed  p. 31

7.2.1.3  Use case #2c: Home MNO charging subscriber for SMS provided at roaming  p. 31

7.2.1.4  Use case #2d: Home MNO charging subscriber for 5G connection and mobility provided to home MNO's subscribers in roaming scenario  p. 32

7.2.2  Potential charging requirements  p. 32

7.2.3  Key issues  p. 32

7.2.4  Potential solutions  p. 33

7.2.4.1  Solution #2.1: V-CHF communicating with H-CHF for retail charging of 5G, single charging session to V-CHF  p. 33

7.2.4.1.1  General  p. 33
7.2.4.1.2  Reference architecture  p. 33
7.2.4.1.3  Message flows  p. 35

7.2.4.2  Solution #2.2: Visited SMF (CTF) communicating with both H-CHF and V-CHF  p. 40

7.2.4.2.1  General  p. 40
7.2.4.2.2  Reference architecture  p. 40
7.2.4.2.3  Message flows  p. 41

7.2.4.3  Solution #2.3: V-CHF communicating with H-CHF for SMS charging reconciliation between MNOs  p. 41

7.2.4.4  Solution #2.4: Visited SMSF (CTF) communicating with both H-CHF and V-CHF  p. 41

7.2.4.4.1  General  p. 41
7.2.4.4.2  Reference architecture  p. 41
7.2.4.4.3  Message flows  p. 42

7.2.4.5  Solution #2.5: Visited AMF (CTF) communicating with both H-CHF and V-CHF  p. 43

7.2.4.5.1  General  p. 43
7.2.4.5.2  Reference architecture  p. 43
7.2.4.5.3  Message flows  p. 44

7.2.4.6  Solution #2.6: Reusing Nchf_ConvergedCharging service API between CHFs  p. 44

7.2.4.6.1  General  p. 44
7.2.4.6.2  Reference architecture  p. 44

7.2.4.7  Solution #2.7: New Nchf service API between CHFs  p. 44

7.2.4.7.1  General  p. 44
7.2.4.7.2  Reference architecture  p. 45

7.2.4.8  Solution #2.8: Using NRF to find H-CHF  p. 45

7.2.4.8.1  General  p. 45
7.2.4.8.2  Reference architecture  p. 45
7.2.4.8.3  Message flows  p. 45

7.2.4.9  Solution #2.9: Using SUPI to find H-CHF  p. 45

7.2.4.9.1  General  p. 45
7.2.4.9.2  Reference architecture  p. 45
7.2.4.9.3  Message flows  p. 45

7.2.4.10  Solution #2.10: Charging session between V-CHF and H-CHF per UE  p. 45

7.2.4.10.1  General  p. 45
7.2.4.10.2  Reference architecture  p. 45
7.2.4.10.3  Message flows  p. 45

7.2.4.11  Solution #2.11: Charging data message exchange between V-CHF and H-CHF per charging data request  p. 50

7.2.4.11.1  General  p. 50
7.2.4.11.2  Reference architecture  p. 50
7.2.4.11.3  Message flows  p. 50

7.2.4.12  Solution #2.12: Roaming charging profile update  p. 50

7.2.4.12.1  General  p. 50
7.2.4.12.2  Reference architecture  p. 50
7.2.4.12.3  Message flows  p. 50

7.2.4.13  Solution #2.13: V-CHF selected charging information for reporting to H-CHF  p. 51

7.2.4.13.1  General  p. 51
7.2.4.13.2  Reference architecture  p. 51
7.2.4.13.3  Message flows  p. 51

7.2.4.14  Solution #2.14: V-SMF selected charging information for reporting to H-CHF  p. 51

7.2.4.14.1  General  p. 51
7.2.4.14.2  Reference architecture  p. 51
7.2.4.14.3  Message flows  p. 51

7.2.4.15  Solution #2.15: V-SMF setting charging information indication by information element group  p. 52

7.2.4.15.1  General  p. 52
7.2.4.15.2  Reference architecture  p. 52
7.2.4.15.3  Message flows  p. 52

7.2.4.16  Solution #2.16: CDF and OCF communicating with SMS-SC for retail charging of SMS  p. 52

7.2.4.16.1  General  p. 52
7.2.4.16.2  Reference architecture  p. 52
7.1.4.16.3  Message flows  p. 53

7.2.4.17  Solution #2.17: configure the roaming charging profile update  p. 53

7.2.4.17.1  General  p. 53
7.2.4.17.2  Reference architecture  p. 53
7.2.4.17.3  Message flows  p. 54

7.2.4.18  Solution #2.18: Roaming charging profile update CHF-to-CHF  p. 54

7.2.4.18.1  General  p. 54
7.2.4.18.2  Reference architecture  p. 54
7.2.4.18.3  Message flows  p. 54

7.2.4.19  Solution #2.19: Charging session between V-CHF and H-CHF per charging session between NF and V-CHF  p. 55

7.2.4.19.1  General  p. 55
7.2.4.19.2  Reference architecture  p. 55
7.2.4.19.3  Message flows  p. 55

7.2.4.20  Solution #2.20: Charging message exchange between V-CHF and H-CHF based on quota management  p. 55

7.2.4.20.1  General  p. 55
7.2.4.20.2  Reference architecture  p. 55
7.2.4.20.3  Message flows  p. 56

7.2.5  Evaluation  p. 59

7.2.6  Conclusion  p. 61

7.3  Charging in an MNO for the purpose of wholesale charging towards an additional actor  p. 62

7.3.1  Use cases  p. 62

7.3.1.1  Use case #3a: MNO does wholesale charging for 5G data connectivity towards additional actors  p. 62

7.3.1.2  Use case #3b: MNO does wholesale charging for 5G connection and mobility towards additional actors  p. 62

7.3.1.3  Use case #3c: MNO does wholesale charging for 5G SMS towards additional actors  p. 62

7.3.2  Potential charging requirements  p. 62

7.3.3  Key issues  p. 63

7.3.4.1  Solution #3.1: CDR in home MNO for wholesale of non-roaming 5G of additional actor without CHF  p. 63

7.3.4.1.1  General  p. 63
7.3.4.1.2  Reference architecture  p. 63
7.3.4.1.3  Message flows  p. 64

7.3.4.2  Solution #3.2: CDR in home MNO for wholesale of non-roaming 5G of additional actor with CHF  p. 64

7.3.4.2.1  General  p. 64
7.3.4.2.2  Reference architecture  p. 64
7.3.4.2.3  Message flows  p. 64

7.3.5  Evaluation  p. 64

7.3.6  Conclusion  p. 65

7.4  Convey charging information from an MNO to an additional actor  p. 65

7.4.1  Use cases  p. 65

7.4.1.1  Use case #4a: Additional actor does retail charging for 5G data connectivity  p. 65

7.4.1.2  Use case #4b: Additional actor does retail billing for 5G data connectivity  p. 65

7.4.1.3  Use case #4c: Use case for additional actor does wholesale charging for 5G data connectivity towards another additional actor  p. 65

7.4.2  Potential charging requirements  p. 66

7.4.3  Key issues  p. 66

7.4.4  Potential solutions  p. 66

7.4.4.1  Solution #4.1: Home SMF (CTF) communicating with both H-CHF and A-CHF for retail charging of 5G data connectivity  p. 66

7.4.4.1.1  General  p. 66
7.4.4.1.2  Reference architecture  p. 67
7.4.4.1.3  Potential charging flows  p. 67

7.4.4.2  Solution #4.2: Additional actor only does retail billing of subscribers  p. 67

7.4.4.2.1  General  p. 67
7.4.4.2.2  Reference architecture  p. 68
7.4.4.2.3  Potential charging flows  p. 68

7.4.4.3  Solution #4.3: H-CHF communicating with A-CHF for retail charging of 5G  p. 68

7.4.4.3.1  General  p. 68
7.4.4.3.2  Reference architecture  p. 69
7.4.4.3.3  Message flows  p. 69

7.4.4.4  Solution #4.4: Reusing Nchf_ConvergedCharging service API between CHFs  p. 69

7.4.4.4.1  General  p. 69
7.4.4.4.2  Reference architecture  p. 70

7.4.4.5  Solution #4.5: New Nchf service API between CHFs  p. 70

7.4.4.5.1  General  p. 70
7.4.4.5.2  Reference architecture  p. 70

7.4.4.6  Solution #4.6: Using NRF to find A-CHF  p. 70

7.4.4.6.1  General  p. 70
7.4.4.6.2  Reference architecture  p. 70
7.4.4.6.3  Message flows  p. 70

7.4.4.7  Solution #4.7: Using local configuration to find A-CHF  p. 70

7.4.4.7.1  General  p. 70
7.4.4.7.2  Reference architecture  p. 70
7.4.4.7.3  Message flows  p. 70

7.4.4.8  Solution #4.8: Charging data request triggered CHF and A-CHF communication  p. 70

7.4.4.8.1  General  p. 70
7.4.4.8.2  Reference architecture  p. 71
7.4.4.8.3  Message flows  p. 71

7.4.5  Evaluation  p. 71

7.4.6  Conclusion  p. 71

7.5  Convey charging information from visited MNO to home MNO, and home MNO to an additional actor  p. 72

7.5.1  Use cases  p. 72

7.5.1.1  Use case #5a: Use case for additional actor does retail changing for 5G data connectivity while roaming  p. 72

7.5.2  Potential charging requirements  p. 72

7.5.3  Key issues  p. 72

7.5.4  Potential solutions  p. 73

7.5.4.1  Solution #5.1: CHF to CHF communication  p. 73

7.5.4.1.1  General  p. 73
7.5.4.1.2  Reference architecture  p. 73
7.5.4.1.3  Message flows  p. 73

7.5.4.2  Solution #5.2: SMF to multiple CHF communication  p. 74

7.5.4.2.1  General  p. 74
7.5.4.2.2  Reference architecture  p. 74
7.5.4.2.3  Message flows  p. 74

7.5.4.3  Solution #5.3: Using NRF to find H-CHF and A-CHF  p. 75

7.5.4.3.1  General  p. 75
7.5.4.3.2  Reference architecture  p. 75
7.5.4.3.3  Message flows  p. 75

7.5.4.4  Solution #5.4: Using SUPI to find H-CHF and local configuration to find A-CHF  p. 75

7.5.4.4.1  General  p. 75
7.5.4.4.2  Reference architecture  p. 75
7.5.4.4.3  Message flows  p. 75

7.5.4.5  Solution #5.5: Reusing Nchf_ConvergedCharging service API between CHFs  p. 75

7.5.4.5.1  General  p. 75

7.5.4.6  Solution #5.6: New Nchf service API between CHFs  p. 75

7.5.4.6.1  General  p. 75

7.5.4.7  Solution #5.7: Charging data request triggered V-CHF, H-CHF, and A-CHF communication  p. 75

7.5.4.7.1  General  p. 75
7.5.4.7.2  Reference architecture  p. 76
7.5.4.7.3  Message flows  p. 76

7.5.8.1  Solution #5.8: CHF to CHF communication between home MNO and additional actor  p. 76

7.5.8.1.1  General  p. 76
7.5.8.1.2  Reference architecture  p. 76
7.5.8.1.3  Message flows  p. 77

7.5.5  Evaluation  p. 77

7.5.6  Conclusion  p. 78

7.6  Reconciliation of wholesale charging from the visited MNO with home MNO information  p. 78

7.6.1  Use cases  p. 78

7.6.1.1  Use case #6a: support for validation of usage information received from visited MNO at the home MNO  p. 78

7.6.2  Potential charging requirements  p. 78

7.6.3  Key issues  p. 78

7.6.4  Potential solutions  p. 78

7.6.4.1  Solution #6.1: Use home routing  p. 78

7.6.4.1.1  General  p. 78

7.6.4.2  Solution #6.2: Using user reported usage information reporting  p. 79

7.6.4.2.1  General  p. 79
7.6.4.2.2  Reference architecture  p. 79
7.6.4.2.3  Potential message flows  p. 80

7.6.5  Evaluation  p. 81

7.6.6  Conclusion  p. 82

8  Conclusions and recommendations  p. 82

$  Change history  p. 83

Up   Top