1
Scope
2 References
3 Terms and Definitions
3.1 Definitions from ITU-T Rec. M.3100
3.2 Definitions from ITU-T Rec. G.872
3.3 Definitions from ITU-T Rec.
G.709/Y.1331
3.4 Definitions from ITU-T Rec. G.798
3.5 Definitions from ITU-T Rec.
G.7710/Y.1701
4 Abbreviations and Acronyms
5
OTN NE Management Requirements
6 Analysis
7 Design of the Protocol-neutral
Information Model
7.1 UML Class Diagram
7.1.1 Class Diagram for OTN-Specific Entity
7.1.2 Class Diagram for Fault Management Support Entity
7.2 UML Data Dictionary
7.2.1 Data Dictionary for OTN Specific Entity
7.2.2 Data Dictionary for Fault Management Support Entity
Appendix I – Usage of
the Model for TCM and GCC
I.1 TCM locations
I.1.1 TC_Trail between ODUk_CTP Source and ODUk_CTP Sink (Points C and D)
I.1.2 TC_Trail between ODUk_CTP Sink and ODUk_CTP Source (Points E and F)
I.1.3 TC_Trail between ODUk_TTP Source and ODUk_CTP Source (Points G and H)
I.1.4 Two TC_Trail terminations within one ODUk_CTP
I.2 GCC access locations
I.2.1 COMMS channel between two ODUk_TTPs (Points A and B,TT atomic functions are included)
I.2.2 COMMS channel between ODUk_CTP and ODUk_TTP (Points C and B(bis)
TT atomic function at B(bis) is not included)
I.2.3 Several COMMS channels
I.3 GCC access and TCM locations together
I.3.1 TC_Trail and COMMS channel between ODUk_CTP Source and ODUk_CTP Sink (Points
C and D)
I.3.2 Terminating TC_Trail and inserting GCC within one ODUk_CTP
I.3.3 Bidirectional
example with TCM and GCC access