Print-Ready Version
Services > Testing > Conformance, Interoperability and Performance >

SSCOP (Q.2110) Signaling Conformance Test Suites

Part Number 803710 - SSCOP (Q.2110) Conformance Test Suite

The Telcordia® ATM Conformance Test Suite for Service Specific Connection Oriented Protocol (SSCOP) Test Suite provides a fully automated conformance testing of end system equipment, such as ATM switches User to Network Interface (UNI)/ Network Node Interface (NNI), that implement ATM Forum UNI 3.1 signaling requirement and support SSCOP protocol.

The Telcordia® SSCOP Conformance Test Suite assesses a system's ability to conform to the following standards from the International Telecommunication Union (ITU-T):

  • ITU-T Q.2110 B-ISDN ATM Adaptation Layer - Service Specific Connection Oriented Protocol (SSCOP)

The test suite consists of the following conformance test groups:

  • STATE_1 - these test group covers the Implementation Under Test (IUT) IUT's capability to correctly response on receipt of different message Protocol Date Unit (PDU) PDUs when it is at the state 1. These specifications are covered under the following sub-groups:
    • Val - these test cases verify the IUT's functionality for sending properly message back upon receipt of valid message PDUs when it is at the state 1.
    • Inv - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs when it is at the state 1. These specifications are covered under the following sub-groups:
      • MSG_SEQ - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs when it is at the state 1.
      • NOT_4BYPE_ALIGN - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs that is not 32-bit aligned when it is at the state 1.
      • INV_LEN - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs that is 32-bit aligned but incorrect length when it is at the state 1.
      • PAD_NOT_ZERO - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs with pad field coded as any value other than 0 when it is at the state 1.
      • RESV_NOT_ZERO - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs with reserve field coded as any value other than 0 when it is at the state 1.
  • STATE_7 - these test group covers the IUT's capability to correctly response on receipt of different message PDUs when it is at the state 7. These specifications are covered under the following sub-groups:
    • Val - these test cases verify the IUT's functionality for sending properly message back upon receipt of valid message PDUs when it is at the state 7.
    • Inv - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs when it is at the state 7. These specifications are covered under the following sub-groups:
      • MSG_SEQ - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs when it is at the state 7.
      • NOT_4BYPE_ALIGN - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs that is not 32-bit aligned when it is at the state 7.
      • INV_LEN - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs that is 32-bit aligned but incorrect length when it is at the state 7.
      • PAD_NOT_ZERO - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs with pad field coded as any value other than 0 when it is at the state 7.
      • RESV_NOT_ZERO - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs with reserve field coded as any value other than 0 when it is at the state 7.
  • STATE_10 - these test group covers the IUT's capability to correctly response on receipt of different message PDUs when it is at the state 7. These specifications are covered under the following sub-groups:
    • Val - these test cases verify the IUT's functionality for sending properly message back upon receipt of valid message PDUs when it is at the state 10.
    • Inv - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs when it is at the state 10. These specifications are covered under the following sub-groups:
      • MSG_SEQ - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs when it is at the state 10.
      • NOT_4BYPE_ALIGN - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs that is not 32-bit aligned when it is at the state 10.
      • INV_LEN - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs that is 32-bit aligned but incorrect length when it is at the state 10.
      • PAD_NOT_ZERO - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs with pad field coded as any value other than 0 when it is at the state 10.
      • RESV_NOT_ZERO - these test cases verify the IUT's functionality for sending properly message back upon receipt of invalid message PDUs with reserve field coded as any value other than 0 when it is at the state 10.
  • Timers - these test cases verify the IUT's functionality for correctly dealing with SSCOP timer when it is in different SSCOP states.