GR 2833 CORE : ISSUE 3 REV 2

1 Introduction
1.1 Purpose and Scope
1.2 Relationship with Other TAs, TRs, GRs, and
              Standards
1.3 Requirements Terminology
1.4 Organization of the Document
1.5 Changes in this Issue
2 Background
2.1 Background of the Management Operations Interface
              Environment
2.1.1 Conceptual View of System Management
2.1.2 OSI-Based Systems Management Communications
2.2 IDLC System Management
2.3 FITL System Management
2.4 GR-2833-CORE and the GR-303-CORE Integrated
              Access Platform
3 Overview of the IDLC and FITL Information Model
3.1 Overview of Managed Objects
3.2 IDLC and FITL Testing Overview
3.2.1 IDLC and FITL Testing Architecture
3.2.2 Test Model Overview
3.3 Modeling Considerations for Integrated IDLC and
              FITL Systems
3.4 GR-303-Feature Groups and the Integrated
              IDLC and FITL Information Model
4 Guidelines on Use of Managed Objects for
              IDLC AND FITL Systems
4.1 Summary of Object Class for IDLC System and
              FITL System Management
4.2 Requirements for Object Class Support
4.2.1 Termination Point Fragment
4.2.2 Managed Element Fragment
4.2.3 Cross-Connection Fragment
4.2.4 Protection Switch Fragment
4.2.5 Generic Support Object Fragment
4.2.6 Performance Monitoring Fragment
4.2.7 Point-to-Multipoint Fragment
4.2.8 Test Management and Access Fragment
4.2.9 Video Transport Management Fragment
4.3 EM-RDT Object Groups
4.3.1 Core Object Groups
4.3.2 Extension Object Groups
5 IDLC and FITL System Model Summary
5.1 Major Changes to Information Model from Issue 2
5.2 Inheritance Relationships
5.3 Containment Relationships
5.4 Definitions for GR-2833-CORE Issue 3
5.4.1 Managed Objects
5.4.2 Packages
5.4.3 Attributes
5.4.4 Name Bindings
5.4.5 Actions
5.4.6 Notifications
5.4.7 Parameters
5.4.8 Supporting Productions
5.5 Information Model Deprecations from Issue 2
5.5.1 Deprecated Objects
5.5.2 Deprecated Namebindings
6 Examples
6.1 Examples of IDLC System Models
6.2 Examples of FITL System Models
6.3 Example Model of a Combined Technology NE
6.4 Test Model Examples
6.5 Examples of Video Service Models
Appendix A: IDLC and FITL System Model Summary
   A.1 alertingCadence
   A.2 channelTestCoordinator
   A.3 fitlCTPBidirectional
   A.4 ftilCTPSink
   A.5 fitlCTPSource
   A.6 fitlDropTestingSystem
   A.7 fitlLineTTPBidirectional
   A.8 fitlLineTTPSink
   A.9 fitlLineTTPSource
   A.10 fitlPathTTPBidirecitonal
   A.11 fitlPathTTPSink
   A.12 fitlPathTTPSource
   A.13 idlcCallProcessingProfile
   A.14 idlcDataLinkProfile
   A.15 idlcTerminal
   A.16 idlcTerminalBCRrl
   A.17 multipleAccessFunction
   A.18 ptmLineTTPGroup
   A.19 ptmPathTTPGroup
   A.20 ptmTTPGroup
   A.21 testResponseCircuit
Appendix B: Test Category Summaries
   B.1 Test Categories
   B.1.1 FITL Drop Test Category
   B.1.2 Multimeter Measurement Test Category
   B.1.3 Noise Measurement Test Category
   B.1.4 Tone Measurement Test Category
Appendix C: TR-TSY-O00303 Supplement 3 and CMISE-GR2833
              EM-RDT IDLC Models
Appendix D: IDLC and FITL System Model Summary
   D.1 RDT System/Hardware Object Group
   D.2 RDT General Support Object Group
   D.3 Interface Group (IG) Object Group
   D.4 POTS + ISDN Object Group
   D.5 DSl Object Group
References
Acronyms
List of Figures
Figure 2-1 A Conceptual Model for System Management
Figure 2-2 Management Communications Using CMISE
Figure 3-1 Generic Test Access and Testing Architecture
Figure 3-2 Metallic Loop Testing Using OSI/CMISE Interfaces
              in an IDLC System
Figure 3-3 Metallic Loop Testing Using an OSI/CMISE Interface
              in an Integrated FITL System
Figure 5-1 Inheritance Hierarchy (Sheet 1 of 2)
Figure 5-2 Inheritance Hierarchy (Sheet 2 of 2)
Figure 5-3 Name Bindings (Sheet 1 of 2)
Figure 5-4 Name Bindings (Sheet 2 of 2)
Figure 6-1 Example Point-to-Point FITL System with Analog
              Termination
Figure 6-2 Example Transport Model for a Point-to-Point
              FITL System Supporting Analog Transmission
Figure 6-3 Example Hardware Model for a Point-to-Point
              FITL System
Figure 6-4 Example Transport Model for a Point-to-Point
              FITL System Supporting DDS and ISDN 4:1 TDM
Figure 6-5 Example Point-to-Multipoint FITL System with
              Analog Terminations
Figure 6-6 Example Transport Model for a Point-to-Multipoint
              FITL System Supporting Analog Transmission
Figure 6-7 Example of Multiple Access Function and Point-to-
              Multipoint Termination Point Groupings in Point-to-
              Multipoint FITL System
Figure 6-8 Example of a UFITL System
Figure 6-9 Example Transport Model for a UFITL System
Figure 6-10 Example Hardware Model for a UFITL System
Figure 6-11 Example of a Combined Technology NE
Figure 6-12 Example Transport Model for a Combined Technology
              NE (Sheet 1 of 2)
Figure 6-13 Example Transport Model for a Combined Technology
              NE (Sheet 2 of 2)
Figure 6-14 Example Channel Test Sequence for LSS
Figure 6-15 Example Drop Test Sequence for LSS
Figure 6-16 Example Special Service Circuit Test Sequence
Figure 6-17 Example HFC System For Video Services
Figure 6-18 Example HFC Model for Video Services
              (Access Subnetwork)
Figure 6-19 Example HFC Transport Model for Video Services
              (NIU/STU)
Figure 6-20 Example FITL System for Video Services
Figure 6-21 Example FITL Transport Model for Video Services
Figure 6-22 Example FITL Transport Model of Video Service
              (NIU/STU)
List of Tables
Table 2-1 Preliminary Impact Assessment of Integrated Access
              Platform Requirements Work on GR-2833-CORE
Table 4-1 Object Classes for IDLC and FITL System Management
Table 4-2 Core Object Groups for CMISE-GR2833 EM-RDT
Table 4-3 Extension Object Groups for CMISE-GR2833 EM-RDT
Table 5-1 GR-2833 Issue 2 Object Classes Moved to Other
              Documents
Table C-1 IDLC Object Classes in GR2833 and in Supplement 3
Table D-1 circuitPack
Table D-2 cross ConnectionBCRrl
Table D-3 equipmentHolder
Table D-4 fabric BCRrl
Table D-5 managedElementRl
Table D-6 alarmSeverityAssignmentProfile
Table D-7 currentAlarmSummaryControlBCRrl
Table D-8 diagnosticControl
Table D-9 eventForwardingDiscriminator
Table D-10 managementOperationsSchedule
Table D-11 scanReportRecord
Table D-12 simpleScanner
Table D-13 thresholdData
Table D-14 idlcCallProcessingProfile
Table D-15 idlcDataLinkProfile
Table D-16 idlcTerminal
Table D-17 analogLineTTPBidirectional
Table D-18 ds0CTPBidirectional
Table D-19 isdnBriPathTTPBidirectional
Table D-20 isdnCTPBidirectional
Table D-21 isdnDSLTTPBidirectional
Table D-22 quarterDs0CTPBidirectional
Table D-23 isdnTTPCurrentData - GR-836
Table D-24 dslCTPBidirectional
Table D-25 dslLineTTPBidirectional
Table D-26 dslPathTTPBidirectionalBCRrl
Table D-27 dslLineTTPSinkCurrentData
Table D-28 dslPathTTPSinkCurrentData

Gives Bellcore's view of proposed generic requirements for an operations communications interface for managing Integrated Digital Loop Carrier (IDLC) and Fiber In the Loop (FITL) systems using the Open Systems Interconnection (OSI) management services and protocols defined in ISO/IEC IS 9595 (Common Management Information Service Element Definition) and ISO/IEC IS 9596 (Common Management Information Protocol). Specifically proposes an information model that gives a common frame of reference for operations communications between a managing system, and IDLC system, and a FITL system. Also, the model may be used for managing multiple technology access systems which may be a combination of IDLC, FITL, and SONET transport technologies.