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.871
Study on Service Based Management Architecture enhancement - Phase 3

3GPP‑Page   fToC↓   Partial Content →
V19.0.0 (Wzip)  2024/12  45 p.
Rapporteur:
Mr. Groenendijk, Jan
Ericsson LM

full Table of Contents for  TR 28.871  Word version:  19.0.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
0Introduction  p. 7
1Scope  p. 8
2References  p. 8
3Definitions of terms, symbols and abbreviations  p. 10
3.1Terms  p. 10
3.2Symbols  p. 10
3.3Abbreviations  p. 10
4Concepts and background  p. 10
4.1Service Based Management Architecture  p. 10
4.2Naming an MnS supporting a specific set of capabilities  p. 10
5Use cases and potential requirements  p. 11
5.1NRM investigation  p. 11
5.1.1Description  p. 11
5.1.2Potential requirement  p. 11
5.1.3Potential solutions  p. 11
5.2Connection between 3GPP TS 28.537 and 3GPP TS 28.622 for generic control NRM capabilities  p. 12
5.2.1Description  p. 12
5.2.2Potential requirements  p. 13
5.2.3Potential solutions  p. 13
5.2.3.0General  p. 13
5.2.3.1Potential solution#1 Add reference for solution description (NRM fragment) for each management capability in TS 28.537.  p. 13
5.2.3.2Potential solution#2 Add reference for management capability description for each NRM fragment in 3GPP TS 28.622  p. 13
5.2.3.3Potential solution#3 Add reference for management capability requirements for each NRM fragment in 3GPP TS 28.622  p. 13
5.2.4Evaluation of potential solutions  p. 14
5.3Discovery of management capabilities of MnS supported by a MnS Producer  p. 14
5.3.1Description  p. 14
5.3.2Potential requirements  p. 15
5.3.3Potential solutions  p. 15
5.3.4Evaluation of potential solutions  p. 19
5.4<<Support IOCs>> instances in SBMA  p. 19
5.4.1Description  p. 19
5.4.2Potential requirements  p. 20
5.4.3Potential solutions  p. 20
5.4.4Evaluation of potential solutions  p. 20
5.5Discovery of management capabilities of MnS instances based on area of interest  p. 20
5.5.1Description  p. 20
5.5.2Potential requirements  p. 20
5.5.3Potential solutions  p. 20
5.5.4Evaluation of potential solutions  p. 20
5.6PM investigation  p. 21
5.6.1Description  p. 21
5.6.2Potential requirement  p. 21
5.6.3Potential solutions  p. 21
5.7Common Notification Header  p. 24
5.7.1Description  p. 24
5.7.2Potential requirements  p. 25
5.7.3Potential solutions  p. 25
5.7.3.1Potential solution#1 Add definition of the common notification header to 3GPP TS 28.532  p. 25
5.7.4Evaluation of potential solutions  p. 25
5.8Schema retrieval enhancements  p. 26
5.8.1Description  p. 26
5.8.2Potential requirements  p. 26
5.8.3Potential solutions  p. 26
5.8.3.1Potential solution#1, Schema list at known location  p. 26
5.8.3.2Potential solution#2 Schema lists as capabilities  p. 26
5.8.3.3Potential solution#3 Solution set specific solutions  p. 27
5.8.4Evaluation of potential solutions  p. 27
5.9Schema reference enhancements  p. 27
5.9.1Description  p. 27
5.9.2Potential requirements  p. 27
5.9.3Potential solutions  p. 27
5.9.3.1Potential solution#1, Update ProvMnS OpenAPI definition to be more generic  p. 27
5.9.3.2Potential solution#2, decouples the ProvMnS schema and supported feature schema  p. 28
5.9.4Evaluation of potential solutions  p. 30
5.10List and handle Alarming-Conditions  p. 30
5.10.1Description  p. 30
5.10.2Potential requirements  p. 30
5.10.3Potential solutions  p. 30
5.10.3.1Potential solution #part1: List of alarming-conditions  p. 30
5.10.3.2Potential solution #part2: Filtering on alarming condition  p. 31
5.10.4Evaluation of potential solutions  p. 31
5.11Overview of management capabilities and corresponding Solution Sets  p. 31
5.11.1Description  p. 31
5.11.2Potential solutions  p. 31
5.11.3Evaluation of potential solutions  p. 33
5.12MnS Version Number Handling  p. 33
5.12.1Description  p. 33
5.12.2Potential requirements  p. 33
5.12.3Potential solutions  p. 34
5.12.3.1Potential solution#1 MnS Version scheme based on semver.  p. 34
5.12.4Evaluation of potential solutions  p. 34
5.13Reliable notification transfer  p. 34
5.13.1Description  p. 34
5.13.2Potential requirement  p. 35
5.13.3Potential solutions  p. 35
5.13.3.1Part#1 Add sequence number (REQ-rel-notif-1)  p. 35
5.13.3.2Part#2 Retrieve stored notifications (REQ-rel-notif-2 & 3)  p. 36
5.13.3.3Part#3 Notification could not be sent/prepared (REQ-rel-notif-4)  p. 36
5.13.3.3.1Problem Scenario  p. 36
5.13.3.3.2Part#3a notifyNotificationNotSent  p. 37
5.13.3.3.3Part#3b state variables on the NtfSubsciptionControl  p. 37
5.13.3.3.4Part#3c Alarm from NtfSubsciptionControl  p. 37
5.13.4Evaluation of potential solutions  p. 37
5.14Usage of MnS Registry NRM fragment for MnS Registry and Discovery for different deployment scenarios  p. 37
5.14.1Description  p. 37
5.14.2Potential solutions  p. 38
5.14.3Evaluation of potential solutions  p. 39
5.15Decouple the management and resource models  p. 39
5.15.1Description  p. 39
6Conclusions and recommendations  p. 40
6.1NRM investigation  p. 40
6.2Connection between 3GPP TS 28.537 and 3GPP TS 28.622 for generic control NRM capabilities  p. 40
6.3Discovery of management capabilities of MnS instances based on area of interest  p. 41
6.4PM investigation  p. 41
6.5<<Support IOCs>> instances in SBMA  p. 41
6.6Schema reference enhancements  p. 41
6.7Overview of management capabilities and corresponding Solution Sets  p. 41
6.8Discovery of management capabilities of MnS instance supported by a MnS Producer  p. 41
6.9Usage of MnS Registry NRM fragment for MnS Registry and Discovery for different deployment scenarios  p. 42
6.10Listing and handling of Alarming-Conditions  p. 42
6.11Reliable notification transfer  p. 42
6.12MnS Version Number Handling  p. 42
6.13Common Notification Header  p. 42
$Change history  p. 43

Up   Top