GR 310 CORE : ISSUE 3

Preface
1. Introduction
   1.1 Purpose and Scope of This Document
   1.2 Related Documents
   1.3 Client Migration to Successor OSs and OS-NE Interfaces
   1.4 Organization of This Document
   1.5 Requirements Terminology
   1.6 Requirements Labeling Conventions
   1.7 Reissuance of the Interface Specification
   1.8 Future Work (Excluded Capabilities and Data)
2. Background: STP and CCS OS Functions and Data
   2.1 The Common Channel Signaling Network
   2.2 STP Functional Description
   2.3 CCS OS Functional Descriptions
3. Functional Overview of the Application-Level Interface
   3.1 General
   3.2 Types of Interaction
   3.3 Application Message Categories
   3.4 Message Priority and Routing
   3.5 Performance and Capacity
   3.6 Implementation of this Interface
4. Message Headers and UPL/Lower-Layer Interactions
   4.1 General
   4.2 UAL/X.25 Protocol Stack (TA-298)
   4.3 TCP/IP Protocol Stack (SR-5129)
5. UPL Interactions and Message Syntax Requirements
   5.1 Interaction Descriptions and Terminology
   5.2 General Application Message Syntax Requirements
   5.3 Overview of Formats for Detailed Message Specifications
   5.4 CCS OS-STP Application Layer and UPL Test Capabilities
6. Data Collection Messages
   6.1 Data Collection Request Structure and Terminology
   6.2 Descriptive Overview of Data Collection Messages
   6.3 Data Collection Message Specifications and Requirements
7. Recent Change and Verify (RC&V) Messages
   7.1 Description of Provisioning Data and RC&V Messages
   7.2 Recent Change Message Specifications
   7.3 Verify Message Specifications
8. On-Occurrence Autonomous Messages
   8.1 Memory Administration (Recent Change) On-Occurrence
       Messages
   8.2 Recent Change/Maintenance Surveillance On-Occurrence
       Messages
   8.3 Network Management/Maintenance Surveillance On-Occurrence
       Messages
   8.4 Maintenance Surveillance On-Occurrence Messages
   8.5 STP Administrative Processor Congestion/Overload Messages
   8.6 Enhanced Link Event Reporting Notifications
   8.7 Additional Requirements Regarding On-Occurrence Message
       Generation
9. STP Application Control Commands
   9.1 Data Collection Controls
   9.2 Network Management Controls
   9.3 Data Base Copy Control Command
   9.4 Summary Tables of Relevant SS7 Parameters
10.Transparent Mode (Flow-Through) Messages
   10.1 General
   10.2 Flow-Through Commands and Responses
   10.3 Flow-Through Autonomous Messages
11.Performance and Capacity
   11.1 General
   11.2 Availability and Reliability
   11.3 System Response Times
   11.4 Data Volume
   11.5 Storage Capacity
12.Message Priority and Routing
   12.1 Logical Channel Assignment Requirements
   12.2 Message Priority Structure
   12.3 Message Routing
13.Routing Verification Test Messages
   13.1 Overview
   13.2 MRVT Requirements
   13.3 SRVT Requirements
14.Interface Implementation Status and Priorities
   14.1 Overview
   14.2 Network Data Collection Functions and Messages
   14.3 RC&V Messages: Telcordia Signaling Network
        Activation Manager
   14.4 Surveillance Messages (for NTM and Network
        Maintenance OSs)
Appendix A: Data Collection Request Structure
Appendix B: Standard Data Collection Schedules
Appendix C: Prior Revision History
Appendix D: References
List of Figures
List of Tables

Defines the Telcordia view of detailed specifications and related generic functional requirements for the messages comprising the application-message layers (referred to as the "User Program Layer [UPL]") of the mechanized system interface between Common Channel Signaling Operations Systems (CCS OSs) and the Signaling Transfer Points (STPs) of the Telcordia client companies' Common Channel Signaling (CCS) networks.