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.879
Study on OAM for service management and exposure to external consumers

3GPP‑Page   fToC↓   Partial Content →
V19.1.0 (Wzip)  2025/03  38 p.
Rapporteur:
Ms. Srinivasaraju, Srilakshmi
Nokia Corporation

full Table of Contents for  TR 28.879  Word version:  19.1.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
0Introduction  p. 6
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
4Concepts and Background  p. 9
4.1Exposure of management services  p. 9
4.1.1Overview  p. 9
4.1.2Background of existing SA5 solutions related to exposure  p. 10
4.1.3Background on existing telco exposure initiatives  p. 10
4.1.3.13GPP exposure framework  p. 10
4.1.3.2GSMA Open Gateway  p. 13
4.1.4Examples of external MnS consumers  p. 14
5Use Cases  p. 15
5.1Exposure of management services  p. 15
5.1.0Exposure of management services through the CAPIF framework  p. 15
5.1.0.1Description  p. 15
5.1.0.2Potential requirements  p. 16
5.1.1Use case #1: API provider domain registration into CAPIF  p. 17
5.1.1.1Description  p. 17
5.1.1.2Potential requirements  p. 17
5.1.1.3Potential solutions  p. 17
5.1.1.3.0Potential solution #1: MSED is the API provider domain for management services  p. 17
5.1.1.3.1Potential solution #2: Map MSED information into APIProviderEnrolmentDetails  p. 18
5.1.1.4Evaluation of potential solutions  p. 19
5.1.1.4.0Evaluation of potential solution #1: MSED is the API provider domain for management services  p. 19
5.1.1.4.1Evaluation of potential solution #2: Capturing MSED registration information with APIProviderEnrolmentDetails  p. 19
5.1.2Use case #2: Publishing of management services to the CCF  p. 20
5.1.2.1Description  p. 20
5.1.2.2Potential requirements  p. 20
5.1.2.3Potential solutions  p. 20
5.1.2.3.1Potential solution #1: Mapping of management service information into service API information  p. 20
5.1.2.3.2Potential solution #2: Mapping MnS API URI to Service API URI.  p. 23
5.1.2.3.3Potential solution #3: MSED providing the APF functionality  p. 24
5.1.2.4Evaluation of potential solutions  p. 24
5.1.2.4.1Evaluation of potential solution #1  p. 24
5.1.2.4.2Evaluation of potential solution #2  p. 24
5.1.2.4.3Evaluation of potential solution #3  p. 24
5.1.3Use case #3: Configuring discovery policy information for an external MnS consumer  p. 25
5.1.3.1Description  p. 25
5.1.3.2Potential requirements  p. 25
5.1.3.3Potential solutions  p. 25
5.1.3.4Evaluation of potential solutions  p. 25
5.1.4Use case #4: Authorization of the external MnS consumer to access the management service API  p. 26
5.1.4.1Description  p. 26
5.1.4.2Potential requirements  p. 26
5.1.4.3Potential solutions  p. 26
5.1.4.3.1Potential solution #1: Using Identity class to define the authorization information of an external MnS consumer  p. 26
5.1.4.3.2Potential solution #2: Identity class made available to the CCF  p. 27
5.1.4.4Evaluation of potential solutions  p. 30
5.1.4.4.1Evaluation of potential solution #1  p. 30
5.1.4.4.2Evaluation of potential solution #2  p. 30
5.1.5Use case #5: Logging the management service API invocations to the CCF  p. 31
5.1.5.1Description  p. 31
5.1.5.2Potential requirements  p. 31
5.1.5.3Potential solutions  p. 31
5.1.5.3.1Potential solution #1: Creation and logging of the management service API invocations  p. 31
5.1.5.4Evaluation of potential solutions  p. 33
6Conclusions and recommendations  p. 33
6.1Conclusions  p. 33
6.1.0General  p. 33
6.1.1Use case #1: API provider domain registration into CAPIF  p. 33
6.1.2Use case #2: Publishing of management services to the CCF  p. 34
6.1.3Use case #3: Configuring discovery policy information for an external MnS consumer  p. 34
6.1.4Use case #4: Authorization of the external MnS consumer to access the management service API  p. 34
6.1.5Use case #5: Logging the management service API  p. 34
6.2Recommendations  p. 34
A3GPP management capabilities  p. 36
$Change history  p. 38

Up   Top