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

PNNI 1.0/UNI 4.0 Signaling Interworking Test Suites

Part Number 803521 - UNI 4.0 to PNNI Interoperability for Point-to-Point Connections

The Telcordia® PNNI/UNI 4.0 Signaling Interworking Test Suite for Point-to-Point Connections Conformance Test Suite verifies the interworking of ATM equipments that implement ATM Forum PNNI 1.0 and UNI 4.0 signaling requirements that support call control procedure for point-to-point call connections. This test suite is based on ATM Forum's PNNI1.0 Signaling requirements, UNI Signaling Specification 4.0 and ITU-T Q.2931. The test suite consists of the following conformance test groups:

  • General - this test group address the basic signaling procedures to verify the Implementation Under Test (IUT)'s capability to support valid call/connection control procedures for point-to-point connections, which include all valid combination of Bearer Class, Traffic Parameters and Quality of Service (QoS). All valid combinations of supported optional information element. Call/connection clearing procedure. These specifications are covered under the following sub-groups:
    • Basic Setup - these test cases verify the IUT's functionality for receiving a SETUP message containing a combination of traffic parameters.
    • Setup Optional IE - these test cases verify the IUT's functionality for handling a message from and toward the called party with optional information elements.
    • Call Proceeding - this test case verifies the IUT's functionality for processing a Call Proceeding message from the called party.
    • Connect - these test cases verify the IUT's functionality for processing a Connect message from the called party.
    • Clearing - these test cases verify the IUT's functionality for call/connection clearing under various conditions.
    • SPVC - these test cases verify the IUT's functionality for soft PVPC and soft PVCC under various conditions.
  • Error - this test group covers procedures to verify IUT's capability to handle error conditions including error conditions for mandatory and non-mandatory information elements. This test group consists for the following sub-groups:
    • Protocol Error - these test cases verify the IUT's functionality for handling a message containing a protocol discriminator error.
    • Short Message Error - these test cases verify the IUT's functionality for handling short message.
    • Call Reference Error - these test cases verify the IUT's functionality for handling messages that contain a call reference error in which bits 5 through 8 of octet 1 are non-zero, a call reference length error and a message containing a global call reference value.
    • Message Sequence Error - these test cases verify the IUT's functionality for handling an unexpected (out of sequence) message.
    • Unrecognized Message Error - these test cases verify the IUT's functionality for handling an unrecognized message.
    • Message Length Error - these test cases verify the functionality for handling a message length error.
    • Mandatory Information Element (IE) Error - these test cases verify the IUT's functionality for handling messages that address the issues of missing mandatory IE, mandatory IEs with length errors and mandatory IEs with content error.
    • Non-Mandatory Information Element (IE) Error - these test cases verify the IUT's functionality for handling messages that address the issues of messages containing unrecognized IEs, error in the contents of a non-mandatory IE, non-mandatory IE with length error and a message with unexpected recognized IE.
    • Status Message Inquiry - these test cases verify the IUT's functionality for status inquiry procedures.
  • UNI 4.0 Procedure - this test group verifies the IUT's functionalities for the following ATM Forum UNI 4.0 specific procedures as defined in UNI 4.0 specification:
    • Traffic Negotiation - these test cases verify the IUT's functionality for traffic negotiation.
    • Individual QoS - these test cases verify the IUT's functionality for signaling individual QoS parameter procedures.
    • ABR - these test cases verify the IUT's functionality for Available Bit Rate (ABR) signaling procedure.
    • ATM Anycast - these test cases verify the IUT's functionality for ATM Anycast signaling procedures.
    • VPCI/VCI Selection - these test cases verify the IUT's functionality for VPCI/VCI selection procedures.
  • Timers - this test group of test cases verify the IUT's functionality for network side timer implementation.

Part Number 803522 - UNI 4.0 to PNNI Interoperability for Point-to-Multipoint Connections

The Telcordia® PNNI Signaling Interworking Test Suite for Point-to-Multipoint Connections Conformance Test Suite verifies the interworking of ATM equipments that implement ATM Forum PNNI 1.0 and UNI 4.0 signaling requirements that support call control procedure for point-to-point call connections. This test suite is based on ATM Forum's PNNI1.0 Signaling requirements and UNI Signaling Specification 4.0. The test suite consists of the following conformance test groups:

  • General - this test group address the basic signaling procedures to verify the Implementation Under Test (IUT)'s capability to support valid call/connection control procedures for point-to-point connections, which include all valid combination of Bearer Class, Traffic Parameters and Quality of Service (QoS). All valid combinations of supported optional information element. Call/connection clearing procedure. These specifications are covered under the following sub-groups:
    • Basic Setup - these test cases verify the IUT's functionality for receiving a SETUP message containing a combination of traffic parameters.
    • Incoming - these test cases verify the IUT's functionality for call/connection establishment for various conditions.
    • Clearing - these test cases verify the IUT's functionality for call/connection clearing under various conditions.
  • Error - this test group covers procedures to verify IUT's capability to handle error conditions including error conditions for mandatory and non-mandatory information elements. This test group consists for the following sub-groups:
    • Protocol Error - these test cases verify the IUT's functionality for handling a message containing a protocol discriminator error.
    • Short Message Error - these test cases verify the IUT's functionality for handling short message.
    • Call Reference Error - these test cases verify the IUT's functionality for handling messages that contains a call reference value that is not recognized/ a message containing an Endpoint Reference IE length that is not valid/ a message containing an Endpoint reference IE type that is not valid/ a message with an Endpoint Reference IE procedure that is not correct.
    • Message Sequence Error - these test cases verify the IUT's functionality for handling an unexpected (out of sequence) message.
    • Unrecognized Message Error - these test cases verify the IUT's functionality for handling an unrecognized message.
    • Message Length Error - these test cases verify the functionality for handling a message length error.
    • General IE - Repeat Information Element - these test cases verify the IUT's functionality for handling repetition of general information elements (IEs).
    • Mandatory Information Element (IE) Error - these test cases verify the IUT's functionality for handling messages that address the issues of missing mandatory IE, mandatory IEs with length errors and mandatory IEs with content error.
    • Non-Mandatory Information Element (IE) Error - these test cases verify the IUT's functionality for handling messages that address the issues of messages containing unrecognized IEs.
    • Status Message Inquiry - these test cases verify the IUT's functionality for status inquiry procedures.
  • UNI 4.0 Procedure - this test group verifies the IUT's functionalities for the following ATM Forum UNI 4.0 specific procedures as defined in UNI 4.0 specification:
    • Traffic Negotiation - these test cases verify the IUT's functionality for traffic negotiation procedures.
    • Individual QoS - these test cases verify the IUT's functionality for signaling individual QoS parameter procedures.
    • VPCI/VCI Selection - these test cases verify the IUT's functionality for VPCI/VCI selection procedures.
  • Timers - this test group of test cases verify the IUT's functionality for network side timer implementation.