I-ETS 300 293 : AUG 96

Foreword
1 Scope
2 Normative references
3 Abbreviations
4 General
  4.1 Purpose
  4.2 Field of application
  4.3 Structure of this I-ETS
  4.4 Overview of the network model
5 Object classes
  5.1 Network fragment
  5.2 Managed element fragment
  5.3 Termination point fragment
  5.4 Cross connect fragment
  5.5 Functional area fragment
  5.6 Service fragment
6 Packages
7 Attributes
8 Name bindings
  8.1 Equipment
  8.2 Network
9 Actions
10 Notifications
11 ASN.1 defined type module
12 Entity-relationship diagrams
Annex A (normative): Object classes for call routing
                     information management
  A.1 Object classes
  A.2 Attributes
  A.3 Name Bindings
  A.4 Actions
  A.5 ASN.1 type definitions
Annex B (informative): Object classes for customer
                       administration on the Operation
                       Systems/Network Element (OS/NE)
                       interface
  B.1 Object classes
Annex C (informative): Candidate object classes for
                       the network level viewpoint
  C.1 Network
  C.2 Layer sub-network
  C.3 Package definition
  C.4 Attribute definitions
  C.5 Name bindings
  C.6 Actions
  C.7 ASN.1 syntax
  C.8 Topological points
  C.9 Conclusion
Annex D (informative): Candidate object classes for
                       the service level viewpoint
  D.1 Introduction
  D.2 Service level financial objects
  D.3 Service level usage information objects
  D.4 Service level objects for telecommunication
      services
  D.5 Other service level objects
Annex E (informative): Examples of use of generic
                       object classes
  E.1 Transport network architecture
  E.2 Applications of the proposed model
History

Provides a generic management information Model and identifies those TMN managed object classes that are generic (i.e. potentially apply to more than one specific information model) and that are used to describe information exchanged across TMN interfaces defined in CCITT Recommendation M.3010 [1].