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.867
Study on Closed Control Loop management

3GPP‑Page   fToC↓   Partial Content →
V19.0.0 (Wzip)  2024/12  84 p.
Rapporteur:
Dr. Mwanje, Stephen
Nokia

full Table of Contents for  TR 28.867  Word version:  19.0.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
1Scope  p. 9
2References  p. 9
3Definitions of terms, symbols and abbreviations  p. 9
3.1Terms  p. 9
3.2Symbols  p. 9
3.3Abbreviations  p. 10
4Concepts and Background  p. 10
4.1Introduction and Overview  p. 10
4.1.1Closed Control loops  p. 10
4.1.2Functional stages of a closed control loop  p. 11
4.2Realizations of Closed Control Loops  p. 12
4.2.1Closed-Box Closed Control Loops - SON Functions as CCLs  p. 12
4.2.2Open-Box Closed Control Loops  p. 12
4.3Closed Control Loop conflicts management  p. 13
4.3.1CCL conflict scenarios  p. 13
4.4Management Service for Closed control Loops  p. 13
4.4.1Overview  p. 13
4.4.2Closed Control Loop Management Capabilities  p. 13
4.5Closed control loop as enabler for Intent handling  p. 14
5Use Cases  p. 15
5.1Use case 1: Dynamic CCL Creation  p. 15
5.1.1Description  p. 15
5.1.1.1Overview  p. 15
5.1.1.2Dynamic composition of CCLs  p. 15
5.1.1.3Examples for scenarios for Dynamic composition of CCLs  p. 15
5.1.1.3.1Composition from management Functions  p. 15
5.1.1.3.2Composition from management services  p. 16
5.1.2Potential Requirements  p. 16
5.1.3Potential Solutions  p. 16
5.1.4Evaluation of solutions  p. 17
5.2Use case 2: Triggered CCL  p. 18
5.2.1Description  p. 18
5.2.1.1Overview  p. 18
5.2.1.2Conditional instantiation of a CCL  p. 18
5.2.1.3Conditional execution of CCLs network changes  p. 18
5.2.2Potential Requirements  p. 18
5.2.3Potential solutions  p. 19
5.2.3.1Overview of LoopTrigger object  p. 19
5.2.3.2Information to be present in LoopTrigger object  p. 19
5.2.3.3Usage of ConditionMonitor to realize LoopTrigger object  p. 19
5.2.3.4Expressing trigger conditions using existing SA5 defined mechanisms  p. 20
5.2.3.4.1Introduction  p. 20
5.2.3.4.2Conditions based on performance metrics  p. 21
5.2.3.4.3Conditions based on Trace metrics  p. 22
5.2.3.4.4Conditions based on data node tree changes  p. 23
5.2.3.5Potential solution for Conditional execution of CCLs network changes  p. 24
5.2.4Evaluation of solutions  p. 24
5.3Use case 3: CCL creation based on Historical CCL data  p. 25
5.3.1Description  p. 25
5.3.2Potential Requirements  p. 25
5.3.3Potential Solution  p. 25
5.3.4Evaluation of solutions  p. 27
5.4Use case 4: closed control loop for problem recovery  p. 27
5.4.1Description  p. 27
5.4.2Potential requirements  p. 28
5.4.3Potential solutions  p. 28
5.4.4Evaluation of potential solutions  p. 29
5.5Use case 5: CCL for fault management  p. 29
5.5.1Description  p. 29
5.5.2Potential Requirements  p. 29
5.5.3Potential Solutions  p. 29
5.5.3.1Closed Control Loop for Fault Management  p. 29
5.5.4Evaluation of solutions  p. 30
5.6Use case 6: CCL conflicts management  p. 30
5.6.1Description  p. 30
5.6.1.1CCL Conflicts  p. 30
5.6.1.2CCL conflicts management and coordination interactions  p. 31
5.6.1.3CCL conflicts resolution  p. 32
5.6.1.3.1CCL Goal-conflicts resolution  p. 32
5.6.1.3.2CCL Trigger-time conflicts resolution  p. 33
5.6.2Potential Requirements  p. 33
5.6.3Potential Solutions  p. 33
5.6.3.1Alternative CCL coordination Approaches  p. 33
5.6.3.2General solution  p. 35
5.6.3.3Goal targets coordination  p. 37
5.6.3.3.1Required capabilities and interactions  p. 37
5.6.3.3.2Information objects to realize required capabilities and interactions  p. 38
5.6.3.4Direct actions conflicts  p. 39
5.6.3.4.1Detection and avoidance of actions conflicts  p. 39
5.6.3.4.2Detecting actual conflicts based on counter-productiveness  p. 40
5.6.3.4.3Bargaining as resolution of potential direct actions conflicts  p. 43
5.6.3.5Indirect targets conflicts  p. 45
5.6.3.5.1Detecting potential and actual indirect targets conflicts  p. 45
5.6.3.5.2Avoiding indirect targets conflicts  p. 46
5.6.3.5.3Avoiding potential indirect target conflicts through likely-impact of planned actions  p. 46
5.6.3.6Action-execution-time conflict coordination  p. 48
5.6.3.6.1Detection of potential action-execution-time conflicts  p. 48
5.6.3.6.1.1Required capabilities and interactions for detecting Action-execution-time conflicts  p. 48
5.6.3.6.1.2Information objects to realize required capabilities and interactions  p. 50
5.6.3.6.2Avoidance of action-execution-time conflicts  p. 51
5.6.3.6.2.1Required capabilities and interactions.  p. 51
5.6.3.6.2.2Information objects to realize required capabilities and interactions  p. 52
5.6.3.7Potential options for implementing the CCL coordination entity  p. 52
5.6.3.7.1Solution for CCL co-ordination entity as a CCL using recurrence  p. 52
5.6.4Evaluation of solutions  p. 54
5.7Use case 7: CCL scope management  p. 54
5.7.1Description  p. 54
5.7.2Potential Requirements  p. 55
5.7.3Potential Solutions  p. 55
5.7.3.1Required capabilities and interactions  p. 55
5.7.3.2Information objects to realize required capabilities and interactions  p. 56
5.7.4Evaluation of solutions  p. 57
5.8Use case 8: CCL-impact assessment and resolution  p. 57
5.8.1Description  p. 57
5.8.1.1Overview  p. 57
5.8.1.2 impact on known/bounded impact-scope  p. 58
5.8.1.3impact on unknown impact-scope  p. 58
5.8.2Potential Requirements  p. 58
5.8.3Potential Solutions  p. 59
5.8.3.1Solution for detection of actual indirect targets conflicts via impact on unknown or unbounded impact-scope  p. 59
5.8.3.1.1Required capabilities and interactions  p. 59
5.8.3.1.2Information objects to realize required capabilities and interactions  p. 60
5.8.4Evaluation of solutions  p. 60
5.9Consumers feedback on CCL actions  p. 61
5.9.1Description  p. 61
5.9.2Potential Requirements  p. 61
5.9.3  p. …
5.9.4Evaluation of solutions  p. 63
5.10CCL decision escalation  p. 63
5.10.1Description  p. 63
5.10.2Potential requirements  p. 63
5.10.3Possible solutions  p. 64
5.10.4Evaluation of solutions  p. 65
5.11Use case 11: Performance Evaluation of a Closed Control Loop  p. 65
5.11.1Description  p. 65
5.11.2Potential Requirements  p. 65
5.11.3Potential Solutions  p. 65
5.11.4Evaluation of solutions  p. 66
5.12Coordinating CCLs with other management functions  p. 67
5.12.2Potential requirements  p. 67
5.12.3Possible solutions  p. 67
5.12.3.1Required capabilities and interactions.  p. 67
5.12.3.2Information objects to realize required capabilities and interactions  p. 67
6Conclusions and Recommendations  p. 68
6.1Closed control loop and intent  p. 68
6.2Dynamic CCL Creation  p. 68
6.3Triggered CCL  p. 68
6.4Use case 4: closed control loop for problem recovery  p. 69
6.5CCL creation based on Historical CCL data  p. 69
6.6CCL for fault management  p. 69
6.7CCL conflicts management  p. 69
6.8CCL scope management  p. 70
6.9CCL-impact assessment and resolution  p. 70
6.10Consumers feedback on CCL actions  p. 70
6.11CCL decision escalation  p. 71
6.12Performance Evaluation of a Closed Control Loop  p. 71
APlantUML Code for figures  p. 72
A.1Relationship UML diagram for CCL Management  p. 72
A.1.1Closed Control Loop Coordination NRM fragment (Figure 5.6.3.1-2)  p. 72
A.1.2CCL co-ordination entity as a CCL using recurrence (Figure 5.6.3.7.1-1)  p. 72
A.1.3Closed Control Loop NRM fragment (Figure X.1-1)  p. 73
A.2Procedures for CCL Management  p. 73
A.2.1Detection and avoidance of potential goal targets conflicts (Figure 5.3.3.1-1)  p. 73
A.2.2Detection and avoidance of direct actions conflicts (Figure 5.6.3.4.1-1)  p. 74
A.2.3Detection of actual conflicts based on counter-productiveness (Figure 5.6.3.4.2.1-1)  p. 74
A.2.4Avoidance of potential direct actions conflicts (Figure 5.6.3.4.3.1-1)  p. 75
A.2.5Detection of potential and actual indirect targets conflicts (Figure 5.6.3.5.1.1-1)  p. 76
A.2.6avoidance of potential indirect targets conflicts (Figure 5.6.3.5.3.1-1)  p. 76
A.2.7Information exchange on action plans alignment and selection for avoidance of potential action-execution-time conflicts (Figure 5.6.3.6.1.1.1-1)  p. 77
A.2.8Information exchange on detected conflict for avoidance of potential action-execution-time conflicts (Figure 5.6.3.6.1.1.2-1)  p. 78
A.2.9Avoiding action-execution-time conflicts (Figure 5.6.3.6.2.1-1)  p. 78
A.2.10Detection and avoidance of scope conflicts (Figure 5.7.3.1-1)  p. 79
A.2.11Detection of actual indirect targets conflicts via impact on unknown or unbounded impact-scope (Figure 5.8.3.1.1-1)  p. 79
BPotential solution for CCL information modelling  p. 81
B.1 General Closed Control Loop Model  p. 81
$Change history  p. 82

Up   Top