TR TSV 000774 : ISSUE 1 SUPP 1

1. Introduction
1.1 Purpose
1.2 Document Organization
1.3 Key Bellcore Documents
1.4 Conventions
1.5 Scope of Generic Criteria on SS NEs
2. SMDS Overview
2.1 Service Description
2.2 Service Features
2.2.1 Access
2.2.2 Addressing
2.3 SMDS Interface Protocol
2.3.1 SIP Level 3_Protocol Data Unit Format
2.3.2 SIP Level 2_Protocol Data Unit Format
2.4 Quality of Service Objectives
3. SMDS Operations Technology
3.1 Approach
3.2 Operations Architecture
3.2.1 Network
3.2.2 Operations Systems
3.3 Operations Communications Architecture
4. SMDS Memory Administration Network Element
              Generic Requirements
4.1 Purpose
4.1.1 Supervisory Systems and Gateway SS NEs
4.1.2 Structure of Section 4
4.2 Changes Since Supplement 2 to TA-TSV-000774, Issue 3
4.3 Provisioning-Driven Functions
4.3.1 Information Validation
4.3.2 Memory Update
4.3.3 Database Query
4.3.4 Report Completions and Failures
4.4 System Administration Functions
4.4.1 Memory Backup and Restoration
4.4.2 Database Security
4.5 SMDS Object Classes
4.5.1 SMDS-Specific Object Classes
4.5.2 Generic Memory Administration Functional
              Object Classes to Support SMDS
4.5.3 Security Administration Object Classes
5. SMDS Maintenance Network Element Generic
              Requirements
5.1 Introduction
5.1.1 Maintenance Goals and Methods
5.1.2 Structure of the Network from a Maintenance
              Perspective
5.2 Changes Since Supplement 2 to TA-TSV-000774,
              Issue 3
5.3 Alarm Monitoring
5.3.1 Failure Conditions for the Incoming and
              Outgoing Signals
5.3.2 Alarm Conditions for the Internal Integrity of
              the SS
5.3.3 Monitoring the Ability to Communicate with
              Subtending SS NEs
5.3.4 Failure Condition Clears and Queries
5.3.5 Alarm Severity
5.4 Common Monitoring Requirements at Levels
              1, 2, and 3
5.5 Physical Layer Performance Monitoring for the
              Incoming and Outgoing Signals
5.6 Protocol Performance Monitoring - Levels 2 and 3
5.6.1 Protocol Parameters Monitored by Network Elements
5.6.2 Performance Monitoring Algorithms
5.6.3 Protocol Monitoring Plan
5.7 Testing
5.7.1 Testing of Physical Level of Subscriber Access
5.7.2 Line Loopbacks
5.7.3 Diagnostics
5.7.4 Protocol Test Access - Protocol Analysis
5.7.5 Testing of SIP Level 3
6. SMDS Network Traffic Management Network Element
              Generic Requirements
6.1 Purpose and Goals
6.2 Changes Since Supplement 2 to TA-TSV-000774,
              Issue 3
6.3 Definition of Congestion
6.3.1 Time Signatures of Congestion
6.4 Reference Architecture
6.4.1 Congestable Resources
6.5 Congestion Measurements
6.5.1 Collecting and Reporting NTM Congestion
              Measurements
6.5.2 Thresholding Strategy
6.6 NTM Controls
6.6.1 Automatic Controls
6.6.2 Manual Controls
7. SMDS Network Data Collection Network Element
              Generic Requirements
7.1 Purpose
7.2 Overview
7.3 Changes Since Supplement 2 to TA-TSV-000774,
              Issue 3
7.4 Data Collection Requirements
7.4.1 Data Collection Principles
7.4.2 Data Priority
7.5 Managing Collection and Reporting of
              Measurements
7.5.1 Data Collection and Reporting
7.5.2 Specifying Measurements to be Collected
7.5.3 Specifying Reporting Schedules
7.6 Network Usage Measurements
7.7 Scheduled Measurements
7.7.1 SS NE Scheduled Measurements
7.7.2 Subscriber Access Scheduled Measurements
7.8 Special Studies
7.8.1 Traffic Characterization Studies
7.8.2 Characterization of L3_PDU Lengths
8. Order of Precedence for Processing of SMDS
              Protocol Data Units
8.1 Overview
8.2 Changes Since Supplement 2 to TA-TSV-000774,
              Issue 3
8.3 Order of Precedence for PDUs at Ingress
8.3.1 Order of Precedence for BOM Segments at Ingress
8.3.2 Order of Precedence for COM Segments at Ingress
8.3.3 Order of Precedence for EOM Segments at Ingress
8.3.4 Order of Precedence for SSM Segments at Ingress
8.4 Order of Precedence for PDUs at Egress
9. Customer Network Management
10. Operations Interface Requirements
10.1 User System Interface
10.2 OS/NE Interface
11. Documentation Requirements
12. Glossary
13. Acronyms
Appendix A. Maintenance Performance Monitoring Calculations
A.1 Width of Counters
A.2 Threshold Value Ranges
A.3 Accuracy of 15 Minute Period
Appendix B. Monitored Parameters Used in the Assessment of
              L3_PDU Discards
REFERENCES
LIST OF FIGURES
Figure 1-1. Subscriber Access Arrangements to the Network
              Supporting SMDS
Figure 1-2. Potential SS Topologies
Figure 3-1. SS with Optional Supervisory System
Figure 3-2. Remote Operations Work Center Serving Multiple
              SSs
Figure 3-3. SS Operations Interfaces
Figure 3-4. Operations Interface Between an OS and a
              Distributed SS
Figure 5-1. Physical and Protocol Paths for Multi-CPE Access
Figure 5-2. Sum-of-Errors Algorithm Structure
Figure 5-3. Bursty Error Algorithm Structure
Figure 5-4. Bursty Error Algorithm Process
Figure 5-5. Level 3 Performance Monitoring Structure
Figure 5-6. Level 2 Performance Monitoring Structure
Figure 6-1. Types of Onsets and Abatement of Congestion
Figure 6-2. Functional Mode of a Simplified Network
              Supporting SMDS
Figure 6-3. Relative Positioning or Thresholds
Figure 8-1. Functional Model of an SS
LIST OF TABLES
Table 2-1. SIP Level 3_Protocol Data Unit (L3_PDU) Format
Table 2-2. SIP Level 2 Protocol Data Unit (L2_PDU) Format
Table 3-1. Relationship Between Operations Technology Domains
              and OSI Network Management Categories
Table 4-1. Subscriber Access Object Class Example
Table 4-2. Individual Address Screening Table Object Class
              Example
Table 4-3. Group Addressing Screening Table Object Class
              Example
Table 4-4. Maximum Concurrent Data Units Object Class Example
Table 4-5. Group Address Object Class Example
Table 4-6. Access Class Table Object Class Example
Table 5-1. Summary of Ingress Monitored SIP Parameters
Table 5-2. Encapsulation of the LLC TEST Command and Response
              PDUs within a SIP L_3 PDU
Table 7-1. Scheduled Measurements
Table 7-2. Special Studies Measurements
Table 8-1. Order of Precedence for BOM Segments at Ingress
Table 8-2. Order of Precedence for COM Segments at Ingress
Table 8-3. Order of Precedence for EOM Segments at Ingress
Table 8-4. Order of Precedence for SSM Segments at Ingress
Table 8-5. Order of Precedence for PDUs at Egress

Provides Bellcore's view of proposed generic requirements for Operations Technology on network elements (NEs) to support the early availability of Switched Multi-megabit Data Service (SMDS). SMDS is a proposed high speed, connectionless, public, packet switched service that will provide interconnection of Local Area Networks (LANs), hosts, workstations, etc. Generic requirements on the order of precedence for the processing of SMDS protocol data units are also included.