Tech-invite 3GPPspace IETFspace

21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

Content for TR 28.840 Word version: 18.1.0

1… 5…

5.1 Topic #1: CHF Selection by NF Consumers Information 5.2 Topic #2: CHF Selection based on SUPI or Group ID 5.3 Topic #3 CHF Selection by a Tenant or Application 5.4 Topic #4 CHF Discovery by Charging Domains

5 CHF Selection Scenarios and Key Issues p. 9

5.1 Topic #1: CHF Selection by NF Consumers Information p. 9

5.1.1 General description and assumptions p. 9

5.1.2 Potential charging requirements p. 10

5.1.3 Key issues#1.1: Charging events and charging information required p. 10

5.1.4 Possible Solutions p. 10

5.1.4.1 Solution #1.1 CHF Selection and Discovery for NF Service Consumers Solution based on UDM p. 10

5.1.4.2 Solution #1.2 CHF Selection by using CHF Default Instance Solution p. 12

5.1.4.3 Solution #1.3 CHF selection based on location p. 14

5.1.4.4 Solution #1.4: CHF selection based on NF instance p. 14

5.1.4.5 Solution #1.5: Using NRF locality information p. 15

5.1.4.6 Solution 1.6: NRF inferred CHF Group Id p. 15

5.1.4.7 Solution 1.7: SCP retrieved CHF Group Id p. 15

5.1.5 Evaluation p. 15

5.1.5.1 Solutions evaluation for Key issue #1.1 p. 15

5.1.6 Conclusion p. 16

5.2 Topic #2: CHF Selection based on SUPI or Group ID p. 16

5.2.1 General description and assumptions p. 16

5.2.2 Potential charging requirements p. 16

5.2.3 Key issues#2.1: CHF Instance Selection optimization p. 16

5.2.4 Possible Solutions p. 16

5.2.4.1 Solution #2.1 Location Optimization Solution p. 16

5.2.4.2 Solution #2.2 CHF selection based on user group p. 17

5.2.4.3 Solution #2.3: Use full set of NRF discovery p. 17

5.2.4.4 Solution #2.4 CHF selection based on internal group identifier p. 18

5.2.5 Evaluation p. 18

5.2.5.1 Solutions evaluation for Key issue #2.1 p. 18

5.2.6 Conclusion p. 18

5.3 Topic #3 CHF Selection by a Tenant or Application p. 18

5.3.1 General description and assumptions p. 18

5.3.2 Potential charging requirements p. 19

5.3.3 Key issues#3.1: CHF Instance Selection p. 19

5.3.4 Possible Solutions p. 19

5.3.4.1 Solution #3.1 Tenant Identifier Solution p. 19

5.3.4.2 Solution #3.2 Generic Identifier Solution p. 19

5.3.4.3 Solution #3.3: CHF selection based on S-NSSAI p. 19

5.3.4.4 Solution #3.4: CHF selection based on S-NSSAI and SUPI p. 20

5.3.5 Evaluation p. 20

5.3.5.1 Solutions evaluation for Key issue #3.1 p. 20

5.3.6 Conclusion p. 20

5.4 Topic #4 CHF Discovery by Charging Domains p. 20

5.4.1 General description and assumptions p. 20

5.4.2 Potential charging requirements p. 21

5.4.3 Key Issues p. 21

5.4.4 Possible Solutions p. 21

5.4.4.1 Solution #4.1: Use NF type and Inter-CHF communication p. 21

5.4.4.2 Solution #4.2: Update Priority for CHF Selection p. 21

5.4.4.3 Solution #4.3: Use enumeration to identify charging domain or subsystem p. 21

5.4.4.4 Solution #4.4: Use NRF to discover CHF by charging domain p. 23

5.4.4.5 Solution #4.5: Specify Charging Domain in Nchf Converged Charging SBI p. 24

5.4.4.6 Solution #4.6: Custom HTTP2 Header For Charging p. 24

5.4.4.7 Solution #4.7: Use NF type and SCP p. 25

5.4.4.8 Solution #4.8: Use NF type and CHF redirect p. 25

5.4.4.9 Solution #4.9: A logical separation of charging domains p. 25

5.4.4.10 Solution #4.10: Use Supported Features p. 26

5.4.4.11 Solution #4.11: Use 3gpp-Sbi-Consumer-Info for indicating domain support p. 26

5.4.5 Evaluation p. 26

5.4.5.1 Solutions evaluation for Topic #4 p. 26

5.4.6 Conclusion p. 27

5.4.6.1 Conclusion for Topic 4 p. 27

7 Conclusion p. 27

$ Change history p. 28