npo diagnosis development
TRANSCRIPT
-
7/29/2019 NPO Diagnosis Development
1/94
Alcatel-Lucent
NPO Diagnosis Development
Guide
NPO Document
User Guide
Release B10, M2, UA5, UA6
3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
2/94
Status RELEASED
Short title User Guide
All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel-Lucent.
BLANK PAGE BREAK
2 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
3/94
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1 Basic Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.2 Diagnosis Module Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2 Start Diagnosis Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 Eclipse Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.1.1 Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1.2 Editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1.3 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2 Start Diagnosis Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3 Display Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.4 Close Diagnosis Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.5 Diagnosis Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.5.1 Scenario Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.5.2 Node Outline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.5.3 Property View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.5.4 Problem View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.5.5 Scenario Graphical Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.5.6 Node Code Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.5.7 Menubar, Toolbar and Popup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.5.8 Customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.1 The Scenario Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.2 Create Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.3 Create Scenario by Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.4 Edit Scenario/Scenario Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.5 Save Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.6 Validate/Check Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.7 Delete Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.8 Create Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.8.1 First Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.8.2 Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.8.3 External Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.9 Edit Node Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503.10 Edit Node Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.10.1 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503.10.2 Link with Iteration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513.10.3 Move a Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.11 Edit Link Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.12 Copy Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533.13 Delete Node/Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4 Edit Node Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.1 Open Node Code Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.2 Node Code Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.3 Import Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.4 Define Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.4.1 QoS Indicator and Parameter Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.4.2 Topology Navigation Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.4.3 Generic Library Related Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624.4.4 List Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.5 Test Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.6 Debug Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3BK 21314 AAAA PCZZA Ed.10 3 / 94
-
7/29/2019 NPO Diagnosis Development
4/94
Contents
5 Example Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.1 V2_DR (GSM Technology) Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.1.1 Problem of unsuccessful Directed Retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.1.2 Bad settings of Directed Retry parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.1.3 Congestion on Potential Target Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.1.4 Failures on Potential Target Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.1.5 Problem of external Directed Retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.1.6 Problem of incorrect A_PBGT_DR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735.1.7 Problem of incorrect FREE_LEVEL_DR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735.1.8 Problem of incorrect L_RXLEV_NCELL_DR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735.1.9 Problem of internal Directed Retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745.1.10 V4_TCONG.Bad settings of queuing parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.2 Scenario V2_SDROP(GSM Technology) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.2.1 SDCCH drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.2.2 BSS internal problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.2.3 Link failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.2.4 Processor restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.2.5 SDCCH drop HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.2.6 SDCCH drop radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775.2.7 SDCCH drop system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775.2.8 SDCCH HO not activated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775.2.9 Standalone SDCCH HO problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785.2.10 TCH HO problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785.2.11 TCH radio problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.3 WAC Cluster Configuration (WiMAX Technology) Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795.3.1 1st Node Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805.3.2 2nd test Node Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815.3.3 3rd Node Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6 Introduction to Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.1 Getting Start with Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.1.1 Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846.1.2 Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866.1.3 Unicode Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886.1.4 Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
6.2 Knowing More About Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916.2.1 First Steps Towards Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916.2.2 if Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926.2.3 for Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926.2.4 The range() Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936.2.5 break and continue Statements and else Clauses on Loop . . . . . . . . . . . . . 936.2.6 pass Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946.2.7 More About Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
5/94
Figures
Figures
Figure 1: Diagnosis Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 2: Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 3: Diagnosis Editor Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 4: Diagnosis Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 5: Node Outline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 6: Node Outline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 7: Property Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 8: Node Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 9: Link Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 10: Link with Iteration Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 11: Scenario Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 12: Problem View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Figure 13: Property View Customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 14: Error Sorting Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 15: Error Grouping Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 16: Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 17: Set Item Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 18: Scenario Graphical Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 19: Node tooltip example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 20: Links and links with iteration in Scenario Graphical Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 21: Fly-out Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 22: Fly-out Palette Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 23: Editing Node Code in Scenario graphical Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 24: Scenario Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 25: Node Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 26: Help Menu Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 27: Context Menu on Scenario Tree Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 28: Context Menu in Scenario Graphical Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 29: Node Context Menu in Graphical Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 30: Context Menu on Proper ty View - Key and Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 31: Context Menu on Property View - Value and Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 32: Context Menu on Indicator Association in Scenario Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 33: Context Menu on View Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 34: Context Menu on Editor Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 35: Create Scenario Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 36: Awaiting server response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 37: Dispatching Request to Get Scenario Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 38: Edit Scenario Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 39: Node Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3BK 21314 AAAA PCZZA Ed.10 5 / 94
-
7/29/2019 NPO Diagnosis Development
6/94
Figures
Figure 40: Link Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 41: Link with Iteration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 42: Link Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 43: Link Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 44: V2_DR Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 45: Scenario V2_DR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
7/94
Preface
Preface
Purpose This document describes the diagnostic solutions provided by the NPO andthe Diagnosis Editor.
Whats New In Edition 10
Update the sections with information about the W-CDMA.
In Edition 09
The document administrative part is updated.
In Edition 08
Test Syntax (Section 4.5) was updated.
In Edition 07
Overall document quality was improved following an editorial review.
In Edition 06
A note was added in Edit Node Code (Section 4).
In Edition 05
The document was updated after technical validation.
WiMAX information was added.
In Edition 04
Overall document quality was improved following an editorial review.
In Edition 03
Validate/Check Scenario (Section 3.6) was updated.
In Edition 02
Graphics were updated.
In Edition 01
3BK 21314 AAAA PCZZA Ed.10 7 / 94
-
7/29/2019 NPO Diagnosis Development
8/94
Preface
First official release of the document.
Audience This guide is intended for operators responsible for diagnosing QoS problems.
Assumed Knowledge You must be familiar with the radio network and Network PerformanceOptimizer (NPO) concepts.
8 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
9/94
1 Basic Concepts
1 Basic Concepts
This section provides an overview of the NPO Diagnosis architecture.
3BK 21314 AAAA PCZZA Ed.10 9 / 94
-
7/29/2019 NPO Diagnosis Development
10/94
1 Basic Concepts
1.1 Terminology
Diagnosis Scenario A diagnosis scenario is an analysis tree that contains ways to investigate a quality ofservice problem using the data available in the NPO. The scenario can be system oruser defined.
Node Nodes provide code that implements checks in order to evaluate the possible causeof a problem.
Link Links provide the association between nodes. A link is oriented from a consequencenode to a causal node.
Eclipse Eclipse is the Diagnosis Development Tool, used to define diagnosis scenarios.
Node Code Editor The Node Code Editor is used to write the node code.
1.2 Diagnosis Module Process
The diagnosis functions in Optimization are used to find the probable rootcause of a QoS or performance problem.
The operator can launch the diagnosis in different contexts:
For a detected QoS degradation (typically when a QoS indicator has
crossed a threshold)
For a network object (e.g. a cell) for which the operator wants to check (and
to know what is the problem, if any)
For a set of network objects (typically a group of cells) that the operator
wants to check.
Once executed, the diagnosis returns the results to the operator (who thentunes radio parameters to correct the degradations and optimize the network).
Use of the Diagnosis functions is restricted to the owner of the MUSE_DIAGNOSIS_LICENSE for all use cases.
The Diagnosis module includes the following logical blocks:
The Diagnosis Development Tool which allows experts to create the
diagnosis scenarios. A scenario language is defined to allow the description
of scenarios
The Advanced Graphical User Interface mechanism (graphical tool, assisted
language):
Diagnosis user interface to launch the diagnosis and get the results
Diagnosis server engine to execute the diagnosis scenarios and provide
reports.
The diagnosis scenario are defined and configured in the diagnosis tool by anexpert (Alcatel-Lucent or operator). The Expert Role can be handled by thesystem administrator. The Expert uses a dedicated tool in order to develop the
diagnosis scenarios. The Administrator imports/exports diagnosis scenarios inthe system through the Web administration interface.
10 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
11/94
1 Basic Concepts
The operator optimizer is in charge of optimizing the radio network andlaunches the diagnosis scenario to discover the cause of the problem. Theoperator should only use the Analysis desktop.
It is also possible to define Tuning Session applications in the DiagnosisEditor. These applications trigger the execution of specific checks for tuning
parameter validation.Use the System Scheduler to schedule the diagnosis execution.
3BK 21314 AAAA PCZZA Ed.10 11 / 94
-
7/29/2019 NPO Diagnosis Development
12/94
1 Basic Concepts
12 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
13/94
2 Start Diagnosis Editor
2 Start Diagnosis Editor
This section presents an overview of the Diagnosis Editor.
3BK 21314 AAAA PCZZA Ed.10 13 / 94
-
7/29/2019 NPO Diagnosis Development
14/94
2 Start Diagnosis Editor
2.1 Eclipse Environment
Eclipse is an open source community whose projects are focused on providingan extensible development platform and application frameworks for buildingsoftware. It has a generic set of development services that can be used by anyplug-in tool and includes a built-in Java Development Tool plug-in.
Eclipse provides the diagnosis expert with a graphical development environmentfor diagnosis design and scenario creation. The user draws a diagnosis causaltree and then writes each node code, all of them in a user-friendly environment.
The Eclipse Platform User Interface is built around a concept of a window thatprovides the overall structure and presents an extensible user interface to theuser. The following complete window is known as the "Diagnosis Editor"(see the following figure).
Figure 1: Diagnosis Editor
The Diagnosis Editor is based on editors, views and perspectives.
14 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
15/94
2 Start Diagnosis Editor
2.1.1 Title Bar
The title bar is the strip at the at the top of the "Diagnosis Editor" window.
It begins with an icon and is followed by the application name, the user name,server IP address and the name of the currently opened scenario.
All these are configurable and mandatory. On the right, several icons allowyou to minimize, maximize or close the application.
Figure 2: Title Bar
2.1.2 Editors
Editors allow the user to open, edit, and save objects. They follow anopen-save-close lifecycle much like file system based tools, but are more tightlyintegrated into the window. When active, an editor can contribute actions tothe "Diagnosis Editor" window menus and tool bar.
Two editors appear in tabs in the middle of the window:
Scenario Graphical Editor
Node Code Editor.
2.1.3 Views
Views provide information about some object that the user is working with in the"Diagnosis Editor" window. Modifications made in a view (such as changing aproperty value) are generally saved immediately, and the changes are reflectedimmediately in other related parts of the user interface.
There are four views in the "Diagnosis Editor" window:
Scenarios View
Node Outline View
Properties View
Problems View.
The "Properties View" and "Problems View", corresponding to ScenarioGraphical Editor and Node Code Editor are also displayed in tabs.
The user can rearrange a view or an editor by drag and drop and customize tobetter suit a particular task (resizing is possible moving to the left, to the right,to bottom or to top the splitters that separate views and editors).
2.2 Start Diagnosis Editor
To start the Eclipse application:
1. From the icon box, select MUSE Applications->Optimization->DiagnosisEditor.
OR
From the Analysis Desktop, select Data->Diagnosis....
A splash screen appears to the user with a progress bar displaying theprogress in bringing up the Diagnosis Editor.
3BK 21314 AAAA PCZZA Ed.10 15 / 94
-
7/29/2019 NPO Diagnosis Development
16/94
2 Start Diagnosis Editor
2. Check that the "Diagnosis Editor" window appears to the user, with all partsdisplayed at their default location, as shown in the following figure.
Figure 3: Diagnosis Editor Window
The Title bar of the "Diagnosis Editor" window displays:
The Alcatel-Lucent Diagnosis Editor
The user name
The server IP address or server hostname.
The title bar is updated once a scenario is opened with the name of scenario.
Below the Title bar, the customized menus appear:
Scenario Menu item, with all the options related to a scenario
Nodes Menu item, with all options related to a node.
Help menu item
Note: Each item in the menu is Enabled/Disabled according to the FAD availableto the current user.
Below the customized menus, there are the customized toolbars that provide aquick access to the options available under the menus.
To the left is the Scenario Tree Viewer. On startup, a list of available scenarionames is provided from the server. A tree displaying the list of scenarios ispopulated and displayed under this view.
On startup, these parts are empty and they are populated only when there isan active scenario:
To the right - the Node Outline View
On the bottom- the Properties and Problems Views
In the center - the Scenario Graphical Editor.
16 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
17/94
2 Start Diagnosis Editor
2.3 Display Scenario
Once the Diagnosis Editor is up and running, the Scenario Tree View ispopulated with the list of available scenarios.
Displaying a scenario involves:
Displaying the Scenario Nodes as saved by the user in the Graphical Editor
Displaying each nodes code and properties
Populating the Outline and Properties View based on the Users context
of interaction.
Note: Only the code for the nodes that belong to the current scenario appears.
The maximum number of scenarios that can be opened in the ScenarioGraphical Viewer is configurable.
To display a scenario:
1. Select a Scenario from the Scenario Tree View.
2. Perform one of the following actions:
From the menu bar, select Scenario->Display scenario, or
Right click on the Scenario. Then, from the popup menu, select Display
Name of Scenario, or
Double click on the Scenario, or
Click on the icon from the toolbar, or
Press [ CTRL ] + [ D ].
The following figure shows the menu option to display a scenario:
, where V2_DR is the scenario name.
2.4 Close Diagnosis Editor
To close the Diagnosis Editor:
1. Select Scenario->Exit.
If there are any unsaved scenarios, a dialog box listing the scenariosthat need to be saved appears.
2. Check the appropriate scenarios that need to be saved.
3. Click on [ OK ].
3BK 21314 AAAA PCZZA Ed.10 17 / 94
-
7/29/2019 NPO Diagnosis Development
18/94
2 Start Diagnosis Editor
2.5 Diagnosis Editor
This section describes the Diagnosis Editor graphical user interface. Itdescribes the layout of different parts within the "Diagnosis Editor" window.
Figure 4: Diagnosis Editor
2.5.1 Scenario Tree View
The Scenario Tree View displays the list of available scenarios. Scenarionames are displayed at the root level of the tree if a Family is not defined.
Usually, scenarios are grouped on the basis of Family / Sub Family. To view thescenarios from a family, click on + from to expand the tree. All the scenariosgrouped within that family are displayed in a tree and the icons change into .
Each scenario has an associated icon that represents whether the Scenario isa System Scenario or Customer Scenario.
Icon Description
If the scenario is a system scenario supplied by Alcatel-Lucent.
If the scenario is created by customer and it belongs tocustomer dictionary.
If the scenario is created by customer and it is not validated.
If the scenario is a system scenario and not validated.
Table 1: Icons for Scenario Tree View
A scenario is available in the Analysis Desktop and can be executed onlywhen it is validated.
A single click selection of a scenario in Scenario Tree View does not imply that
the Scenario appears in the Scenario Graphical Viewer. Similarly, a scenario
18 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
19/94
2 Start Diagnosis Editor
selected in the Scenario Graphical Viewer does not imply that the respectivescenario is selected in the Scenario Tree View.
By default, the Scenario Tree View part appears to the left of the DiagnosisEditor.
When Link with Editor menu item from the Scenario Tree
Toolbar is enabled:
Selecting any scenario in the Scenario Tree would bring to the front the
corresponding Graphical Editor for that scenario (if the scenario is currently
opened)
On Changing tabs between the Graphical Editor, the corresponding scenario
name is selected in the Scenario Tree View.
2.5.2 Node Outline View
The Node Outline View displays a list of nodes available for the current active
scenario. It provides quick access to the nodes related to the current scenario.If there are no opened scenarios, this view is empty.
Figure 5: Node Outline View
Available nodes are displayed in a list view format, in this order:
First Node
Standard Nodes in alphabetical order
External Nodes in alphabetical order.
Each node has a related icon representing the node type, as follows:
Type Icon Displayed String
First Node Node_Name
Node Node_Name
External Node External_Scenario_Name.Node_Name
By Default, the Node Outline View appears to the right of the Diagnosis Editor.
Once the Node Code Editor is opened for editing a node code, the Node
Outline View displays the libraries and the variables defined for the node.
3BK 21314 AAAA PCZZA Ed.10 19 / 94
-
7/29/2019 NPO Diagnosis Development
20/94
2 Start Diagnosis Editor
Figure 6: Node Outline View
It is now possible to:
Sort the elements alphabetically, by clicking on
Hide the comments, by clicking on
Hide the libraries, by clicking on
Collapse all, by clicking on
Expand all, by clicking on .
2.5.3 Property View
Property View displays all properties linked to a Scenario, a Node or a Link.The properties view gets populated based on the context of user operation.
If a scenario is opened and no nodes are selected in the scenario, then theproperty view displays the details related to the scenario.
If a node is selected in the Scenario Graphical Editor or in Node Outline View,then it displays the properties of the node.
If a link between two nodes is selected, then the properties for the link are
displayed.
By default, the Property View appears at the bottom of the Diagnosis Editor.
Figure 7: Property Toolbar
When selecting the first icon from the Property Toolbar, a two option windowopens that allows the user to select the type of properties to display:
Show Categories
Show Advanced Properties.
20 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
21/94
2 Start Diagnosis Editor
2.5.3.1 Node Property
If a node is selected in the Scenario Graphical Editor or in Node Outline View,the node details are displayed in the property view. If the user has editingrights, the user can edit node information in the property view by double clickingon the value field for the respective property.
Name of the node, the Description and the X and Y coordinates can bemodified. On changing any property, the Scenario Graphical Editor and NodeOutline View are updated to reflect the changes.
Figure 8: Node Property
2.5.3.2 Link Property
If a link is selected in the Scenario Graphical Editor, the Link Rank appearsin the Property View. If the user has the editing rights, the user can modifythe Rank associated with that Link. Each link also has a property calledCut off associated with it, meaning that if the next node proves to be True,the evaluation of the scenario is immediately stopped (this is a find first rootcause mechanism).
Figure 9: Link Property
If the link is a link with iteration, along with the Rank, the property window alsodisplays the Iteration List and the Iteration Variable.
Figure 10: Link with Iteration Property
3BK 21314 AAAA PCZZA Ed.10 21 / 94
-
7/29/2019 NPO Diagnosis Development
22/94
2 Start Diagnosis Editor
2.5.3.3 Scenario Property
If neither a node nor a link is selected in the Scenario Graphical Editor and anode is not selected in the Node Outline View, the Property window displaysthe properties of the currently active scenario.
Figure 11: Scenario Property
The operator cannot modify the scenario properties.
2.5.4 Problem ViewIf there are any errors / problems in the Diagnosis Node Code Editor, theProblem View displays these errors.
Figure 12: Problem View
By default, Problem View appears at the bottom of the Diagnosis Editor.
When selecting the icon from the Problem Toolbar, the following optionsallow the user to customize the Property View:
Figure 13: Property View Customizing
To sort the errors, from the toolbar menu, select Sorting and in the new openwindow, select the sorting criteria:
Figure 14: Error Sorting Criteria
22 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
23/94
2 Start Diagnosis Editor
Errors can be sorted by these criteria (ascending or descending): Severity andDescription / Path / Resource / Location / Creation Time / Id.
To restore the default sorting criteria, click on [ Restore Defaults ].
To group errors, select Grouping and choose one of the following options:Type / Java Problem Type / Severity / None .
Figure 15: Error Grouping Criteria
To select filters to be applied on the Problem view, from the Toolbar menu,select Filters. A list of available filters appears. Check the filters to apply.
To configure filters, select the icon from the Toolbar.
The following widow opens.
Figure 16: Filters
To select one filter, check the box related to the filter.
To select all filters, click on [ Select All ].
To deselect all filters, click on [ Deselect All ].
To add a new filter, click on [ New ] and in the window that opens, fill in the filtername, then click on [ OK ].
To remove a filter from the list, check the filter, then click on [ Remove ].
Note: The default filter cannot be removed.
Check the filter to configure, then:
Select the type of elements on which the filter is configured:
On any element
On any element in the same project
On a selected element only
On a selected element and its children
On a working set.To select one working set, click on [ Select... ] and in the window that opens,check one of the options: Window Working Sets / Selected Working Sets.If needed, the user can add new working sets.
3BK 21314 AAAA PCZZA Ed.10 23 / 94
-
7/29/2019 NPO Diagnosis Development
24/94
2 Start Diagnosis Editor
If required, add a description of the filter type:
Select and fill in the following field with the appropriate
comment
Select and fill in the following field with the appropriate
comment.
To filter errors of one type of severity, check the box attached to Where severityis, then check the box attached to the type of problem:
Error
Warning
Info.
To select the type of items, check the box(es) attached to the possible types(displayed to the right of the window).
To select all types of items, click on [ Select All ].To deselect all types of items, click on [ Deselect All ].
To restore the defaults characteristics of the filter, click on [ Restore Defaults ].
To limit visible items per group, from the Toolbar menu, select Preferences....A new window opens, as shown in the following figure.
Figure 17: Set Item Limits
Check the Use marker limits field, fill in the number of visible items, thenclick on [ Ok ].
To restore defaults value (100 items / group), click on [ Restore Defaults ].
24 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
25/94
2 Start Diagnosis Editor
2.5.5 Scenario Graphical Editor
The Scenario Graphical Editor is one of the major components of the DiagnosisEditor, displayed in the center of the window, used to display the graphicalrepresentation of a Scenario (links and nodes).
The Scenario Editor (Tab) title displays the name of the Scenario. An additional* appears if the current Editor was modified, as in the following example:
. The* is not shown when the current Editor is saved.
The Scenario is colored in:
Orange , when it is a system scenario
Green , when the scenario is created by customer.
As long as a scenario is not validated, it is marked with /.
Figure 18: Scenario Graphical Editor
Nodes are displayed in the Scenario Graphical Editor using the representativeicons. The Node name appears below the icon. Each node appears at itsrespective X and Y location, retrieved from its node property.
On mouse-over the node, a tool-tip appears displaying following informationabout node:
Mode name
Mode description
Mode code snipped (first 100 characters).
For an external node, only the node name appears on mouse-over the node.
3BK 21314 AAAA PCZZA Ed.10 25 / 94
-
7/29/2019 NPO Diagnosis Development
26/94
2 Start Diagnosis Editor
Figure 19: Node tooltip example
Multiple nodes can be selected in the Scenario Graphical Editor by holdingdown the [ Ctrl ] or [ Shift ] keys and clicking on various nodes or pressing theleft mouse button and dragging the selection box over the nodes to be selected.
Note: For a node to be selected, the node should be completely within the boundingselection rectangle.
For example, in the following figure, six nodes are selected.
26 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
27/94
2 Start Diagnosis Editor
2.5.5.1 Links
Links are also known as connections. The link orientation defines the causalitybetween two nodes (which node is the cause, which node is the consequence).A consequence node can have several causal nodes. Links between nodes aredirected to visually represent the flow of execution. Rank associated with links
decides the order of execution of casuality nodes.The link can also carry an iteration variable enabling to test the next node ona set of variables (for neighbor or adjacency checks provided a given cellfor instance).
Links with iteration are represented using dotted blue directed lines.
Links can also be defined as cutoff, meaning that if the causal node provesto be true, the evaluation of all sibling nodes is skipped. Rank of a cutofflink is display in pink color.
Figure 20: Links and links with iteration in Scenario Graphical Editor.
3BK 21314 AAAA PCZZA Ed.10 27 / 94
-
7/29/2019 NPO Diagnosis Development
28/94
2 Start Diagnosis Editor
2.5.5.2 Fly-out Palette
The Fly-out Palette allows the user to:
Select a Node/Link
Create new Nodes/Links.
NormalIcon16x16
Large Icon32x32
Displayed Stringwithout Details
Displayed String with Details
Link Link - Create a Link
Link with iteration Link with iteration - Create a Link with iteration
Node Node- Create a node
First Node First Node- Create a first node
External Node External Node- Create an external node
Table 2: Icons for Fly-out Palette
Figure 21: Fly-out Palette
Right clicking on the Fly-out Palette provides the user with the following options:
Change the Layout to Columns, List, Icons Only and Details
Display Large Icons
Change Settings
Pinned. If unchecked, the palette hides itself when the cursor moves out
of the palette area.
28 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
29/94
2 Start Diagnosis Editor
To change the settings of the Fly-out Palette, click on Settings. A dialogbox appears.
Figure 22: Fly-out Palette Settings
The following settings are available.
Font To change the "Diagnosis Editor" window Dialog Font,
click on . A new window opens, which allowsuser to change the settings.
To come back to the system default font settings, click
on .
Layout To change the Layout to Columns, check the Columnsfield.
To change the Layout to List, check the List field.
When set to List, Layout can use large icons, when theUse large icons field is checked.
To change the Layout to Icons only, check the Iconsonly field.
To change the Layout to Details, check the Detailsfield.
Drawer options Always close when opening another drawer.
Always close when opening another drawer.
Never close.
By default, the Fly-out Palette appears to the right of the Scenario GraphicalEditor.
To change the position of the Palette, right click on Palette and select Dockon> Left.
To resize the Palette, right click on Palette and select Resize.
3BK 21314 AAAA PCZZA Ed.10 29 / 94
-
7/29/2019 NPO Diagnosis Development
30/94
2 Start Diagnosis Editor
2.5.6 Node Code Editor
The Pydev Editor is a plug-in that enables users to use Eclipse for Pythondevelopment in order to write node code. Features like code completion, syntaxhighlighting, syntax analysis, debug traces are available.
The following icon is used in the heading for the Node Code Editor: .
Editing node code opens a new Node Code Editor in place of the ScenarioGraphical Editor. The user can switch between the editors by means of the tabs.
Figure 23: Editing Node Code in Scenario graphical Editor.
In the case of a scenario, the Editor (Tab) title displays the name of theScenario, while editing a nodes code the Editor title displays the name of thecorresponding Node. An additional * appears if the current Editor has beenmodified. The* is not shown if the current Editor is saved.
The Python libraries are used in the node code definition when the userwants to access to a QoS indicator, a parameter value, or to navigate in thetopology. The QoS and parameters libraries are generated by the offline toolsat dictionary imports. Only the topology navigation are hard coded. The use ofthe libraries allows completion when typing a indicator or parameter value.
By default, the Node Code Editor appears in the center of the Diagnosis Editor.
30 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
31/94
2 Start Diagnosis Editor
2.5.7 Menubar, Toolbar and Popup Menu
Note: When the user (even if the user is the Administrator) does not have a particularlicense for a feature, then all the popup menus, menu bar menus, toolbar itemsrelated to that feature are disabled.
2.5.7.1 Menu BarThe following figure shows the menu bar.
Figure 24: Scenario Menu
The following table lists the scenario menu items and their correspondingdescriptions.
ScenarioMenu Item
Description Accelerator
Scenario Opens the submenu under Scenario Menu Item Alt + S
New Scenario Creates a new Scenario Ctrl + N
Copy Scenario
Name ofScenario...
Copies the selected Scenario
Grayed when no scenario is currently selected
Display Nameof Scenario
Displays the Scenario
Grayed when no scenario is currently selected
Ctrl + D
Save Name ofScenario
Save the currently opened Scenario
Grayed when no scenario is currently opened or when no changes havebeen made to the scenario since last save
Ctrl + S
Properties
of Name ofScenario
Displays properties of the selected scenario in a wizard
Grayed when no scenario is currently selected
Ctrl +
Enter
Validate/InvalidateName ofScenario
Validates/Invalidates the currently opened scenario
Grayed when no scenario is currently opened or when the user does nothave privilege to modify selected scenario
Delete Deletes the selected Scenario
Grayed when no scenario is currently selected or when the user does nothave privilege to delete selected scenario
Exit Exits Diagnosis Editor Alt +F4
3BK 21314 AAAA PCZZA Ed.10 31 / 94
-
7/29/2019 NPO Diagnosis Development
32/94
2 Start Diagnosis Editor
The following figure shows the Node menu.
Figure 25: Node Menu
Node MenuItem
Description Accelerator
Node Opens the submenu under Node menu item
Create Node Create a new node in the currently opened scenario
Grayed when the user does not have the privilege to modify the currentscenario
Ctrl + 2
Create FirstNode
Creates a new First Node in the currently open scenario
Grayed when the user does not have the privilege to modify the currentscenario or when a First Node already exists in the current scenario
Ctrl + 1
CreateExternalNode
Creates a new External Node in the currently open scenario
Grayed when the user does not have the privilege to modify the currentscenario
Ctrl + 3
Edit NodeCode
Opens PyDev Editor with the node code of the currently selected node
Grayed when no node is selected
Ctrl + D
Delete Deletes the currently selected Node
Grayed when the user does not have the privilege to modify the currentscenario or when no nodes are selected
Ctrl + Delete
Copy Node Copies the currently selected Node
Grayed when no nodes are selected
Ctrl + Shift +C
Paste Nodeas ... Pastes the copied node in the current scenarioGrayed when the user does not have the privilege to modify the currentscenario or when no node was previously copied
Ctrl + Alt + V
Auto Layout Arranges all the nodes in the current scenario in a tree form
Grayed when the user does not have the privilege to modify the currentscenario or when a node is selected
Shift + F5
32 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
33/94
2 Start Diagnosis Editor
The following figure shows the Help menu.
Figure 26: Help Menu Item
2.5.7.2 Toolbar
The icons on the Toolbar display associated tool tips specifying the meaning ofthe icon when mouse is moved over them, as described in the following table.
Icon Description Grayed when ...
New Scenario Never
Copy Scenario No scenario is currently selected
Display Scenario No scenario is currently selected
Save Scenario No scenario is currently opened or no changes made since last save
Validate/InvalidateScenario
No scenario is currently opened or user is not privileged to modify selectedscenario
Delete Scenario No scenario is currently selected or user is not privileged to delete selectedscenario
Auto Layout The user is not privileged to modify the current scenario or a node is selected
Create new Node The user is not privileged to modify the current scenario
Create new FirstNode
The user is not privileged to modify the current scenario or a First Nodealready exists in the current scenario
Create newExternal Node
The user does is not privileged to modify the current scenario
Edit Node Code No node is selected
Delete Node No node is selected or user is not privileges to delete the current node
Copy Node No node is selected
Paste Node The user is not privileged to modify the current scenario or no node waspreviously copied
3BK 21314 AAAA PCZZA Ed.10 33 / 94
-
7/29/2019 NPO Diagnosis Development
34/94
2 Start Diagnosis Editor
2.5.7.3 Popup Menus
Note: All popup menus are context sensitive. Menu items are present / enabled /disabled, based on the current context.
Figure 27: Context Menu on Scenario Tree Viewer
Note: If there are no scenarios selected when the user right clicks on the ScenarioTree View, all options on the context menu, except Create Scenario underthe new menu, are disabled.
Figure 28: Context Menu in Scenario Graphical Editor
Figure 29: Node Context Menu in Graphical Editor
In the last two popup menus, option Create First node appears only when thefirst node does not exist (it is deleted).
Figure 30: Context Menu on Property View - Key and Value
Figure 31: Context Menu on Property View - Value and Key
Figure 32: Context Menu on Indicator Association in Scenario Wizard
34 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
35/94
2 Start Diagnosis Editor
Figure 33: Context Menu on View Bar
Figure 34: Context Menu on Editor Bar
2.5.8 Customizing
You can maximize or minimize all Views and Editors, by clicking on one of the
two buttons situated in the top right corner of each window :
To minimize the window, click on
To maximize the window, click on
To restore the window, click onThis option is available only if one of the first two was selected.
To modify the size of each window, drag and drop the splitters that separate
the windows.All windows can be moved from the default position.
To move views, from the popup menu of the views, select:
Move-> View to move one view
Move-> Tab Group to move both Property View and Problem View.
To move editors, from the popup menu of the Scenario Graphical Editor, select:
Move->Editor to move one editor
Move-> Tab Group to move all editors opened.
3BK 21314 AAAA PCZZA Ed.10 35 / 94
-
7/29/2019 NPO Diagnosis Development
36/94
2 Start Diagnosis Editor
36 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
37/94
3 Scenarios
3 Scenarios
This section describes the ways that a scenario can be manipulated by thesystem.
3BK 21314 AAAA PCZZA Ed.10 37 / 94
-
7/29/2019 NPO Diagnosis Development
38/94
3 Scenarios
3.1 The Scenario Tree
A diagnosis scenario is a formal description of a causal graph expressed asa linked set of nodes. Each node provides code that implements checks inorder to evaluate the possible cause of a problem.
The maximum number of nodes in a scenario is limited (to 150 nodes).There are three types of nodes:
The first nodeAppears at the beginning of a scenario and is the entry point of thescenario execution. A scenario must have a first node.Only one first nodeis accepted.
The classic nodeThis is the basic node. There can be as many basic nodes as required.
The external nodeRepresent a node from another scenario.
Nodes are associated by means of links. A link is oriented from a consequencenode to a causal node. A consequence node can have several causal nodes.
A link contains the variable associations between the casual and consequencenodes.
There are two types of links:
The classic link
The link with iteration, list and variable.
The arrow of the links differs depending on the link type.
The NPO concept of the Availability domain is reused to specify on which objecttypes the scenarios are valid at each temporal level. The availability domain isdefined by the scenario developer.
A diagnosis scenario can reference a QoS indicator that semiautomaticallytriggers the execution of the scenario on the threshold crossing. If no referenceindicator was set, the execution of the scenario can be triggered through amanual Network Object selection operation in the Analysis Desktop.
The maximum number of Network Objects in the execution context isconfigurable.
Diagnosis is the process of execution of a scenario applied on an initial context.
A diagnosis can be executed:
On one objectThe textual output describes probable failure cause and possible remedy.
On a set of objects.The output provides the list of objects which were identified by the scenario.The intent is to select cells candidate for further analysis.
Diagnosis scenario result reports are provided in a synthetic or detailed waydepending on the execution mode.
38 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
39/94
3 Scenarios
Execution Modes/Context
The Detailed Mode launches a diagnosis execution, specified by the user,on a single network object, at a specific date, for a given periodicity, with agiven QoS requirement level (taken from the current working zone). This modeis used to interactively launch the diagnosis from the NPO application. An
HTML report is generated.The Synthetic Mode is available for one or many network objects (withparameter associated), and optionally with a date and a periodicity if the inputcontext contains the corresponding variables. The QoS requirement level isrequired if a date and periodicity are given.
This execution mode is similar to a classical view execution for QoS orParameter in the NPO. The Analysis Desktop basically displays a matrixof Boolean values, but it can also return string values with the status. TheSynthetic mode implies that the diagnosis execution stops at the first detectedproblem.
The Tuning Session Mode is used to launch the execution of specific
scenarios (called complex rules) that are used to check parameter validity.For more information about the execution of a scenario, refer to ExecuteScenario from the NPO User Guide.
3.2 Create Scenario
To create a new scenario:
1. Perform one of the following actions:
From the menu bar, select Scenario->New Scenario..., or
Right click in the Scenario Tree View and select Scenario->New
Scenario..., or
Click on the icon from the toolbar, or
Press [ CTRL ] + [ N ].
Use the two page wizard with default values and editable fields that appears(see below) to set up the mandatory preconditions of a scenario.
Figure 35: Create Scenario Wizard
A default scenario name is populated based on the current user. The titlearea displays messages / errors, if any, while creating a scenario.
3BK 21314 AAAA PCZZA Ed.10 39 / 94
-
7/29/2019 NPO Diagnosis Development
40/94
3 Scenarios
2. Fill in the appropriate fields, as described in the following table.
Field Name Description Read-only Default Value
ScenarioName
Name of Scenario to create must be unique. No Scenario__n
Owner The name of the user who creates the scenario. Yes
Access Access rights for Public or Private No Private
Dictionary Dictionary to which the scenario belongs. (Always acustomer dictionary in create mode).
Yes Current DictionaryName
Type Scenario type (Diagnosis or Complex rule) No Diagnosis
System Displays whether the scenario is a system scenario.
Note:Creation of system scenarios via editor is not
supported.
Yes Unchecked
Severity Error or Warning Flag, used to discriminate the complexrules (Tuning checks)
Yes, ifdiagnosisscenario
Visible Checked, if this scenario is visible in the AnalysisDesktop.
Unchecked, if this scenario is not visible in the AnalysisDesktop except by the Administrator.
No Checked
Validated Displays whether the user has considered that this
scenario is correct and executable.
Yes Unchecked
Description Operator description for node No
AvailabilityDomain -Object Type
Contains the list of object types from which the usercan choose.
The items in the list are based on the following rules:
If the Type is Complex Rule, all the Object Type in
the System are available
If the Type is Diagnosis then it displays the object
types of those modes for which scenario creationis allowed.
No
AvailabilityDomain - H
A Tooltip mentioning Hourly appears No Unchecked
AvailabilityDomain - D
A Tooltip mentioning Daily appears No Checked
AvailabilityDomain - W
A Tooltip mentioning Weekly appears No Unchecked
AvailabilityDomain - M
A Tooltip mentioning Monthly appears No Unchecked
40 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
41/94
3 Scenarios
3. If needed, add the appropriate Families.
An indicator can belong to a family and sub-family hierarchy. Up to fourdepths of sub family are currently supported.
The table cells are editable dropdown lists, proposing the existing valuesand it allows the user to add new values.
A scroll bar appears if needed. Add new rows by right clicking on a celland selecting Add Row.
Once the mandatory fields are filled in, the [ Next ] and the [ Finish ] buttonsare enabled.
4. Click on [ Next ].
The "Trigger Association Page" appears, based on the scenario typeselected.
For scenario type Diagnosis, the "Trigger Association Page" appears,as shown in the following figure.
A tree containing the list of available Indicators associated with the selectedobject type appears.
For scenario type Complex Rule, the "Trigger Association Page" appears,as shown in the following figure.
3BK 21314 AAAA PCZZA Ed.10 41 / 94
-
7/29/2019 NPO Diagnosis Development
42/94
3 Scenarios
5. For scenario type Diagnosis, double click on an Indicator from the IndicatorTree to set the selected Indicator.
Note: To clear the currently selected Indicator, click on [ Clear ].
To search for an indicator:
From the popup menu, select Search
Fill in the Indicators name in the new window opened and if needed,
check one of the search options
Click on [ Find Next ].
For scenario type Complex Rule, click on [ Add... ] to set the Parameter.A new window opens (see the following figure), displaying the parametersdivided in two trees:
Design Parameters
Logical Parameters.
6. For scenario type Complex Rule, double click on a Parameter from one ofthe lists.
7. Click on [ OK ]. The "Associate Parameter(s) with Scenario" window closes.
Note: Click on [ Remove ] to remove the currently selected Parameter.
8. Click on [ Finish ].
The scenario is created.
42 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
43/94
3 Scenarios
3.3 Create Scenario by Copy
To copy a scenario:
1. From the Scenario Tree View, select a scenario to copy.
2. Perform one of the following actions:
From the menu bar, select Scenario->Copy Scenario ..., OR
Right click and select from the popup menu Scenario->Copy Scenario
..., OR
Click on icon from the toolbar.
A question dialog windows appears informing that the external nodesare not copied.
3. Click on [ Yes ].
If the scenario is not currently open in the Graphical Editor, a progress barappears while the scenario information is retrieved from the server.
Figure 36: Awaiting server response
Once the scenario information is retrieved, a two page wizard appears (onepage after the other), as shown in the following figure.
3BK 21314 AAAA PCZZA Ed.10 43 / 94
-
7/29/2019 NPO Diagnosis Development
44/94
3 Scenarios
All the scenario properties are copied, and the following properties arechanged by default:
The name of the scenario to oldname_copy_n, where oldname is the
name of the scenario being copied and n is the copy number
The owner is set to the current user nameAccess rights are set to Public.
4. To modify any Scenario Properties, see Create Scenario (Section 3.2).
5. Click on [ Finish ].
The scenario details are updated only in the local files. The scenario mustbe saved for it to be reflected on the server.
3.4 Edit Scenario/Scenario Properties
To edit a scenario or scenario properties:
1. From the Scenario Tree View, select a scenario to edit.
2. Perform one of the following actions:
From the menu bar, select Scenario-> Properties of ..., or
Right click on the scenario and, from the popup menu, select Scenario->
Properties of ..., or
Press [ CTRL ] + [ Enter ].
If the scenario is not currently open in the Graphical Editor, a progress
bar appears to the user while the scenario information is retrieved fromthe server.
Figure 37: Dispatching Request to Get Scenario Information
Once the scenario information is retrieved, a two page wizard appears (onepage after the other) for editing the scenario properties.
44 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
45/94
3 Scenarios
Figure 38: Edit Scenario Wizard
If the scenario is not currently open in the graphical editor (or if the userdoes not have the privilege to modify the selected scenario), the wizard
displays scenario properties with all fields disabled.
A user can edit the scenario if:
The scenario is not a system scenario, if the user is the owner of the
scenario, and if the scenario is not currently locked by another user
The user is an administrator and the scenario is not currently locked
by another user.
3. Edit the required Scenario Properties, if any (only fields that are enabled);see Create Scenario (Section 3.2).
4. Click on [ Finish ].
The scenario details are updated only in local files. The scenario must besaved for it to be reflected on the server.
3.5 Save Scenario
To save a scenario:
1. From the Scenario Tree View, select a scenario to save.
2. Perform one of the following actions:
From the menubar, select Scenario->Save , or
Click on icon from the toolbar.
An information message appears:
3. Click on [ OK ].
The scenario is saved.
3BK 21314 AAAA PCZZA Ed.10 45 / 94
-
7/29/2019 NPO Diagnosis Development
46/94
3 Scenarios
3.6 Validate/Check Scenario
Before marking a scenario as validated, all nodes must be checked to detectsyntax error, undefined functions or invalid parameters.
A scenario that is not validated is not be visible in Analysis Desktop and
cannot be executed.Note: Only saved scenario can be marked as validated.
A scenario that is linked with an invalid scenario must be tagged invalid.
After validating a scenario, if Diagnosis Scenario window was already openedin Analysis Desktop, perform a Refresh All action.
To validate a scenario:
1. From the Scenario Tree View, select a scenario to validate.
2. Perform one of the following actions:
From the menubar, select Scenario->Validate ...,
or
Click on the icon from the toolbar.
A question dialog appears.
3. Click on [ Yes ].
An information message appears:
4. Click on [ OK ].
The scenario is validated.
The following modifications to a Validated scenario automatically mark thescenario as Invalid:
Adding / Deleting Nodes / Links
Editing Node Code
Modifying Scenario Properties.
46 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
47/94
3 Scenarios
3.7 Delete Scenario
To delete scenario:
1. From the Scenario Tree View, select a scenario to delete.
2. Perform one of the following actions:
From the menubar, select Scenario->Delete, or
Right click on the scenario and select from the popup menu:
Scenario->Delete, or
Click on the icon from the toolbar left side.
A question dialogue appears.
3. Click on [ Yes ].
If the scenario had been opened in the Graphical Editor, the associateeditors (including Node Code Editor) close.
The scenario is deleted and removed from the Scenario Tree View.
3.8 Create Node
Note: By default, the a suggested node name appears. Node names must be unique.
A scenario must have a first node. Only one first node is accepted.
3.8.1 First Node
To create the first node:
1. Perform one of the following actions:
From the menubar, select Node->Create First Node, or
Right click in the Scenario Graphical Editor and, from the popup menu,
select Node->Create First Node..., or
Click on the icon from the Fly-out Palette, then click in the Scenario
Graphical Editor, or
Click on the icon from the toolbar, or
Press [ CTRL ] + [ 1 ].
The following dialog box appears.
3BK 21314 AAAA PCZZA Ed.10 47 / 94
-
7/29/2019 NPO Diagnosis Development
48/94
3 Scenarios
2. Fill in the following fields:
Name with the name for the first node
Description a short description of the node.
3. Click on [ OK ].
The first node is created and displayed in the Scenario Editor and in theNode Outline View.
3.8.2 Node
To create a standard node:
1. Perform one of the following actions:
From the menubar, select Node->Create Node, or
Right click in the Scenario Graphical Editor and, from the popup menu,
select Node->Create Node..., or
Right click in the Node Outline View and, from the popup menu, select
Node->Create Node..., or
Click on the icon from the Fly-out Palette, then click in the Scenario
Graphical Editor, or
Click on icon from the toolbar, or
Press [ CTRL ] + [ 2 ].
The following dialog box appears.
2. Fill in the following fields:
Name with the name for the first node
Description with a short description of the node.
3. Click on [ OK ].
The node is created and displayed in the Scenario Editor and in the NodeOutline View.
48 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
49/94
3 Scenarios
3.8.3 External Node
To create an external node:
1. Perform one of the following actions:
From the menubar, select Node->Create External Node, or
Right click in the Scenario Graphical Editor and, from the popup menu,
select Node->Create External Node..., or
Right click in the Node Outline View and, from the popup menu, select
Node->Create External Node..., or
Click on the icon from the Fly-out Palette, then click in the Scenario
Graphical Editor, or
Click on the icon from the toolbar, or
Press [ CTRL ] + [ 3 ].
The following dialog box appears.
For Auto completion, press at the same time the [ CTRL ] +[ Space ] keys:
When the Name field is empty
When the . is entered.
2. Fill in the Name field with the following:
External scenario name
.
Its node name.
An example of an external node name is:V2_DR_Copy.V2_DR_Copy_Problem of unsuccessfulDirected retry.
3. Click on [ OK ].
The node is created and displayed in the Scenario Editor and in the NodeOutline View.
3BK 21314 AAAA PCZZA Ed.10 49 / 94
-
7/29/2019 NPO Diagnosis Development
50/94
3 Scenarios
3.9 Edit Node Properties
Once a node is selected, node properties are updated in the "Property View".
Figure 39: Node Property
To edit node properties, double click on the property value in the ValueColumn for:
Node Name
Description
X and Y coordinate.
Only these fields are editable. Fill in the new values.
To save the new properties, click on [ Enter ].
3.10 Edit Node Links
A link is oriented from a consequence node to a causal node. A consequencenode can have several causal nodes.
There are two types of links:The classic link
The link with iteration list and variable, meaning that the following node must
be evaluated one time for each value of this iterator.
The arrow of the links differs depending on the link type.
Links can be defined as cut off, meaning that if the next node proves to betrue, the evaluation of the scenario is immediately stopped.
A link between two nodes is invalid, in fact it cannot be created and a messageappears to the operator in the following cases:
The new link creates a loop within the scenario (inter scenario loops are
checked on save)
The target node is the First Node
The source node is an External Node.
3.10.1 Link
To create a new link:
1. In the Fly-out Palette in the Scenario Graphical Editor, click on Create a link.
The cursor is updated to indicate that a link is selected.
50 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
51/94
-
7/29/2019 NPO Diagnosis Development
52/94
3 Scenarios
6. If the link created is a cutoff link, then check the Cutoff field.
7. Fill in with the appropriate value:
Iteration List
Iteration Variable.
8. Click on [ OK ].
The link is created and reflected with a directional dotted blue line betweenthe two nodes (from the cause node to the consequence node).
The rank of the link appears closed to the target node (it is indicated in pinkif the Cutoff field was checked).
3.10.3 Move a Link
To move a link:
1. Select the link.
2. Put the mouse on the extremity you want to move.
3. Drag the link to the new node.
3.11 Edit Link Properties
Once a link is selected, link properties are updated in the "Property View".
Figure 42: Link Property
Figure 43: Link Property
To edit link properties, double click on the property value in the Value Columnfor:
Rank
Cutoff
Iteration List ( in case of link with iteration)
Iteration Variable ( in case of link with iteration).
Only these fields are editable. Fill in the new values.
To save the new properties, click on [ Enter ].
52 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
53/94
3 Scenarios
3.12 Copy Node
Note: When copying a Node, the Nodes link and node position are not copied. Onlythe node description and node code are copied.
To copy a node:
1. In the Scenario Graphical Editor, select a node to copy.
2. Perform one of the following actions:
From the menubar, select Node->Copy Node, or
Right click and, from the node popup menu, select Copy Node, or
Click on the icon from the toolbar.
3. In the Scenario Graphical Editor, perform one of the following actions:
From the menubar, select Node->Paste Node As..., or
From the popup menu, select Paste Node as..., or
Click on the icon from the toolbar.
A new dialog box opens that allows the user to select the type of node topaste (by default standard node).
Note: Pasting a node as a First Node is possible only when the scenario does notalready have a first node.
To paste node as an External Node, paste the node as an external node linkingto the scenario from which it was copied.
Pasting a node as an External Node is possible only when:
The current scenario is not the same as the copied node scenario, and
The copied node scenario is not a system scenario.
4. Select the type of node, then click on [ OK ].
If the node type selected is External Node, an external node linking to the
scenario the node was copied from is created in the existing scenario.Alternatively, the "Create new node" dialog box opens.
3BK 21314 AAAA PCZZA Ed.10 53 / 94
-
7/29/2019 NPO Diagnosis Development
54/94
3 Scenarios
By default, the fields are filled in:
Name with the name of copied node_copy number
Description with the short description of the copied node.
5. Fill in the two fields with the appropriate values, then click on [ OK ].
The node is copied and pasted and displayed in the Scenario Graphical Editorand Node Outline View.
3.13 Delete Node/Link
To delete a node/link:
1. In the Scenario Graphical Editor, select a node/link to delete.
2. Perform one of the following actions:
Only for node, from the menubar, select Node->Delete, or
Right click in the Scenario Graphical Editor and, from the popup menu,
select Delete, or
Only for node, right click in the Node Outline View and, from the popup
menu, select Node->Create Node..., or
Click on the icon from the right side of the toolbar.
3. From the popup menu, select Delete.
A new dialog box opens.
4. Click on [ OK ].
The node/link is deleted.
If a node is deleted from a scenario, all the links associated to the node arealso deleted (the scenario links and the links defined in other scenarios).
54 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
55/94
4 Edit Node Code
4 Edit Node Code
This section describes how to edit a node in the Node Code Editor and thetelecom primitives.
3BK 21314 AAAA PCZZA Ed.10 55 / 94
-
7/29/2019 NPO Diagnosis Development
56/94
4 Edit Node Code
4.1 Open Node Code Editor
To open the Node Code Editor:
1. Select the node to edit the code associated with it.
2. From the pop up menu, select Edit Node Code.
The "Code Editor" window opens in the center of the Diagnosis Editor, in aswitching tab with the Scenario Graphical Editor.
If there is no code associated with the node, a new empty code is created anddisplayed, otherwise the node code is loaded in the Node Code Editor.
The code is editable based on the FAD. If the user does not have the validprivileges, the Node Code editor is read-only.
The Code Editor supports the following functions:
Python Syntax highlighting
Code Auto Completion
Auto Indentation
Libraries for tracing are provided
Standard libraries for Indicators, Parameters and Topology Navigation
are also provided.
Note: The popup menu available in the Node Code Editor is not used for nodecode development.
4.2 Node Code Template
Most of the nodes follow the same structure as below:
#import libraries
import library_name
# Define variable
variable_name = library_name.primitive_template(parameter1,...,parameter n)
# Test part
if(variable_name == None):
unknown("Report when it is not possible to evaluate the node")
elif (condtion of a problem):
pbfound("Report when a problem has been found")
else:
nopbfound("Report when no problem has been found")
All words that come after the hash character # are considered to be comments.
56 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
57/94
4 Edit Node Code
4.3 Import Libraries
The NPO Diagnosis Library defines telecom primitives that are predefined tobuild test expressions and node code.
Primitives are functions that allow access to the data (indicators, parameter,
topology object).They are available only when the related library is imported into the code.
The libraries are imported in the Diagnosis Editor manually by the user eachtime a node code is developed, typing the command:
import library_name
Due to Python Syntax highlighting, the word import is always written in blue.
The following table presents the library types.
Library Definition
I_technology name QoS Indicator for specified technology
Example: I_GSM; P_WiMAX
P_technology name Logical radio parameters and the radio network design for specified technology
Example: P_GSM; P_WiMAX
P_DN_technologyname
Logical radio parameters and the radio network design for specified technology;the primitive name is constructed with the displayed names
Example: P_DN_GSM
N Generic topology primitives
N_Technology Navigation topology for a technology
Example: N_GSM
Generic Filtering and generic primitives
set Manipulation of list
4.4 Define Variables
The template to define a variable is:
variable_name = library_name.primitive_template(parameter1,...,parameter n)
All the parameters used to define a variable for a node code that are notspecified are global and can be reused in its consequence node. They arealso called initial context.
Examples of global parameters are:
object, the identifier of the network object given at the execution context
object_list, the list of identifiers of all network object on which the diagnosis
is executed.
3BK 21314 AAAA PCZZA Ed.10 57 / 94
-
7/29/2019 NPO Diagnosis Development
58/94
4 Edit Node Code
bsc = N_GSM.BSCofOMC_R( object )
When executing the scenario, this expression returns the list of all BSC of thegiven OMC-R at the execution moment.
The user can also define local parameters for a variable:
bsc = N_GSM.BSCofOMC_R( omcr19 )
When executing the scenario, this expression returns the list of all BSCof the OMC-R 19.
To declare a variable:
1. In the command line, type:
variable_name = library_name.
A list appears, displaying all the primitives available for that library, in green.
The global parameter related to that primitive appears in parenthesis.
If this list disappears, press [ Ctrl+ Space ] to reload the templates.
The AutoCompletion feature provides primitives filters once you start typing inthe command line to select an item from the dropdown list. Due to the hugenumber of telecom primitives, the word completion proposition appears onlywhen there is a unique proposition.
2. Double click on the primitive to select it.3. If needed, fill in the parameters related to that primitive with the appropriate
value.
4.4.1 QoS Indicator and Parameter Primitives
4.4.1.1 Input Parameters for QoS Indicator Primitives
The global variable (object) is passed by default to the primitives for the QoSindicator.
Once a primitive is selected, a textual description of the selected primitiveappears to the right of the list.
The following expressions are equivalent:
Ratio_HO = I_GSM.SDCCH_drop_HO_ratio ( object )
Ratio_HO = I_GSM.SDCCH_drop_HO_ratio ( )
58 / 94 3BK 21314 AAAA PCZZA Ed.10
-
7/29/2019 NPO Diagnosis Development
59/94
4 Edit Node Code
To call a QoS indicator with a context that is not the initial context, use thefollowing syntax:
Ratio_HO = I_GSM.SDCCH_drop_HO_ratio ( value )
4.4.1.2 Input Parameters for Radio Parameter Primitives
By default, the operational value(s) of the radio parameter is (are) returned.Once a primitive is selected, a textual description of the selected primitiveappears to the right of the list.
The following expressions are equivalent:
P_GSM.TIMER_T11( )
P_GSM.TIMER_T11( object, OP).
The input parameters for radio parameters primitives are:
object
type
The following table lists the possible syntax for the type parameter.
Parameter Name Meaning
OP Operational
REF Reference
REFMIN Reference Minimum
REFMAX Reference Maximum
P Planned
FC Forecast
Note: Usage of FC requires execution based on a Tuning Session, so it can onlybe used in a complex rule.
Example:
To get the minimal value of a design parameter, use the following syntax:
P_GSM.TIMER_T11(object, REFMIN)
To get the planned value of a design parameter, use the following syntax:
P_GSM.TIMER_T11(object, P)
3BK 21314 AAAA PCZZA Ed.10 59 / 94
-
7/29/2019 NPO Diagnosis Development
60/94
4 Edit Node Code
4.4.2 Topology Navigation Primitives
The feature described in this section is not yet available for W-CDMA.
These primitives provide facilities to navigate between related objects of theRNO data model. These primitives use the special prefix N.
The generic primitives that allow navigation between Parent and ChildrenNetwork Objects can replace most of these primitives.
Adjacencies topology primitives (serving, target, neighbors) are alsomade accessible via a Python primitive. Navigation primitives use somecartographical distance computing for the interference computing. If nocorresponding objects are found, the system returns empty object lists.
The following table describes the existing NPO generic topology primitives.
Name Definition Parameters
get_children_objects Returns the children network elements related to thespecified object for the specified technology.
object
technology
get_filtered_children_objects Returns the children network elements related to thespecified objects for the specified technology.
object1
object2
technology
get_parent_object Returns the parent network elements related to thespecified object for the specified technology.
object
technology
getObjectExternalId Returns the object external Id object
getObjectType Returns the object type. object