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.849
Study on Charging aspects of Common API Framework for Northbound APIs (CAPIF) Phase 2

3GPP‑Page   fToC↓   Partial Content →
V19.1.0 (Wzip)  2025/06  44 p.
Rapporteur:
Mr. Rodrigues, João
Nokia

full Table of Contents for  TR 28.849  Word version:  19.1.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
1Scope  p. 8
2References  p. 8
3Definitions of terms, symbols and abbreviations  p. 8
3.1Terms  p. 8
3.2Symbols  p. 8
3.3Abbreviations  p. 9
4Void  p. …
5Concepts and background  p. 9
5.1General Description  p. 9
5.2Background  p. 10
5.2.1API Exposure  p. 10
5.3Business Roles related to CAPIF charging  p. 11
5.3.1Basic CAPIF business relationships  p. 11
5.3.2CAPIF business relationships for RNAA  p. 11
5.4Charging aspect requirements by SA6  p. 12
6CAPIF Charging Scenarios and Topics  p. 13
6.1Topic #1 CAPIF Converged Charging support of Service APIs Operation and Management  p. 13
6.1.1General description and assumptions  p. 13
6.1.2Use Case  p. 13
6.1.2.1Use Case #1.1: Service API Operation and management via CAPIF  p. 13
6.1.2.2Use Case #1.2: API invoker management via CAPIF  p. 13
6.1.2.3Use Case #1.3: Service API discovery via CAPIF  p. 14
6.1.3Potential charging requirements  p. 14
6.1.4Key issues  p. 14
6.1.4.1Key issue#1.1: Charging events and charging information required  p. 14
6.1.4.2Key issue#1.2: Charging events and charging information required  p. 14
6.1.4.3Key issue#1.3: Charging events and charging information required  p. 14
6.1.5Possible Solutions  p. 15
6.1.5.1Solution #1.1 API Service Management Charging  p. 15
6.1.5.1.0General  p. 15
6.1.5.1.1Service API Publish Invocation - IEC  p. 16
6.1.5.1.2Service API Publish Invocation - ECUR  p. 17
6.1.5.1.3Service API Notification Invocation - IEC  p. 18
6.1.5.1.4Service API Notification Invocation - ECUR  p. 19
6.1.5.1.5Service API Update - IEC  p. 20
6.1.5.1.6Service API Update - ECUR  p. 21
6.1.5.2Solution #1.2: Service API discovery via CAPIF  p. 22
6.1.5.2.1General description  p. 22
6.1.5.2.2Architecture description  p. 22
6.1.5.2.3Procedures description  p. 22
6.1.5.3Solution #1.3: API invoker management by via CAPIF  p. 24
6.1.5.3.1General description  p. 24
6.1.5.3.2Architecture description  p. 24
6.1.5.3.3Procedures description  p. 24
6.1.5.4Solution #1.4: Service API management via CAPIF  p. 25
6.1.5.4.1General description  p. 25
6.1.5.4.2Architecture description  p. 25
6.1.5.4.3Procedures description  p. 26
6.1.5.5Solution #1.5: Use of Exposure function Northbound Application Program Interfaces (APIs) charging  p. 26
6.1.5.5.1General description  p. 26
6.1.5.5.2Architecture description  p. 26
6.1.5.5.3Procedures description  p. 26
6.1.5.6Solution #1.6: Use of subscription based charging  p. 27
6.1.5.6.1General description  p. 27
6.1.6Evaluation  p. 27
6.1.6.1Solutions evaluation for Key issue #1.1  p. 27
6.1.6.2Solutions evaluation for Key issue #1.2  p. 27
6.1.6.3Solutions evaluation for Key issue #1.3  p. 27
6.1.7Conclusion  p. 28
6.2Topic #2 CAPIF Converged Charging of multiple API Providers  p. 28
6.2.1General description and assumptions  p. 28
6.2.2Use Case  p. 28
6.2.2.1Use Case #2.1: API Provider Converged Charging  p. 28
6.2.2.2Use Case #2.2: API Invoker Converged Charging  p. 28
6.2.3Potential charging requirements  p. 28
6.2.4Key issues  p. 29
6.2.4.1Key issue#2.1: Charging events and charging information required  p. 29
6.2.5Possible Solutions  p. 29
6.2.5.1Solution #2.1 Multiple API Provider Service Management Charging  p. 29
6.2.5.2Solution #2.2: Use of Exposure function Northbound Application Program Interfaces (APIs) charging  p. 30
6.2.5.2.1General description  p. 30
6.2.5.2.2Architecture description  p. 30
6.2.5.2.3Procedures description  p. 30
6.2.6Evaluation  p. 30
6.2.6.1Solutions evaluation for Key issue #2.1  p. 30
6.2.7Conclusion  p. 30
6.3Topic #3 API Service usage charging of CAPIF  p. 30
6.3.1General description and assumptions  p. 30
6.3.2Use Case  p. 31
6.3.2.1Use Case #3.1: API Service Usage via CAPIF  p. 31
6.3.3Potential charging requirements  p. 31
6.3.4Key issues  p. 31
6.3.4.1Key issue#3.1: Charging events and charging information required  p. 31
6.3.5Possible Solutions  p. 31
6.3.5.1Solution #3.1: API invocation via CAPIF  p. 31
6.3.5.1.1General description  p. 31
6.3.5.1.2Architecture description  p. 31
6.3.5.1.3Procedures description  p. 32
6.3.5.2Solution #3.2: Use of Exposure function Northbound Application Program Interfaces (APIs) charging  p. 32
6.3.5.2.1General description  p. 32
6.3.5.2.2Architecture description  p. 32
6.3.5.2.3Procedures description  p. 33
6.3.5.3Solution #3.3: CAPIF APIs charging  p. 33
6.3.5.3.1General description  p. 33
6.3.5.3.2Architecture description  p. 33
6.3.5.3.3Procedures description  p. 34
6.3.6Evaluation  p. 37
6.3.6.1Solutions evaluation for Key issue #3.1  p. 37
6.3.7Conclusion  p. 37
6.4Topic #4 CAPIF Converged Charging of NEF API  p. 37
6.4.1General description and assumptions  p. 37
6.4.2Use Case  p. 37
6.4.2.1Use Case #4.1: API Provider Converged Charging  p. 37
6.4.3Potential charging requirements  p. 38
6.4.4Key issues  p. 38
6.4.4.1Key issues#4.1: Charging events and charging information required  p. 38
6.4.5Possible Solutions  p. 38
6.4.5.1Solution #4.1 CAPIF Converged Charging of NEF API  p. 38
6.4.5.2Solution #4.Y CAPIF Converged Charging when NEF implement the API provider domain  p. 40
6.4.5.2.1General description  p. 40
6.4.5.2.2Architecture description  p. 41
6.4.5.2.3Procedures description  p. 42
6.4.6Evaluation  p. 42
6.4.6.1Solutions evaluation for Key issue #4.1  p. 42
6.4.7Conclusion  p. 43
7Evaluation  p. 43
8Conclusion  p. 43
$Change history  p. 44

Up   Top