GR 2940 CORE : ISSUE 2

Generic OTGR contents and ordering information
Preface
1. Introduction
1.1 Specification tools
1.2 Relationship with other Bellcore Documents and
      standards
1.3 Purpose of document
1.4 Changes from previous issue
1.5 Organization of this document
1.6 Requirements terminology
2. Background of operations interfaces using OSI tools
2.1 Conceptual view of system management
2.2 Principles of information modeling
2.3 Common management information services
2.4 Network management
2.5 Specification tools - GDMO templates
2.6 Registration
3. Background
3.1 Introduction
3.2 History and scope of Bellcore testing requirements
3.3 Generic access and testing architecture
3.4 Approaches to distributed testing
3.5 Characteristics of current testing domains
3.6 Business drivers
3.7 Resolution
3.8 A-Mode and B-Mode characteristics
3.9 Other features of the CMISE-bases interface
4. Access and testing model overview
4.1 The test environment
4.2 Test function
4.3 Roles for objects in test management
4.4 Underlying CMISE services
4.5 Test scenarios
4.6 Architectural mapping of test management model
4.7 Test access
4.8 Callback line
4.9 Access and testing model framework
4.10 Using the model
4.11 Callback line model elements
5. Access and testing management information model
5.1 Object class relationships
5.2 Functional mapping of service types
5.3 Guidelines for referencing information
5.4 System management functional units
5.5 Requirements for GR-2940-CORE
5.6 Definitions of managed object
5.7 Definitions of conditional packages
5.8 Definitions of attributes
5.9 Definitions of parameters
Appendix A: Test category summaries
References
Glossary

Provides the view of the Telcordia on generic needs for the information model of an Open Systems Interconnection/Common Management Information Service Element (OSI/CMISE) - based interface for Plain Old Telephone Service (POTS)/loop testing. Terminology of the Bellcore generic testing architecture, the interface is between a Testing Operations System and a Test System Controller/Remote Test Unit. Details the needed object classes, actions, attributes, etc needed to implement the information model. Details two variants of the model, the A-mode and B-mode, which are most appropriate for large end office based testing systems and smaller testing systems, respectively.