1
Scope
2
Introduction
2.1 Functional requirements
2.2 Modelling methodology
3
Normative references
4
Definitions
4.1 Alternate routed
4.2 Direct routed
5
Symbols and abbreviations
6
Information model
6.1 Entity relationship diagram
6.2 Inheritance hierarchy
6.3 Naming hierarchy
7
Information model description
7.1 Object class descriptions
7.1.1 Managed element fragment
7.1.2 Performance monitoring fragment
7.1.3 Control fragment
7.1.4 State fragment
7.1.5 Administrative fragment
7.2 Definition of common attributes
7.2.1 Relative distinguished name
7.2.2 State attributes
7.3 Description of actions
7.4 Description of notifications
8
Functional units
8.1 Functional units from other Recommendations
8.2 Negotiation of functional units
9
Relationship with other Recommendations
10 Conformance
10.1 Static conformance
10.2 Dynamic conformance
10.3 Management implementation conformance statement requirements
11 Formal object class definitions
11.1 Definition of object classes
11.1.1 ACC
11.1.2 accAffectedTraffic
11.1.3 accTrigger
11.1.4 adc
11.1.5 adcTrigger
11.1.6 cancelFrom
11.1.7 cancelRerouted
11.1.8 cancelTo
11.1.9 CircuitEndPointSubgroupCurrentData
11.1.10
circuitEndPointSubgroupHistoryData
11.1.11 congestionLevelIndication
11.1.12 destinationCodeControl
11.1.13 dccGroup
11.1.14 exchangeCurrentData
11.1.15 exchangeHistoryData
11.1.16 htrDestination
11.1.17 observedDestination
11.1.18 observedDestinationCurrentData
11.1.19 observedDestinationHistoryData
11.1.20 scr
11.1.21 scrAffectedTraffic
11.1.22 skip
11.1.23 StateIndicator
11.1.24 tarFrom
11.1.25 tarTo
11.1.26 tmCircuitEndPointSubgroup
11.1.27 tmCircuitEndPointSubgroupCurrentData
11.1.28 tmExchangeCurrentData
11.1.29 tmObservedDestinationCurrentData
11.1.30 tmTrafficControlCurrentData
11.1.31 trafficControl
11.1.32 trafficControlCurrentData
11.1.33 trafficControlHistoryData
11.2 Definition of name binding
11.3 Definition of packages
11.4 Definition of common behaviour
11.5 Definition of attributes
11.6 Definition of actions
11.7 Definition of notifications
11.8 ASN.1 defined types module
Appendix I Traffic management TMN management service
Appendix II Correlation between E.412 traffic controls and object classes
covered in this Recommendation
Appendix III State transition diagrams for automatic and manual controls
Appendix IV Differentiation of direct and alternate routed traffic for cancel-to and cancel-from controls
Appendix V Use of Q.822 history data for traffic measurements
V.1 Introduction
V.2 Overview of the performance management information model
V.3 Initial configuration
V.3.1 Current data
V.3.2
History data
V.3.3 Simple scanner
V.4 Autonomous reporting
V.5 Polled reporting
V.6 Changes to the report
V.7 Conclusions
Appendix VI Circuit end point subgroup object definition
Appendix VII Mapping of NM functions to functional units
Appendix VIII Support of the audit functionality using Q.823
VIII.1 Introduction
VIII.2 Functional requirements
VIII.3 Types of audit
VIII.3.1 Full/partial audit
VIII.3.2 Change audit
VIII.4 Mechanisms
VIII.4.1 Use of PT-GET service
VIII.4.2 Use of simple scanner
VIII.4.3 Use of discovery object
VIII.5 Conclusions
Appendix IX Examples of addressing errors in Q.823
IX.1 Introduction
IX.2 Protocol machine generated errors
IX.3 Use of CMISE errors
IX.4 Use of specific errors
IX.5 Conclusion
Appendix X Control hierarchy