TR TSY 000385 : ISSUE 1 REV 1

1 Introduction
1.1 Perspective
1.2 Concepts and Definitions
1.3 Relationship to Previous Documentation
2 AMAT/Collector Interface Specification
2.1 Introduction
2.1.1 Scope
2.1.2 Overview of the Interface
2.1.3 Collector Functional Description
2.1.4 AMAT Functional Description
2.2 Protocol Layers
2.2.1 Physical Layer
2.2.2 Link Layer
2.2.3 Packet Layer
2.2.3.1 Introduction and General Considerations
2.2.3.2 Logical Channels
2.2.3.3 Differences in DTE/DTE and DTE/DCE Operation
2.2.3.4 Procedures for Data and Interrupt Transfer
2.2.3.5 Maximum User Data Field Length of DATA Packets
2.2.3.6 Delivery Confirmation Bit
2.2.3.7 More Data Mark
2.2.3.8 Qualifier Bit
2.2.3.9 Window Description
2.2.3.10 Throughput Characteristics and Throughput Classes
2.2.3.11 Procedures for Reset
2.2.3.12 The DIAGNOSTIC Packet
2.2.3.13 Recovery from Nonacknowlegement of DATA Packets
2.2.3.14 Recovery from Receipt of Erroneous DATA Packets
2.2.3.15 Procedures for Packet Layer Optional User Facilities
2.2.3.16 DTE Timer Parameters
2.2.3.17 DTE Retransmission Count Parameters
2.2.4 Session Layer
2.2.4.1 BX.25 and AMATPS Session Layer
2.2.4.2 Session Layer Messages
2.2.4.3 AMAT and Collector Session Layer Description
2.2.5 Application Layer
2.2.5.1 Application Layer Messages
2.2.5.2 AMAT File Transfer Description
2.2.5.3 Collector File Transfer Description
2.3 AMATPS Data Structures
2.3.1 AMA Data Files
2.3.1.1 Primary AMA Data File
2.3.1.2 Secondary AMA Data File
2.3.2 Special Files
2.3.2.1 Secondary Tracer Record File
2.3.2.2 Maintenance File
2.3.2.3 Test File
2.3.2.4 Dump File
2.3.2.5 Program File
2.3.2.6 Operational Data File
2.3.2.7 Time Synchronization Files
2.3.2.8 Translation File
2.3.3 Tracer Records
2.3.3.1 Primary Tracer Records
2.3.3.2 Secondary Tracer Record
2.3.3.3 Tracer Count Reconciliation
2.4 Changes/Clarifications to Prior Documentation
2.4.1 Application Layer (File) Messages
2.4.2 File Sequence Number
2.4.3 File Reject Message: Next File Name Field
2.4.4 Session Layer Messages
2.4.5 Message Received Sequence Number
2.4.6 BX.25 Text Eliminated
2.4.7 Link Layer Exceptions
2.4.8 Link Layer Password Exchange
2.4.9 File Formats
2.4.10 Padding of Blocks
2.4.11 SDL for Application and Session Layers
2.4.12 Primary Tracer Records
2.4.13 Secondary Tracer Record File
2.4.14 Multi-Switch AMATs
2.4.15 Maintenance Record
2.4.16 Inactivity Timer
2.4.17 Primary and Secondary File Polling within the Same
             AMAT Session
2.5 Future Enhancements
APPENDIX A: Protocol Layer Data and Layouts
APPENDIX B: Application Layer Messages
APPENDIX C: Session Layer Messages
APPENDIX D: AMATPS File Names
APPENDIX E: Maintenance Records
APPENDIX F: Fixed Data Test Pattern
APPENDIX G: Structure for Translation Files
APPENDIX H: Block Header Format
APPENDIX I: SDL Key
3 AMA Transmitter Generic Requirements
3.1 Introduction
3.1.1 Scope
3.1.2 Configurations
3.1.3 Definitions
3.1.4 Multi-Switch AMAT
3.1.5 High-Level AMAT Description
3.2 User Perspective
3.2.1 Documentation
3.2.2 Input/Output
3.2.3 Operational Activities
3.2.4 Database
3.3 AMAT Generic Requirements
3.3.1 Data Handling Requirements
3.3.1.1 Bellcore AMA Format
3.3.1.2 Mass Storage Capacity
3.3.1.3 Block Structure for Mass Storage and Transmission
3.3.1.4 Block Sequence Numbering
3.3.1.5 Primary Polling
3.3.1.6 Secondary Polling
3.3.1.7 Simultaneous Polling Considerations
3.3.1.8 Tracer Records
3.3.1.9 Transfer In and Transfer Out Flags
3.3.1.10 Input/Output Messages
3.3.1.11 Daily Maintenance Record
3.3.1.12 Test File
3.3.1.13 Call Event Reference Times
3.3.1.14 Validation Flag
3.3.2 Capacity
3.3.3 Interfaces
3.3.3.1 Collector Interface
3.3.3.2 Switch Interface
3.3.3.3 Local Maintenance Interface
3.3.3.4 Remote Maintenance Interface
3.3.3.5 Alarm Interface
3.3.4 Administration
3.3.4.1 Installation
3.3.4.2 Service Changes
3.3.4.3 Capacity Monitor
3.3.4.4 Maintenance Measurements
3.3.5 Maintenance
3.3.5.1 Diagnostics
3.3.5.2 Alarms
3.3.5.3 On-Line Functional Test
3.3.6 Performance
3.3.7 Interactions
3.3.8 Environmental Requirements
3.3.9 Power Source
3.3.10 Internal AMAT Implementation Requirements
3.3.11 Adjunct AMAT Implementation Requirements
3.3.11.1 Switch/AMAT Interface
3.3.11.2 Improved AMA Functions
3.3.11.3 Maintenance and Operations
3.3.11.4 Alarm Items
3.3.11.5 Program Loading
3.3.11.6 Interface Replacement Considerations
3.3.11.7 Acceptance Testing Capabilities
3.3.12 Multi-Switch AMA Transmitters
3.3.13 Optional AMAT Features
3.3.13.1 Use Collector to Monitor AMAT Time
3.3.13.2 Operational Instructions from the Collector
3.3.13.3 Program Dump to Collector
3.3.13.4 Local Tape Capabilities
4 AMATPS Collector Generic Requirements
4.1 Introduction
4.1.1 Scope
4.1.2 High-Level Collector Description
4.2 User Perspective
4.2.1 Personnel Interaction
4.2.2 Documentation
4.3 Collector Generic Requirements
4.3.1 Main Collector Operations
4.3.1.1 Collecting AMA Data
4.3.1.2 Auditing and Administering AMA Data
4.3.1.3 Outputting AMA Data
4.3.2 Other Collector Operations
4.3.2.1 Secondary Polling
4.3.2.2 Non-AMA Data
4.3.2.3 Database
4.3.2.4 Printout From Tape
4.3.2.5 Input/Output Messages
4.3.2.6 Program Loading
4.3.2.7 Operations Reports
4.3.3 Capacity and Overload Control
4.3.4 Administration
4.3.4.1 Installation
4.3.4.2 Service Changes
4.3.4.3 Person/System Interface
4.3.4.4 Quantities
4.3.5 Maintenance
4.3.5.1 Diagnostics
4.3.5.2 Exercisers
4.3.5.3 Alarms
4.3.5.4 Maintenance Reports
4.3.6 Performance
4.3.7 Environmental Requirements
4.3.8 Power
Glossary
References
LIST OF TABLES
Table 1-1 AMATPS Allocation of Billing Error Standards
Table 2-1 AMATPS Link Layer Protocol Parameters
Table 2-2 Packet Layer Timer Values
Table 2-3 Packet Layer Counter Values
Table 3-1 AMA Teleprocessing System - AMA Data Accuracy
             & Reliability Requirements
Table 3-2 AMA Processing Tracer - Structure Code 09100
Table 3-3 Channel Tracer - Structure Code 09101
Table 4-1 AMATPS AMA Data Accuracy and Reliability
             Requirements

AutomaticMessage Accounting (AMA) is a switching system process that generates the data from which the Revenue Accounting Office (RAO) bills carriers for network access, and bills customers for their usage of the network and various telephoney services. AMA data items that a switch generates for a typical phone call include calling party phone number, called party phone number, date and time when a conversation starts and total conversation time. The RAO uses the calling phone number to determine the account to be billed. This TR defines generic requirements applicable to AMA data teleprocessing capabilities for LATA switching systems and all other types of network switching elements.