6 APPENDIX II

6.1 Abbreviations

    ANSI - American National Standards Institute

    API - Application Programming Interface

    ASN.1 - Abstract Syntax Notation 1

    ATM - Automated Teller Machine

    TCK - Technology Compatibility Kit

    HTML - HyperText Mark-up Language

    IN - Intelligent Network

    ITU - International Telecommunications Union

    JAIN - Java Advanced Intelligent Network

    JTAPI - Java Telephony Application Programming Interface

    MTP - Message Transfer Part

    OMAP - Operation and Maintenance Application Part

    P&M - Provisioning and Management

    QMS - Quality Management System

    RI - Reference Implementation

    SCCP - Signaling Connection Control Part

    SPC - Signaling Point Code

    SSN - Sub-System Number

    SS7 - Signaling System 7

    TCAP - Transactions Capabilities Application Part
     

6.2 Terms

Common Interface: - An Interface that defines a common fully functional set of methods from a specified group of protocol variants.

Global Title: - An address used by the SCCP, such as customer dialed digits which does not explicitly contain information that would allow routing in the signaling network, i.e. the SCCP translation function is required.

Interpretation Guru: - The expert that handles the maintenance of the specification.

Listener Interface: - The Listener Interface is the Java Listener interface specified in the JAIN TCAP API.

Peer: - A particular platform specific implementation of a Java interface or API.

Provider Peer: - The Provider Peer is the stack vendor specific implementation of the Provider Interface.

Provider Interface: - The Provider Interface is the Java Provider interface specified in the JAIN TCAP API.

Shall: - Within the Requirements Chapter 3, if the wording of a specific requirement includes ‘shall’ then the incorporation of this requirement in the JAIN TCAP specification is mandatory.

Should: - Within the Requirements Chapter 3, if the wording of a specific requirement includes ‘should’ then the incorporation of this requirement in the JAIN TCAP specification is strongly recommended but is not mandatory.

Signaling Point Code: - A binary code uniquely identifying a signaling point in a signaling network. This code is used, according to its position in the label, either as destination point code or as originating point code.

Specification Lead: - The expert responsible for writing the specification with input from the other experts, and hence responsible for developing consensus within the group. This person shall possess strong diplomatic and writing skills as well as technical expertise.

Sub-System Number: - A number to identify a subsystem using the SCCP either directly, like the ISDN User Part, or indirectly (via the Transaction Capabilities) like the OMAP.

TC_User: - Any User of the Transaction Capabilities Application Part.


Copyright - 2000 Sun Microsystems

28 June 00

If you have any comments or queries, please mail them to JainTcapRiFeedback@AePONA.com